in (dspace 5) http://85.152.11.156:7172/handle/10317/4931?show=full you can show that the system is automatically assigning dois to new records (well, you have to trust that this is the process we are following) and via cron jobs the system is able to retrospectively assign dois to archived objects
dc.identifier.uri is used for the handle dc.identifier.uri: http://hdl.handle.net/10317/4931 and
dc.identifier.doi is used for DOIs dc.identifier.doi ---> 10.31428/10317/4931 (note that following crossref recomendations the doi suffix re-user the main indicator, the handle
regards Emilio El 11/10/2018 a las 17:59, Jere Odell escribió:
Claudia, Mark, and friends,I think there's mismatch between how librarians think metadata should be applied and how DSpace can auto-register (DataCite) DOIs. If Mark and Claudia are correct, DSpace generates DOIs in dc.identifier.uri and [cannot/is not currently able to] register DOIs from other Dublin Core fields ... such as dc.identifier.doi.If I understand correctly, DSpace was designed to issue one persistent identifier ... the handle. DOIs were a more recent request and, for now, if we want to auto-generate DOIs we have to store them in dc.identifier.uri. Is that correct?If so, that puts those of us that want to assign DOIs to our DSpace records in a difficult spot ... we must choose between a) manual methods of registering the DOI or b) rely on a less-than-optimal metadata practice.Am I missing something? JereOn Thu, Oct 11, 2018 at 9:37 AM Claudia Jürgen <[email protected] <mailto:[email protected]>> wrote:Hi, as Mark pointed out the self generated doi's are in dc.identifier.uri. If you have secondary publications and use the doi service I would put the original doi of the publication in another field like dc.identifier.doi in order to be able to seperate them in crosswalks etc. Hope this helps Claudia Jürgen Am 11.10.2018 um 15:33 schrieb Mark Wood: > On Tuesday, October 9, 2018 at 3:13:03 PM UTC-4, Jere Odell wrote: >> 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.) >> >> > If your DSpace instance is generating DOIs then it is storing them in > dc.identifier.uri. This is not configurable. > -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 [email protected] <mailto:[email protected]> www.ub.tu-dortmund.de <http://www.ub.tu-dortmund.de> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.-- All messages to this mailing list should adhere to the DuraSpaceCode of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to a topic in the Google Groups "DSpace Community" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-community/Jz4VlgPuK8w/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected] <mailto:dspace-community%[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] <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.
<<attachment: elorenzo.vcf>>
