datacite
datacite copied to clipboard
DataCite Metadata v5.0 update list
Several backwards-compatibility solutions and implementation details that should be dropped with DataCite metadata 5.0:
- Drop support for single
geoLocationPolygon
- schema users should generategeoLocationPolygons
instead. - Drop support for
type
in the title, users should usetitleType
. -
nameType
should be a sub-property of creatorName/contributorName, instead of a direct sub-property of Creator/Contributor. This was kept this way to avoid changing the type of the creatorName/contributor name fiels from string to object between 4.0 -> 4.1 schema updates. In 5.0nameType
should be a subproperty of creatorName and contributorName, which by themselves should be objects like:
"creatorName": {
"type": "object",
"properties": {"creatorName": {"type": "string"}, "nameType": {"enum":[..]}}
}
- DataCite requires four
polygonPoint
elements pergeoLocationPolygon
(andpolygonPoint[0] == polygonPoint[-1]
). So far JSON schema was requiring only 3 and was kept this way forgeoLocationPolygon
due to backwards compatibility, with a generation of a missing polygon when necessary (actually the auto-generation was not done until 4.1 upgrade, so it's not clear what the original intention was). ThegeoLocationPolygons
also requires minimum 3 points. In new kernel, a decision needs to be made whether:- 4 is the new minimum number of points, and the schema validation should fail if first point does not match the last point (or auto-generate)
- 3 remains to be the minimum number of points, and we continue to auto generate the last point.