You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Date & Time

  • December 12th 16:00 UTC/GMT - 11:00 ET

Dial-in

We will use the international conference call dial-in. Please follow directions below.

  • 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 and feedback on the Proposal to move all DSpace-generated DOIs to dc.identifier.doi Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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 "dc.identifier.uri" (alongside Handles), in "dc.identifier", or in "dc.identifier.doi".  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 (for DSpace master code) "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 (for the master code). 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:

Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

In preparation for 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

  • No labels