We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
schemaVersion
The schemaVersion REST API attribute should only contain the current metadata schema version in a standard format.
The schemaVersion attribute reflects only the current schema version of the DOI metadata.
The schemaVersion attribute can contain arbitrary strings and can be overwritten by users.
Submit a POST or PUT request with the schemaVersion attribute containing an arbitrary string.
The text was updated successfully, but these errors were encountered:
The user-submitted value is used for transitioning a DOI's metadata from schema 3 to schema 4: https://support.datacite.org/docs/how-do-i-update-my-dois-to-metadata-schema-version-4-with-the-datacite-rest-api. I'm not sure if there are other places in our systems that have behaviour based on this value.
It would be great to have this field accurately reflect the schema version being used—at least the major version, if not minor.
Sorry, something went wrong.
schema_version
current_metadata
codycooperross
Successfully merging a pull request may close this issue.
Describe the bug
The
schemaVersion
REST API attribute should only contain the current metadata schema version in a standard format.Expected Behaviour
The
schemaVersion
attribute reflects only the current schema version of the DOI metadata.Current Behaviour
The
schemaVersion
attribute can contain arbitrary strings and can be overwritten by users.Steps to Reproduce
Submit a POST or PUT request with the
schemaVersion
attribute containing an arbitrary string.Context (Environment)
Screenshots
Further details
Proposal
Hypothesis
Possible Implementation
The text was updated successfully, but these errors were encountered: