|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
In The DSpace metadata you should try to use the URL form. This is the DOI communities recommendation. note doi:xxx never was approved as a registered URI, likewise hdl:..., I would recommend avoiding non-resolving versions of any identifiers in your metadata.
On Wed, Oct 2, 2013 at 1:57 PM, helix84 <heli...@centrum.sk> wrote:
http://dx.doi.org/10.1234/567
or the new shortened version
http://doi.org/10.1234/567
It could be stored internally (like handle table) however one desires.
The name of the metadata field is dependent on the resource the DOI refers to you see lots of descriptions in DCMI terms like
"Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system."
So I assume you mean for DSpace purposes in identifying the current item, it'd be dc.identifier or dc.identifier.uri or dc.identifier.doi... qualification is upto the implementer.
Best,