On Tue, May 21, 2013 at 05:31:59PM +0200, helix84 wrote:
> On Tue, May 21, 2013 at 4:50 PM, Mark H. Wood <[email protected]> wrote:
> > On Tue, May 21, 2013 at 03:31:37PM +0200, helix84 wrote:
> >> 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.
> >
> > Well, the ORCID ID is metadata about an item, binding it to external
> > ORCID metadata which binds the ID to (one of) the item's creator(s).
> > ORCID.org is managing the author metadata in this case.
> 
> OK, I didn't know that there are also ORCID IDs for items. Can you
> point me to some basic information about this?

There aren't.  An ORCID ID is a unique opaque identifier for a person.
The way it would be used in DSpace is to uniquely identify authors,
contributors, etc. of an item.  So the ID itself is metadata about the
item (showing its relationship to a person), the same way that
dc.contributor.author is, but it's a different type with different
syntax and semantics.  The ORCID organization holds *other* metadata
which identifies an ORCID ID with a person, and DSpace's use of the ID
would be a reference to external metadata about that person.

The ID itself, when stored in DSpace, would not be "about" the person;
it's an opaque token that someone could use to retrieve (from ORCID)
information about the person, or simply to select a subset of holdings
associated with a specific but unnamed person.  It describes the item.

(There has got to be a better way to say this.  I did say I'm not
really a metadata person.)

> > I doubt, as you do, that DC has any place for ORCID IDs, which are
> > unique identifiers with URL syntax.
> 
> In that case, I'd suggest to add a new metadatafield dc.identifier.orcid.

But I don't think DCMI defines such a type.  So it shouldn't be shoved
into the DC namespace.  Doing that would lumber a DSpace instance with
metadata which gives the appearance of being standardized but is
globally uninterpretable.  Conforming implementations of DC
specifications should consider this type invalid and ignore it or flag
an error.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Machines should not be friendly.  Machines should be obedient.

Attachment: signature.asc
Description: Digital signature

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

Reply via email to