datacite icon indicating copy to clipboard operation
datacite copied to clipboard

Python API wrapper for the DataCite API.

Results 9 datacite issues
Sort by recently updated
recently updated
newest added

:heart: Thank you for your contribution! ### Description Please describe briefly your pull request. ### Checklist Ticks in all boxes and 🟢 on all GitHub actions status checks are required...

We should support the DataCite 4.5 Schema. https://doi.org/10.5438/jvkk-8198 ```[tasklist] ### Tasks - [ ] Transfer over starting schema from @mfenner https://github.com/front-matter/commonmeta-py/blob/main/commonmeta/resources/datacite-v45.json - [ ] Transfer all example 4.5 files from...

Package version (if known): 1.1.3 ## Describe the bug uniqueItems does not appear to be justified in the arrays in the json schemas where it is currently used (e.g. [creators](https://github.com/inveniosoftware/datacite/blob/master/datacite/schemas/datacite-v4.3.json#L259))...

Package version (if known): v1.1.2 ## Describe the bug The date format verification https://github.com/inveniosoftware/datacite/blob/b15db91e1231135e5f2dba0cadca0c72ede037cf/datacite/schemas/datacite-v4.3.json#L80 may not be used by default https://python-jsonschema.readthedocs.io/en/latest/validate/#validating-formats or be implemented correctly.

DataCite is depreciating version 3.1 metadata in January 2025 https://datacite.org/blog/deprecating-schema-3/. We should remove it here too.

I *thing* we have had a behavior change on the DataCite side. When a specified DOI is included in the metadata (not as a doi= option), DataCite ignores it and...

Package version (if known): 1.1.3 ## Describe the bug The field `"dentifiers"` corresponds to the optional field additionalIdentifiers in the DataCite XSD, however, in the json schema v4.3 `"dentifiers"` is...

The REST API wrapper documentation should be expanded, and more (non-XML) examples should be provided.

Several backwards-compatibility solutions and implementation details that should be dropped with DataCite metadata 5.0: 1. Drop support for single ``geoLocationPolygon`` - schema users should generate ``geoLocationPolygons`` instead. 1. Drop support...