LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

METS Home

METS Home

METS  March 2019

METS March 2019

Subject:

SV: CONTENTIDS example; where are you putting unique external IDs?

From:

Sigfrid Lundberg <[log in to unmask]>

Reply-To:

Metadata Encoding and Transmission Standard <[log in to unmask]>

Date:

Mon, 25 Mar 2019 09:04:28 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (95 lines)

Dear Teresa & Robert (and anyone else),

I really think one should stick to having links to files in the file section. I'm well aware of the fact that it requires one of those ID/IDREF constructs in XML and that might be regarded as "difficult", on the other hand: Once implemented that way you a METS object where you could replace that file section while keeping the rest intact -- given that you keep your ID (or xml:id) attributes persistent. 

The ID or xml:id of an element in an XML document should be regarded with as much respect as a PURL or a DOI or an URN, changing an xml:id might cause a 404.

From my perspective the best place to put links to components is in mets:FLocat/@xlink:href as in Robert's example.

If you want really unique ID feel free to use UUIDs (making sure that they start with a a-z or A-Z something). I once got into problems using the ordinary generate-id() xpath function as implemented in gnome libxml and it turned out not unique if run multiple times. Therefor I now always a uuid (even if it several bytes too long for the purpose).

If you put those links into the structMap you could just as well use DIDL rather than METS (superior format (again from my point of view).

Yours,

Sigfrid






________________________________________
Fra: Metadata Encoding and Transmission Standard [[log in to unmask]] på vegne af Robert Stephan [[log in to unmask]]
Sendt: 23. marts 2019 13:25
Til: [log in to unmask]
Emne: [METS] AW: CONTENTIDS example; where are you putting unique external IDs?

Dear Teresa,

at Rostock University Library we use Persistent URLs in CONTENTIDS.
In one of our digitization projects we also decided to use UUIDs as object ids.
Since we host our own PURL-Resolver, we could simply append the UUIDs to a URL. For elements of the internal structure we combine the UUID of the object with the ID of the DIV element.

One example METS can be found here:
http://doro.uni-rostock.de/depot/darl/2c840a7e-1a23-4118-9302-0952eafd21e0/2c840a7e-1a23-4118-9302-0952eafd21e0.repos.mets.xml

In your case your right. You cannot put the UUID into the ID-attribute. On a conceptual level nobody can forbid the use of  UUID for IDs. If they are gloabally unique they are also unique within the XML document. But technically UUIDs do not comply with the XML-ID-Type (e.g. IDs cannot start with a number and cannot contain „:“) (https://www.w3.org/TR/xmlschema11-2/#ID)

In your case I see several possibilities to convert the UUID-string into a URI:


a)  Output them as URN (wich is a valid URI) by using the prefix: „urn:uuid:“:
The URN-UUID-scheme is definied in https://tools.ietf.org/html/rfc4122.

e.g.:   urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6


b)      Define a local URL-Prefix like http://uuid.getty.edu/
If you do so, you can „claim“ the UUIDs as definied by your institution and later you could decide to implement your own resolver which leeds to the presentation of the object in your digital library.


c)       Alternatively you can define metadata sections (mets:dmdSec) for each div and link them via dmdid attribute.
Within this metdata section you can use MODS or another metadata schema to store the UUID.

Kind regards,

Robert Stephan


--------------------------------------------------------------------------------
Dipl.-Inf. Robert Stephan
- Digitale Bibliothek -

Universitätsbibliothek Rostock
18051 Rostock
Tel.: +49 (381) 498 8625

[log in to unmask]
www.ub.uni-rostock.de



Von: Metadata Encoding and Transmission Standard <[log in to unmask]> Im Auftrag von Teresa Soleau
Gesendet: Samstag, 23. März 2019 00:38
An: [log in to unmask]
Betreff: [METS] CONTENTIDS example; where are you putting unique external IDs?

Hello,

We are trying to find a place in the METS structMap divs to put UUIDs referring to unique physical objects that have been digitized (like a barcode for the physical object) and CONTENTIDS seems like a good element to use (since the ID element is only supposed to refer to links internal to the METS, right?) but I’d like to see an example of the CONTENTIDS values. The type is URI, not string.

Anyone adding this type of information to your METS documents and could share where you’ve added it?

Thanks,
~Teresa Soleau


Digital Preservation & Library Systems Manager
Collection & Content Management Systems
J. Paul Getty Trust
1200 Getty Center Drive
Los Angeles, CA 90049-1688
[log in to unmask]<mailto:[log in to unmask]>
310.440.7601

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2023
April 2023
March 2023
January 2023
November 2022
December 2021
November 2021
November 2020
October 2020
September 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
May 2019
April 2019
March 2019
November 2018
October 2018
September 2018
July 2018
June 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
January 2017
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
January 2016
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
January 2014
December 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
February 2013
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
March 2012
February 2012
January 2012
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager