Ellen Kraffmiller

@mccalluc thanks for your comments, I made some additional changes

Hi @k4llman, there are issues with deprecated libraries, so that might be causing your error, but I also noticed that you are running on localhost:8080 - the app should be...

> > Deploy to beta.dataverse.org and do the rich-results test. > > It would be nice for beta to only run merged code but whatever works for now! > >...

I created a Dataverse issue for customizing robots.txt: https://github.com/IQSS/dataverse/issues/10593

@GermanSaracca There is still a difference between the form validation and the API validation - from my testing, I think the API validation is requiring that the email address be...

> > @GermanSaracca There is still a difference between the form validation and the API validation - from my testing, I think the API validation is requiring that the email...

@GermanSaracca There are some warnings due to the new lint tests...I know we don't need to fix them all, but maybe this PR could fix the ones related to Create...

beta.dataverse.org has been updated with a robots.txt to allow all, so now https:/beta.dataverse.org is being crawled successfully, but individual dataset pages are not being indexed by Google. See this page...

> Shouldn't we add this functionality also for the test workflow? yes, thanks for catching that! I didn't add it to the deploy workflows however, since I thought that could...

> https://dataverse-guide--9776.org.readthedocs.build/en/9776/container/auto-usage.html @pdurbin It looks like this uses the access to secrets to control the actions triggered by external contributors. Based on our conversation at standup, I don't think we...