-
Type:
Improvement
-
Status: Volunteer Needed (View Workflow)
-
Priority:
Trivial
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
-
Attachments:
-
Comments:4
-
Documentation Status:Needed
While testing the introduction of DOI's with Datacite I noted some discrepancies between the code and documentation.
The statuses used in DOIIdentifierProvider do not match the ones mention in the documentation
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L70
versus
https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier
"In DSpace, a DOI can have the state "registered", "reserved", "to be reserved", "to be registered", "needs update", "to be deleted", or "deleted". After updating an item's metadata the state of its assigned DOI is set back to the last state it had before"
It would be good to describe the flow/process of creation and the proper order of jobs the doi-organiser should run.
Furthermore the documentation for the doi-organiser (https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface) is wrong with regards to the options which can be used on a single item see DS-2669.
- is related to
-
-
- Volunteer Needed
-