On Thursday, October 11, 2018 at 2:17:26 PM UTC-4, Emilio Lorenzo wrote: > > I think the assignation of DOIs to whatever field, is possible, just some > extra lines of codes would solve it > > 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 > >
Indeed, that must be local code modifications. Stock DSpace code does not define a dc.identifier.doi field and would not accept it. dc.identifier.uri is hard-coded into the org.dspace.identifier.DOIIdentifierProvider. (Also, this provider is letting the persistence layer generate the suffix, probably via a DBMS sequence generator -- I didn't follow it all the way down. On a stock 5.4 instance I can see in the database that the Handle and DOI suffixes are unrelated.) -- 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.
