LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


METS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

METS Home

METS Home

METS  July 2002

METS July 2002

Subject:

Re: Media File Location

From:

Jerome McDonough <[log in to unmask]>

Reply-To:

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

Date:

Mon, 1 Jul 2002 14:35:35 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (88 lines)

At 05:23 PM 6/26/2002 +0200, Laurent Duplouy wrote:
>I've got a problem (other than my bad english) :
>How to locate file store on differents media in METS ?

The approach you've taken is actually a reasonably sensible one. In cases
where there are multiple instances of the same data file on different media,
you'd want a METS:file element for each instance. For instances that are
not online, you could either do what youv'e done, use a file:// URL, or
use some type of persistent identifier (URN?) with an online resolution
mechanism
that would inform people how to access data files that aren't online.

It looks like you also want to store technical metadata about the media use,
in which case you're pretty much on target with your approach. Have a single
techMD element for each different media type, each with its own XML ID
(say "AMD1" for delivery CD, "AMD2" for archive CD, and "AMD3" for web
accessible).
Then each METS:file element could reference the appropriate admin metadata,
i.e., all files on delivery CDs would include "AMD1" in their "ADMID"
attribute, all
archive CD files would reference "AMD2", etc.

In short, it looks like you're on the right track to me.

>Ours image files are on differents storage areas : first on a delivery CD for
>control, second on magnetic disc for consultation (http:\\gallica.bnf.fr) and
>third on a archive CD (Century-disc) for preservation.
>Because amdSec or fileSec seems to not be provide for, we have to create new
>element or attribute, like :
>
>first way, use administrative metadata :
>
><METS:amdSec>
> <METS:techMD ID="ADM1">
> <METS:mdWrap MDTYPE="OTHER">
> <METS:xmlData>
> <IMD>
> <IMGSTORAGE ID="CD01">
> <type>CenturyCD</type>
> <refmedia>90100034</refmedia>
> </IMGSTORAGE>
> <IMGSTORAGE ID="CD02">
> <type>CD-R</type>
> <refmedia>20000738</refmedia>
> </IMGSTORAGE>
> <IMGSTORAGE ID="MG01">
> <type>web</type>
> <refmedia>gallica.bnf.fr</refmedia>
> </IMGSTORAGE>
> </IMD>
> </METS:xmlData>
> </METS:mdWrap MDTYPE="OTHER">
> </METS:techMD ID="ADM1">
></METS:amdSec>
>
>second way, use file section :
>
><METS:fileSec>
> <METS:file ID="FID20" MIMETYPE="image/tiff" ADMID="ADM5">
> <METS:FLocat LOCTYPE="OTHER" typemedia="CenturyCD"
> refmedia="90100034"
> xlink:href="file://20102355.DIR/20000032.TIF" />
> </METS:file>
> <METS:file ID="FID21" MIMETYPE="image/tiff" ADMID="ADM5">
> <METS:FLocat LOCTYPE="OTHER" typemedia="CD-R" refmedia="90100034"
>xlink:href="file://20028023.DIR/20000032.TIF" />
> </METS:file>
> <METS:file ID="FID22" MIMETYPE="image/tiff" ADMID="ADM5">
> <METS:FLocat LOCTYPE="URL"
>xlink:href="http://gallica.bnf.fr/scripts/ConsultationTout.exe?E=32&O=N028023"
>/>
> </METS:file>
><METS:fileSec>
>
>Want do you think about this?
>
>Thanks.
>
>Laurent DUPLOUY

Jerome McDonough
Digital Library Development Team Leader
Elmer Bobst Library, New York University
70 Washington Square South, 8th Floor
New York, NY 10012
[log in to unmask]
(212) 998-2425

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager