You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example: If a new version is created from a previous version with a minted DOI, then we should start in "No" mode.
Example: For a new deposit we start in "Yes"-mode.
The backend should be able to control the initial state based on the data it's sending.
Sending data to the REST API
# Yes with an value (empty string allow)
{"pids": {"doi": {"provider": "external", "identifier": "<value>"}}}
# No - without a reserved DOI
{"pids": {}}
# No - with a reserved DOI
{"pids": {"doi": {"provider": "datacite", "identifier": "<value>", "client": datacite}}}
Receiving data from the REST API
The form should not start modifying the data it receives from the backend. E.g. it looks like that if you send:
{"pids": {"doi": {"provider": "external", "identifier": ""}}} it gets changed to {"pids": {"doi": {"provider": "external"}}}.
The DOI field has several issue.
To test it you need to enable DOI minting:
Serialization/Deserialization/Form state
It should be possible to initialise the form to start either yes or no mode:
Example: If a new version is created from a previous version with a minted DOI, then we should start in "No" mode.
Example: For a new deposit we start in "Yes"-mode.
The backend should be able to control the initial state based on the data it's sending.
The form should not start modifying the data it receives from the backend. E.g. it looks like that if you send:
{"pids": {"doi": {"provider": "external", "identifier": ""}}}
it gets changed to{"pids": {"doi": {"provider": "external"}}}
.Error messages in form feedback
Error messages should be displayed in the FormFeedback with correct label.
Example:
"Digital object identifier: Missing DOI for field."
The API delivers error messages as either (most errors or on the
pids.doi
):Error messages on field
Error messages should be displayed on the field. Note the error can likely be put on the text field for the unmanaged DOI.
vs
The text was updated successfully, but these errors were encountered: