http://www.loc.gov/standards/mets/test/00000009.xml Library of Congress METS Profile for Recorded Events [Draft] The Library of Congress Recorded Events METS Profile specifies how METS documents representing recorded events should be encoded. The term "recorded event" includes both audio and video recordings. This profile will typically be used for non-commercial recordings of events such as concerts, lectures, or radio and television broadcasts. A distinctive feature of the profile is that it represents the physical structure of a given audio or video program as a simple sequence of time-based segments. These segments are expressed in the METS structMap section of the METS document. There is no attempt made to express the physical components (e.g. tape, disc, side, track, etc.) of the original carrrier. 2006-01-12T17:31:00 Morgan V. Cundiff Network Development and MARC Standards Office, Library of Congress
101 Independence Avenue, Washington DC, 20540
 No related profiles. Metadata Object Description Schema (MODS) http://www.loc.gov/mods/v3/ Premis http://www.loc.gov/standards/premis

It is recommended that the content data used in the MODS section of a METS document conform to AACR2 to the extent that it applies.

 Library of Congress Subject Headings Library of Congress

Controlled subject headings used in the MODS section of a METS document must be formulated according to the Library of Congress Subject Headings (LCSH).

 Library of Congress Classification Library of Congress http://www.loc.gov/catdir/cpso/lcc.html NACO Authority File Library of Congress http://authorities.loc.gov/

Controlled name and title headings used in the MODS section of a METS document must be formulated according to the NACO Authority File.

 MARC Country Codes Library of Congress http://www.loc.gov/marc/countries/

Country codes used in the MODS section of a METS document must use MARC country code list.

 ISO 639-2 Language Codes Library of Congress http://www.loc.gov/standards/iso639-2/

Language codes used in the MODS section of a METS document must use ISO 639-2 bibliographic codes.

 MARC Relator Codes Library of Congress http://www.loc.gov/marc/relators/

Relator codes or terms used in the MODS section of a METS document must use MARC relator list.

 Target Audience Codes Library of Congress http://www.loc.gov/marc/sourcecode/target/

Terms used in the MODS section of a METS document must use the MARC target audience list.

 MARC Code List for Organizations Library of Congress http://www.loc.gov/marc/organizations/

Source codes used in the MODS section of a METS document must use MARC organization list.

The METS root element must have an attribute PROFILE="http://www.loc.gov/mets/profiles/00000009.xml".

A document must contain one and only one Descriptive Metadata Section (dmdSec) with a wrapped (mdWrap) MODS bibliographic record. The mods element must have an ID attribute.

If the recorded event contains subparts that are to be described, the MODS element must contain one Related Item (relatedItem) element for each sub-part. An example of a sub-part might be a recorded concert with a relatedItem describing each musical work. Each relatedItem element must have an ID attribute and a type="constituent" attribute.

If a musical work (as is in the previous example) or any other kind of event segment, has logical sub-parts of its own, the logical structure of those sub-parts may in turn be represented with relatedItem type="constituent" child elements. Examples of logical sub-parts are the movements of a musical work, the acts and scenes of a dramatic work, etc. The logical structure of a work (or any other kind of program segment) will thus be represented as a heirarchy of relatedItems type="constituent". All relatedItem type=constituent" elements must be given an ID attribute.

Note also that a recorded event might be subdivided into sub-parts for purely arbitrary reasons (rather than logical sub-parts based on the content of the recorded program). The typical example of this is breaking a long program into shorter segments based on arbitrary time durations. As with logical sub-parts, relatedItems may be used to represent these event segments.

A METS document may optionally contain preservation-related metadata that is expressed using the PREMIS schemas. PREMIS data can be associated with either the entire object (i.e. data that is applicable to all component files), which is, in PREMIS terms, considered to be at the level of the object category "representation", or PREMIS data may associated with individual files. The following brief example shows a possible encoding for the date of a preservation "event" (i.e. the date of digitization) for an audio file. Note that (as of this writing) PREMIS is still very new, and that best practices for its use with METS have not yet emerged.

 File Section

The content files referenced by the fptr elements (in the structMap) must point to the appropriate files in the File Section (fileSec). The highest quality or "master" files must be contained in File Group (fileGrp) elements with a USE="MASTER" attribute. File (file) elements must have a MIMETYPE attribute with appropriate value and File Location (FLocat) elements must have a LOCTYPE attribute with appropriate value. The profile makes no further requirements regarding the fileSec element. The example document in Appendix 1 provides a more complete example of Library of Congress practice (see the XML version of this document).

The physical structure of the recorded event will be represented in the Structure Map (structMap) section of the METS document. The document will have one and only one structMap. The structMap element must contain one and only one top level div TYPE="re:recordedEvent" child element. The top-level div element of the structMap must have a DMDID attribute that points to the mods element.

The div TYPE="re:recordedEvent" element must contain one or more div TYPE="re:segment" elements. The div TYPE="re:segment" elements represent ordered, time-based segments of the recorded program (i.e. the document order of the div TYPE="re:segment" elements must reflect the audio or video program order). A div TYPE="re:segment" element has no furthur semantic meaning. The entire recorded event object will always be expressed as a sequence of one or more segments.

Each div TYPE="re:segment" elements must contain either one div TYPE="re:audio" child element or one div TYPE="re:video" child element.

In the case where there is only one div TYPE="re:segment" element (as in Example 5) the DMDID attribute must also point to the mods element.

In the case where there are more than one div TYPE="re:segment" elements (as in Example 6) the DMDID attributes must must point to the corresponding relatedItem type="constituent" elements in the MODS record. In some cases the relatedItem type="constituent" elements represent only arbitrary segments of the recorded event (perhaps based only on time duration) but where navigation of the segments is desirable. This is the case in the following example.

In other cases, the segments may be associated with the appropriate relatedItem elements where the relatedItems provide a more thorough description of the logical structure (i.e. the program content) of the recorded event. This is the case in the following example. Note that this approach provides a method for correlating the two differing hierarchical representations (logical and physical) of the recorded event object.

A recordedEventObject may also contain text and image content in addition to audio or video content. A text file may exist as a transcription of the audio program content, or may exist as a transcription of text that appears on the original container, or, in any document that is inserted in the container. (These include the kind of documents usually described as "accompanying material", e.g. a concert program, a curator's notes, a recording engineer's notes, etc.). Images may exist as scans of the original container, or as scans of an inserted document.

The profile thus provides for the following possibilities: 1) A text transcription of an entire recordedEvent, 2) A text transcription of an audio or video segment, 3) A text transcription of material from the original container, 4) A text transcription of an inserted document, 5) Images of the container, 6) Images of an inserted document, and 7) An illustrative image. Each of these will be demonstrated in the examples that follow.

A text transcription of an entire recordedEvent is expressed as a div TYPE="re:text" element. In this case the div TYPE="re:text" element will occur as a child element of the div TYPE="re:recordedEvent" element as in Example 8.

There may also exist text transcriptions for each audio or video segment of a multi-segment recordedEvent. In this case the div TYPE="re:text" element will occur as a child element of the div TYPE="re:segment" element as in Example 9.

If there exists a text file derived from the original container, then the div TYPE="re:recordedEvent" element will contain one div TYPE="re:container" element. The div TYPE="re:container" element will contain one div TYPE="re:text" element as in Example 10.

If there exist image files derived from the original container, then the div TYPE="re:recordedEvent" element will contain one div TYPE="re:container" element. The div TYPE="re:container" element will in turn contain one or more div TYPE="re:containerPart" elements. The div TYPE="re:containerPart" elements will each contain one div TYPE="re:image" element. Note that there is no prescribed order for the div TYPE="re:containerPart" elements as far as the profile is concerned. The div TYPE="re:containerPart" elements may be arranged in any order according to local practice. The div TYPE="re:containerPart" elements may optionally contain a LABEL attribute with additional structural information.

In the case of a text transcription derived from an inserted document, the div TYPE="re:recordedEvent" element will contain one or more div TYPE="re:insertedDoc" elements. The div TYPE="re:insertedDoc" element will contain a div TYPE="re:text" element as in Example 11.

In the case of images derived from the original container, the div TYPE="re:container" element will contain one div TYPE="re:imageSet" element. The div TYPE="re:imageSet" element will contain one div TYPE="re:image" element for each scanned image as in Example 12. Note that there is no prescribed order for the images as far as the profile is concerned. The images can be arranged in any order according to local practice.

In some cases it may be desirable to create a single arbitrary image for the purpose of illustration. A typical example of this is using a still image captured from a video program to serve as an illustration when displaying the bibliographic information for the video in question. In this case the div TYPE="re:recordedEvent" element will contain one div TYPE="re:illustration" element which in turn will contain one div TYPE="re:image" element.

