1 / 23

MODS

MODS. What is MODS: Stands for Metadata Object Descriptive Schema MODS is an XML descriptive metadata standard. Extension schema to METS MODS was derived from MARC (which is another standard for representation of bibliographic information)

chick
Télécharger la présentation

MODS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MODS • What is MODS: • Stands for Metadata Object Descriptive Schema • MODS is an XML descriptive metadata standard. • Extension schema to METS • MODS was derived from MARC (which is another standard for representation of bibliographic information) • More specifically, MODS uses a subset of MARC data elements • When is MODS use: • MODS will be used for descriptive metadata, in other words, MODS will be help to identify resources such as a bibliographic data.

  2. MODS Schema Attributes • Language Attributes • xml:lang – is an XML standard attribute that defines the language individual elements may use • Date Attributes • encoding: refers to the values that identify the format of the dates, for instance, “w3cdtf” refers to dates that use the pattern: YYYY-MM-DD

  3. MODS Top-Level Elements • Top-level elements • Top-level elements in MODS, are element names without a hierarchy, meaning that these may or may not have sub-elements but are not sub-elements of any other element. • The only exception where all MODS elements are sub-elements is under <relatedItem> container, this will be explained later with an example

  4. MODS Top-Level Elements • titleInfo • name • typeOfResource • genre • originInfo • language • physicalDescription • abstract • tableOfContents • targetAudience • note • subject • classification • relatedItem • identifier • location • accessCondition • part • extension • recordInfo

  5. MODS Required Elements • Required elements are items that are absolutely a requirement of the guidelines • Based on this, my understanding is that these elements are essential in order to assemble the archive

  6. MODS Required Elements • titleInfo • typeOfResource • originInfo • physicalDescription • Location • accessCondition • recordInfo • language (required if language is primary to the resource) • subject (required if applicable)

  7. MODS Required Elements Example 1 • Taken from the mods.xml that Kate send to us: • typeOfResource • Generally describes the form of the resource content • For example: <typeOfResource>text</typeOfResource>

  8. MODS Required Elements Example 2 • Taken from the mods.xml that Kate send to us: • originInfo • Information that pertains to the origin of the resource such as publisher, date published, how the resource was issued (monographic means that it was released in one part or a finite number of parts) • For example: <originInfo> <publisher>U.S. Government Printing Office</publisher> <dateIssued encoding="w3cdtf">2010-09-29</dateIssued> <issuance>monographic</issuance> </originInfo>

  9. MODS Required Elements Example 3 • Taken from the mods.xml that Kate send to us: • physicalDescription • describes the physical attributes of the resource such as general text based information about the resource (for example “type” is an attribute that gives more detail to the general text), the method use to achieve digital form of the resource (for example “born digital” indicates that this particular archive was created and must remain in digital form) and the number of units that make up the resource

  10. MODS Required Elements Example 3 continue • For example <physicalDescription> <note type="source content type">deposited</note> <digitalOrigin>born digital</digitalOrigin> <extent>7 p.</extent> </physicalDescription>

  11. MODS Required Elements Example 4 • Taken from the mods.xml that Kate send to us: • location • Identifies the repository holding the resource • displayLabel is an attribute the provides information associated with the location • access label (unsure) • For example: <location xmlns:exslt="http://exslt.org/common"> <url displayLabel="HTML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/html/BILLS-111s3880is.htm</url> <url displayLabel="PDF rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/pdf/BILLS-111s3880is.pdf</url> <url displayLabel="XML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/xml/BILLS-111s3880is.xml</url> </location>

  12. MODS Required Elements Example 5 • Taken from the mods.xml that Kate send to us: • recordInfo • Provides information about the metadata of the original record such as who created it or modified it, date it was created (encoding – denotes the format of the date), date it was last modified, contains the organization and the system control number assigned to it, shows the origin of the MODS record, and the language (can be used to represent more than one language)

  13. MODS Required Elements Example 5 continue • For example <recordInfo> <recordContentSource authority="marcorg">DGPO</recordContentSource> <recordCreationDate encoding="w3cdtf">2010-10-06</recordCreationDate> <recordChangeDate encoding="w3cdtf">2010-10-06</recordChangeDate <recordIdentifier source="DGPO">BILLS-111s3880is</recordIdentifier> <recordOrigin>machine generated</recordOrigin> <languageOfCataloging> <languageTerm type="code" authority="iso639-2b">eng</languageTerm> </languageOfCataloging> </recordInfo> • type attribute “identifies what type of <languageTerm> is recorded”, for example, “the value used to express language” in a coded term is code. • authority attribute, refers to a value taken from a controlled list, for example “iso639-2b” refers to a bibliographic language code from ISO 639-2.

  14. MODS Recommended Elements • Recommended elements are items that the implementer may ignore as long he or she have taken into account the consequences of doing so • The recommended elements are: • genre • abstract • identifier

  15. MODS Recommended Elements Example 1 • Taken from the mods.xml that Kate send to us: • genre • Gives more specific terms to the form of the resource content used in typeOfResource • Again, an interesting attribute of genre is “authority”, which refers to the controlled list from which the value is taken, in the case below the value “marcgt” refers to MARC (another standard for representation of bibliographic information) genre terms • For example: <genre authority=“marcgt">government publication</genre>

  16. MODS Recommended Elements Example 2 • Taken from the mods.xml that Kate send to us: • identifier • refers a unique standard number or code that identifies a resource • type is attribute of identifier refers to the identifier being used, in this case "local" refers to a locally define identifier • For example: <identifier type="local">V0b002ee180b003e5</identifier> • What is the significance of the value “V0b002ee180b003e5”?

  17. MODS Recommended If Applicable • Recommended If Applicable refers to an item that can be applied to the resource, again the implementer may ignore as long he or she have taken into account the consequences of doing so

  18. MODS Recommended IF Applicable • name • tableOfContents • targetAudience • note • relatedItem • part

  19. MODS Recommended IF Applicable Example 1 • Earlier, I mentioned that there was an exception where all MODS elements are sub-elements of <relatedItem> • relatedItem • May be best used for complex objects that may need more detail descriptive information, for example a CD with several tracks • the type attribute describes the association between the resource in the MODS record and <relatedItem>, for example “isReferencedBy” are references or citations of the content of the resource

  20. MODS Recommended IF Applicable Example 1 continue… • For example (Taken from the mods.xml that Kate send to us): <relatedItem type="isReferencedBy" xmlns:exslt="http://exslt.org/common"> <identifier type="USC citation">20 U.S.C. 1070a(b)(2)</identifier> <identifier type="USC citation">20 U.S.C. 1087mm(b)</identifier> </relatedItem>

  21. MODS Optional Elements • Optional elements are items that may be used at the implementer’s discretion • <extension> • is a container used to include information that is not MODS • For example, information that is local to the creator of the data • Another example, is to extend MODS to allow another XML schema to handle information about the resource

  22. Optional Element Example • Taken from the mods.xml that Kate send to us: <extension> <collectionCode>BILLS</collectionCode> <searchTitle>To increase Federal Pell…. searchTitle> <category>Bills and Statutes</category> <waisDatabaseName>111_cong_bills</waisDatabaseName> <branch>legislative</branch> <dateIngested>2010-10-06</dateIngested> </extension>

  23. References • http://www.loc.gov/standards/mods/mods-guidance.html

More Related