As an additional note on this issue, both NYU and LC have already had some
discussions regarding a technical metadata extension schema for METS that
covers most all of the required information you mention below. We would
base this on the SMPTE Metadata Dictionary, and have already approached SMPTE
to inquire whether they're planning on implementing an XML schema version of
their metadata dictionary. If they're not, and assuming they don't have
we'll probably do one ourselves and make it publicly available for use with
an enhanced version of LC's A/V prototyping project technical metadata for
At 09:48 PM 12/5/2002 +0100, you wrote:
>For MODS record with online data, it will be very usefull to have more
>Especially for doing a search with ZING SRW/SRU.
>In my company, we use a lot digital video (we build digital video servers).
>A big problem for us, is to find a video in the good format :
> * MPEG 1, MPEG 2 system, MPEG 2 transport, MPEG 4 ...
> * PAL / NTSC (25 fps / 30 fps)
> * File size
> * Duration
> * Black and white, color
> * resolution : 800/600, ...
> * Aspect ratio : 4:3, letterbox, ...
> * dumb, dumb with piano score, ...
> * How many audio tracks, and for each track :
> * PID
> * language
> * MPEG 3, ...
> * Which sound track is the original ?
> * How many subtitle/closed caption, and for each subtitle :
> * ID ?
> * Language
> * Rights (copy/download, print, modify, personnal or commercial use, ...)
>If the MODS records describe an audio file, some of the video parameters
>are the same (duration, copyrights, ...).
>There is some similarities for still image, maps ...
>For all theses contents it's possible to have alternate format :
> * text format (pdf, TEI, docbook, ...) for a scanned printed text or a
> * small picture for a gallery view.
> * small picture of the jacket for a book, DVD, video, CD, ...
> * (see <http://www.amazon.com>www.amazon.com for example. This type of
> view could be very usefull for children, or even everybody who search the
> real book in the library)
> * reduced size/quality for download.
> * alternate digital format (wav, mp3 for audio ; mpeg 4, mov, real for
> video ; tiff, jpeg, png for still pictures ...)
>Of course some of these metadata are coded inside the file, but there are
>not accessible directly by the IR server.
>So these MODS metadata will be usefull for a user in your (digital)
>library searching for black&white movie with subtitles in french.
>But it could be difficult to define some elements for digital contents in
>Or the pitfall is to reinvent the wheel ?
>One solution is use specific metadata inside MODS elements, like MATHML or
>SVG modules for DOCBOOK.
>There is also extension schemas for METS :
>METS could embeded MODS, but i understood that METS is used only to
>backup/move data from/to servers.
>Not for IR in (SRW/SRU) servers.
>I'am right ?
>All this speech (i apologize if i was too long) was for the (near?) MODS
>Curently, i found a problem with the MARC21 to MODS conversion :
>I "play" with the OAI server of the american memory.
>With a movie about the Roosevelt Dam near Phoenix, the digital video is in
>All theses parts are discribed in the MARCXML record (field tag 856,
>subfields $f), but they are loosed in the MODS record.
>MARCXML RECORD :
><datafield tag="856" ind1="7" ind2="">
> <subfield code="d">trmp</subfield>
> <subfield code="f">4095s1</subfield>
> <subfield code="f">4095s2</subfield>
> <subfield code="f">4095s3</subfield>
> <subfield code="g">urn:hdl:loc.mbrsmi/trmp.4095</subfield>
> <subfield code="u">http://hdl.loc.gov/loc.mbrsmi/trmp.4095</subfield>
> <subfield code="q">m</subfield>
> <subfield code="2">http</subfield>
>MODS RECORD :
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]