Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free: http://www.readytalk.com/intl 
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
    • Once on the call, enter participant code 2257295

Agenda

...

: DOIs + DSpace

 
DCAT input on the Proposal to move all DSpace-generated DOIs to dc.identifier.doi
Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3708

Background: The Developer Team recently had detailed discussions around where DOIs are stored in DSpace, and how to better manage their storage going forward.
Currently, based on the DOI system instances have configured, DOIs may be stored in either "dc.identifier.uri" (alongside Handles), or in "dc.identifier".  See this ticket: https://jira.duraspace.org/browse/DS-2199

After much discussion, the Developer Team proposes, starting with DSpace 7, (automatically*) moving all DSpace-generated DOIs into a new "dc.identifier.doi" field. This would standardize their location, and also keep them separate from Handles (which are stored in "dc.identifier.uri"). The full details of the proposal can be found in this ticket: https://jira.duraspace.org/browse/DS-3708 

The Developer Team notes that the "dc.identifier.doi" field is another non-standard DC field. But they would like to simply keep DOIs in a location alongside other identifiers. However, they hope that, in the future, a Metadata Working Group (or similar) could be established to help the Developer Team determine the DSpace metadata best practices going forward.

*it would happen automatically during the upgrade process, and wouldn't be configurable.  But, they would only automate for DOIs that *DSpace generated* (they can determine this based on data in the 'doi' database table).  So, any other DOIs you are storing which are not generated by DSpace would be kept where they currently exist.

Preparing for the call

Please review the DCAT Google Group thread "Proposal to move all DSpace-generated DOIs to dc.identifier.doi" and tickets:

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3708
 
Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-2199
Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3472

In preparation of the call, you could do the following:

  • Share any questions you may have
  • Think about local institution code implications
  • Share how you are using DOIs currently (what systems/plugins you are using, what fields you are using, how you are displaying DOIs, differences for minting versus manually assigned, etc.)

Meeting notes


Call Attendees

 To be determined

Preparing for the call

Meeting notes