-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: force all the dois updated with the form to become schema 4 #452
Conversation
So what will happen in the scenario of older schema version with missing data, the form should fail to submit because it will be missing required fields right? and therefore once they fill it in, it will be valid schema 4? |
Can't review as I am on vacation. |
its mostly an FYI @mfenner . @richardhallett yeah, in that case, it will fail until they fill all the fields correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. It would be good if the form would show a warning message if you open a DOI using a schema version < 4.
unrelated test are failing because DOIs already exist (422) which doesn't make sense. This might be related to datacite/lupo#606. and it happening even with the master branch and the last release. This needs be fixed to merge. |
Purpose
Forces all DOIs updated in the form to become schema 4.
closes: #447
Approach
All DOIs updated in the form will be transformed to schema 4. Independently of the state of the DOI (draft, registered, findable)
Learning
Looking back at the form support messages it can be seen that the form has not support schema transformation on the past. See https://app.frontapp.com/open/msg_29opdsb from 2019 ,which is related to datacite/datacite#654
This most likely due to the form modifying the metadata fields. The schema version is not a metadata field.
Status
Types of changes