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]. 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.
