DMP upload would not complete the registration

[magicalmary]

User Andrew Johnson at Colorado-Boulder, testing the new upload feature on production.

Uploaded pdf file and entered information in each section. Made sure PI was entered and flagged as the primary contact.

At last screen, tried to register plan using both registration buttons, but each time received a message stating "There was a problem registering the plan. Try again later."

I jumped on a Zoom with the user, and we reviewed the entered information; I did not notice anything unusual. He repeated the steps and again the registration failed. Next, I changed my profile to Boulder. and tried to register it but I received the same message.

Plan: https://dmptool.org/dashboard/dmp/20240408-7639fc91feed
Title: Understanding the Reversals in Polarity of the Magnetic Fields of Planets and Stars

[briri]

It was rejected because the Repository has no name. We need both a name and a URL for repository definitions.

Looking at the URL the user entered, https://doi.org/10.1103/PhysRevResearch.4.L012026, brings me to the landing page of an actual dataset. We aren't looking for actual outputs here, we're looking for the repository information. Our background harvesters will look at systems like DataCite to try and find the research outputs.

Perhaps we need some guidance on the page to explain what is expected here.

[mariapraetzellis]

@magicalmary Thanks for reporting this one. Can you record this issue in the feedback doc so we can track it? Thinking of the error message and confusion about the repository URL.

[briri]

we also really need to update the React pages so that they display these error messages for the user. The DMPHub sent back "errors"=>["A DMP ID could not be registered at this time.", "Invalid JSON., The property '#/dmp/dataset/0/distribution/0/host' did not contain a required property of 'title'"]. The JS code should be able to use this to help the user understand what the problem was

[magicalmary]

It was rejected because the Repository has no name. We need both a name and a URL for repository definitions.

Looking at the URL the user entered, https://doi.org/10.1103/PhysRevResearch.4.L012026, brings me to the landing page of an actual dataset. We aren't looking for actual outputs here, we're looking for the repository information. Our background harvesters will look at systems like DataCite to try and find the research outputs.

Perhaps we need some guidance on the page to explain what is expected here.

Thanks, Brian. The user was trying to indicate the resulting research paper output, so there is not an associated 'repository' unless you count the journal. We may need to discuss and update guidance, etc., as you have suggested.

[magicalmary]

Mary & Maria will review language on the outputs to make clear they relate to those detailed within the DMP, not the entirety of the research outputs.

[magicalmary]

Changes for the outputs section:

1. Change 'Title' to 'Proposed output'
2. Remove the following 4 permissible values from 'Data type' field: event, service, text, workflow
3. Change 'Repository Size' to 'Estimated size of data'
4. Change 'URL' to 'Repository URL (e.g., "https://dataverse.org/")'