The following example provides an illustration of all the possibilities for building a structMap. Note that the div elements that indicate content type (i.e. div TYPE="re:audio", div TYPE="re:video", div TYPE="re:text", and div TYPE="re:image" are always leaf nodes. These div elements will always contain an fptr child element.

 Audio Files

The master audio files referenced by conforming documents must be in WAVE Audio File Format. See Digital Formats for Library of Congress Collections: WAVE Audio File Format at http://www.digitalpreservation.gov/formats/fdd/fdd000001.shtml.

 Video Files

It is recommended that master video files referenced by conforming documents be in MPEG-2 Video Encoding. See Digital Formats for Library of Congress Collections: MPEG-2 Video Encoding at http://www.digitalpreservation.gov/formats/fdd/fdd000028.shtml.

 Still Image Files

The master image files referenced by conforming documents must be in TIFF Revision 6.0 format. See Digital Formats for Library of Congress Collections: TIFF, Revision 6.0 at http://www.digitalpreservation.gov/formats/fdd/fdd000022.shtml.

 Text Files

Master text files referenced by conforming documents must be in XML format. See Digital Formats for Library of Congress Collections: XML (Extensible Markup Language) at http://www.digitalpreservation.gov/formats/fdd/fdd000075.shtml.

 Great conversations: the composers Istomin, Eugene Host Zwilich, Ellen Taaffe Interviewee Rorem, Ned Interviewee Perle, George Interviewee Lieberman, Lowell Interviewee Danielpour, Richard Interviewee Babbitt, Milton Interviewee Rosen, Peter Producer moving image New York Peter Rosen Productions, Inc. 2005 monographic
videorecording
access 1 digibeta videotape; duration: 56 min., 4 sec. reformatted digital adult Composers Milton Babbit, Richard Danielpour, Lowell Liebermann, George Perle, Ned Rorem, and Ellen Taaffe Zwilich join Istomin at the American Academy of Arts and Letters in New York to discuss and argue about the strong feelings and controversies surrounding modern contemporary music and the challenges that programming their music presents. The composers talk about their lifelong struggles to achieve recognition, but express pride in their collective status as representatives of the avant-garde. In opening credits: "The Library of Congress, Washington, DC, presents." Filmed at the American Academy of Arts and Letters, New York. "Program two" in the series of Great conversations. Additional credits: for the Music Division of the Library of Congress: Jon Newsom, Chief; Jan Lauridsen, Asst. Chief; Ruth Foss, Program Specialist. In credits: "produced for the Library of Congress by Peter Rosen Productions, Inc." Copyright Library of Congress. This program was made possible through the courtesy of Eugene Istomin. Artists' appearances are courtesy of themselves: Milton Babbitt, Richard Danielpour, Lowell Lieberman, George Perle, Ned Rorem, and Ellen Taaffe Zwilich. Opening credits; and Roots moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 5 min., 10 sec. reformatted digital Opening credits. Istomin introduces his guests and begins a conversation on the European roots of American music. The composer moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 7 min., 11 sec. reformatted digital Istomin’s guests reflect on how they decided to become composers. Twentieth-century masterpieces moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 3 min., 14 sec. reformatted digital Istomin’s guests discuss their choices for the six greatest works written after the turn of the twentieth century. Appreciating different works moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 3 min., 25 sec. reformatted digital Rorem, Liberman, Danielpour, and Babbit talk about works that have vastly differing aesthetics. Eclectic programming moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 3 min., 31 sec. reformatted digital Istomin and his guests speak about eclectic programming. Performers moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 6 min., 30 sec. reformatted digital Istomin’s guests discuss the relationships and qualities they desire in musicians who perform their works. Accessibility moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 9 min., 57 sec. reformatted digital Istomin and his guests comment on the accessibility and popularity of twentieth-century classical music. Language and tonality moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 9 min., 18 sec. reformatted digital Istomin and his guests speak about understanding tonal, atonal, and serial music. The avant-garde; and closing credits moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 5 min., 14 sec. reformatted digital Istomin and his guests make observations on obsolescence and the avant-garde as well as perceived differences between American and European contemporary composers. Closing credits. Experimental music moving image New York Peter Rosen Productions, Inc. 2005
video
access Duration: 2 min., 34 sec. reformatted digital Istomin and his guests discuss experimental music. 200031103 23598 Music Division DLC IHAS 051118 loc.natlib.ihas.200031103
[Senator Smith speech to Rotary Club, 1956-12-12]
[Library of Congress Music Division concert, 2003-02-12] Millennium designs Shapey, Ralph, 1921- Quartets, strings, D major no. 3, op. 18, no. 3, D major Beethoven, Ludwig van, 1770-1827
[Library of Congress Music Division concert, 2003-02-12] Millennium designs Shapey, Ralph, 1921- Quartets, strings, D major no. 3, op. 18, no. 3, D major Beethoven, Ludwig van, 1770-1827 Allegro Allegretto Rondo: Allegro commodo
[Library of Congress Music Division concert, 2003-02-12] Part 1 Part 2 Part 3
[Senator Smith speech to Rotary Club, 1956-12-12] LCfileID fileID0001 file LCcaptureID captureID0001 digitize 2005-10-06T00:00:00.001
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12] Part 1 Part 2 Part 3
[Library of Congress Music Division concert, 2003-02-12] Millennium designs Shapey, Ralph, 1921- Quartets, strings, D major no. 3, op. 18, no. 3, D major Beethoven, Ludwig van, 1770-1827 Allegro Allegretto Rondo: Allegro commodo
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12] Part 1. Part 2.
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12]
[Senator Smith speech to Rotary Club, 1956-12-12]