1. I will be storing DOIs in dc.identifier.doi, as soon as I get it set up. (I am new to DOI registrations.) I am temporarily storing them in the same field as handles.
2. Other DOIs – my plan is to put these in a dc.relation field. I see that UMN did that, too. When doing retrospective assignment of DOIs, I found that a dataset I have is also in Dryad. I need to come up with a better plan, but in the meantime I added: dc.relation Also available in Dryad: https://doi.org/10.5061/dryad.9bg43. 3. I see advantages to having different persistent identifiers in different fields. a) Easier to manipulate the data, if needed, in the DSpace instance of when the data is exported. b) The display of the fields in a local repository can be customized with different labels, order of display changed, etc. There was a discussion on the DCAT list last fall about DOIs. This ticket was referenced: https://jira.duraspace.org/browse/DS-3708: … it is proposed that we move all DOIs generated by DSpace into a new field 'dc.identifier.doi'. This will resolve the discrepancy between the DataCite and EZID DOI generation code (DS-2199<https://jira.duraspace.org/browse/DS-2199>), disentangle generated DOIs from Handles, and consistently separate generated DOIs from user-entered DOIs. Thereafter, dc.identifier will hold all user-supplied identifiers; dc.identifier.doi will hold all DSpace-generated DOIs; and dc.identifier.uri will hold all Handles. This will make storage of identifiers more consistent, prevent confusion of generated and submitted identifiers, and make it simpler to work with generated identifiers since each field will hold only one type. Felicity Felicity Dykas Head, Digital Services Department MU Libraries University of Missouri--Columbia (573) 882-4656 [email protected] From: [email protected] <[email protected]> On Behalf Of Jere Odell Sent: Tuesday, October 09, 2018 2:13 PM To: DSpace Community <[email protected]> Subject: [dspace-community] Best Practices in DSpace DOIs and Dublin Core? 1. If your DSpace instance is generating DOIs and storing them in the DSpace Dublin Core metadata, how are you doing this? To be specific, are you (A) storing the DSpace DOI in the same metadata field as the DSpace handle? dc.identifier.uri? (See for example: https://conservancy.umn.edu/handle/11299/188066 ... which stores both the handle and the doi in dc.identifier.) Or, are you (B) using a different metadata field to store the DSpace DOI? (One might use dc.identifier.doi, for example? But I haven't seen this used for this purpose yet.) 2. With the above in mind, where do you store non-DSpace DOIs? For example, if the work has a doi that resolves to a different site (a CrossRef journal doi, probably), do you store that external doi in dc.identifier.doi? Or do you store it in a different metadata field, such as ... dc.relation.isversionof? 3. Finally, are you aware of any downstream issues that might result from choosing to store the DSpace DOI in the same DC field with the handle? Will sites that harvest or crawl our metadata fail to see the DOI? Jere Odell Scholarly Communication Librarian IUPUI ScholarWorks https://scholarworks.iupui.edu/ -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
