MODS ULA 2006

If not DC, then MODS? A look at the Metadata Object Description Schema: 

If not DC, then MODS? A look at the Metadata Object Description Schema Cheryl Walters Kayla Willey ULA Annual Conference St. George, Utah May 17, 2006

Useful Articles: 

Useful Articles McCallum, Sally. An Introduction to the Metadata Object Description Schema (MODS). Library Hi-Tech, v. 22, no. 1 (2004): 82-88 Guenther, Rebecca S. Using the Metadata Object Description Schema (MODS) for resource description: guidelines and applications. Library Hi-Tech, v. 22, no. 1 (2004): 89-98 Guenther, Rebecca S. MODS: The Metadata Object Description Schema. portal: Libraries and the Academy, v. 3, no. 1 (2003): 137-150

Useful resources & websites : 

Useful resources & websites MODS Official website: http://www.loc.gov/standards/mods/  METS Official website: http://www.loc.gov/standards/mets/  DLF MODS Implementation Guidelines for Cultural Heritage Materials: http://www.diglib.org/aquifer/DLF_MODS_ImpGuidelines_ver4.pdf Best Practices for Shareable Metadata http://oai-best.comm.nsdl.org/cgi-bin/wiki.pl?PublicTOC

What MODS is…: 

What MODS is… MODS = Metadata Object Description Schema It is a MARC21 compatible XML schema for descriptive metadata only Created by the same folks that brought us MARC (Library of Congress) Version 1: open to public review in 2002 Version 3.1 is most current version: http://www.loc.gov/standards/mods/v3/mods-3-1.xsd

… What MODS is: 

… What MODS is MODS descriptive records can be contained inside METS record MODS is a MARC21 derivative, simpler than MARC21 but compatible Converting a MARC21 record to MODS and back again to MARC21 may lose specificity of tagging or data MODS is richer than Dublin Core, more compatible with library data than ONIX, more end user friendly than MARCXML, and simpler than MARC.

MODS User Guidelines: top level elementshttp://www.loc.gov/standards/mods/v3/mods-userguide.html: 

MODS User Guidelines: top level elements http://www.loc.gov/standards/mods/v3/mods-userguide.html

MODS User Guidelines explain attributes for each element: 

MODS User Guidelines explain attributes for each element

Example of element and attribute: 

Example of element and attribute <genre authority = “aat”> portraits </genre> Element Element Attribute Controlled vocabulary stipulated as the “authority” Value (i.e. Controlled term)

… and show & explain all sub elements: 

… and show & explain all sub elements

Example of element and sub element: 

Example of element and sub element <originInfo <place> <placeTerm type=“text”>Ithaca, N.Y. </placeTerm> Element Sub element Sub elements Attribute Value (i.e. Place name) Text stipulated as the “type”

… sub elements clarify, explain source of terms/codes, or provide instructions for data manipulation : 

… sub elements clarify, explain source of terms/codes, or provide instructions for data manipulation

Guidelines give lots of examples…: 

Guidelines give lots of examples…

MODS features: 

MODS features Uses natural language tags instead of numeric tags and avoids abbreviations for easier understanding MODS: <title> Sound and fury : </title> <subTitle> the making of the punditocracy /</subTitle> </titleInfo> MARC: 245 10 Sound and fury : |b the making of the punditocracy / Consolidates data from different MARC tags Publishing info in MARC tags 008, 044, 260 subfields a,b & c, 033, 250, 310, 321 pulled together under same MODS tag <originInfo>

MODS features: 

MODS features Physical description info from MARC tags 008, 256, 300 and 856 are pulled together under the MODS <physicalDescription> tag Genre info from MARC tags 007, 008, and 655 are combined under the one MODs tag, <genre> MODS unique elements with no MARC equivalent: <digitalOriginal> with values “born-digital” and “formatted-digital” <reformattingQuality> with values “access” and “preservation”, and “replacement” Xlink attribute allows inclusion of a link to information ID attribute allows inclusion of an internal link to information

MODS Elements: 

MODS Elements All MODS elements and attributes are optional All MODS elements and sub elements are repeatable Some top level elements may also serve as a sub element under another element Example: titleInfo can be a top level element (to show the main title of a resource) but can also function as a sub element under another top level element such as relatedItem (to show the title of another item related to a resource).

Example of a MODS element with sub element: 

Example of a MODS element with sub element Using MODs to show series data: <relatedItem type=“series”> <titleInfo> <title> Music for voice and instrument <title> </titleInfo> the term type functions as an attribute with the value series The title is given inside <titleInfo> and </titleInfo> tags

Metadata record with MODS and METS format options: 

Metadata record with MODS and METS format options

MODS record: 

MODS record

MODS record inside METS recordMODS tags take up about half of this entire METS record: 

MODS record inside METS record MODS tags take up about half of this entire METS record

(2) Continuation of MODS inside METS…: 

(2) Continuation of MODS inside METS…

(3) Continuation of MODS inside METS…: 

(3) Continuation of MODS inside METS…

(4) Continuation of MODS inside METS…: 

(4) Continuation of MODS inside METS…

(5) Continuation of MODS inside METS…: 

(5) Continuation of MODS inside METS… … and so on for 4 or so more screens.

Book record in MODS: 

Book record in MODS

Book record continued…: 

Book record continued…

…end of Book record : 

…end of Book record

Video record in MODS: 

Video record in MODS

Video record continued…: 

Video record continued…

The end: 

The end If not of Dublin Core, at least this presentation! Contact info for your presenters: Cheryl Walters, Utah State University Cheryl.Walters@usu.edu Kayla Willey, Brigham Young University Kayla_Willey@byu.edu