Hi Ann, I don't intend you to discourage you from using ORCID, on the contrary. But I have to warn you that DSpace doesn't really provide any special support for it.
You're asking about a suitable metadata field for storing it, but you have to realize that currently DSpace supports metadata only on items, not on authors. For this reason I also doubt you will any standardized DC field to store it. You could store ORCIDs the same way as we store authors of an item - as a sequence of values of the same field. I have anecdotally verified that the order of values will remain the same when you read them back. In the light of the proposed updates to the DC registry, you should most likely use a custom metadata field in your own namespace for this (i.e. not in dc). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
