The Library of Congress » Standards » MODS Official Web Site
Metadata Object Description Schema: Official Web Site
HOME >> MODS 3.5 Changes

Changes for MODS 3.5

February 2013

The following changes for MODS Version 3.5 have been approved by the MODS Editorial Committee. Version 3.5 will be backwards compatible to 3.4 and therefore only includes changes that do not result in invalidating existing MODS records. In the future the Committee may consider major changes that may not be backwards compatible and will document those approved on this website. Changes listed below include the change, its purpose, examples, and the date approved by the MODS Editorial Committee." The MODS Draft 3.5 Schema is available for public review through June 7th, 2013.

  1. Add attribute @unit to <physicalDescription><extent> (Approved 2012-03-12)

    This change makes the extent element more granular by separating units from extent.


         <extent unit=”pages”>12</extent>

  2. Add rfc5646 as value for <language><languageTerm> (Approved 2012-03-12)

    Enumerated values reflect earlier standards; RFC5646 has superceded RFC4646

  3. Add @altFormat and @contentType attributes to <titleInfo>, <abstract>, <tableOfContents> and <accessCondition> (Approved 2012-09-17)

    This change allows for embedding HTML in MODS, linking with @altRepGrp, and indicating the format of the alternative encoding. It applies to those elements that are most likely to have values that need HTML or other formatting that cannot be expressed inside a MODS XML record. Use the altFormat attribute to link out of the record to the same content, formatted or marked up in a different way. Optionally, include the contentType attribute with a media-type as its value (e.g. text/html) to indicate the content type of the target. Where there are multiple alternatives, use the already defined altRepGroup attribute to bind the related instances of each element.


    <abstract altRepGroup="A" altFormat="" contentType="application/xhtml+xml"/>

    <abstract altRepGroup="A">l'histoire d'un cheval et un garçon qui aimait</abstract>

  4. Add @eventType to <originInfo> to indicate production, publication, distribution, manufacture (Approved 2012-04-23, Revised 2013-01-23

    This attribute allows for indicating what type of event the statement of originInfo relates to, e.g. production, publication, distribution, manufacture, or some other event.

  5. Example:

    <originInfo eventType="publication">
               <placeTerm>Menlo Park, CA</placeTerm>
         <publisher>Center for Computer Assisted Research in the Humanities</publisher>
         <dateIssued encoding="marc" point="start">1985</dateIssued>
         <dateIssued encoding="marc" point="end">1988</dateIssued>
         <frequency authority="marcfrequency">Annual</frequency>

  6. Add @typeURI to <identifier>, <note>, and <physicalDescripton>/<note> (Approved 2012-09-17)

    This change allows for indicating that a type is in the form of a URI.


    <identifier typeURI="">9780385333511</identifier>

  7. Add @generator to <classification> (Approved 2013-01-09)

    The value of this attribute indicates that the classification number was automatically generated and, if appropriate, how.


    <classification authority="ddc" edition="22" generator="" >813.54</classification>

  8. Add <etal> element, a subelement of <name> (Approved 2013-01-23)

    The <etal> subelement is added to the list of <name> subelements to indicate that there are one or more names that, for whatever reason, cannot be explicitily included in another name element.


                <namePart type="family">Fox</namePart>
                <namePart type="given">Nellie</namePart>
                <namePart type="family">Phillips</namePart>
                <namePart type="given">Bubba</namePart>

    Would mean "Nellie Fox, Bubba Phillips, and others"

  9. Add @otherType to <titleInfo> element (Approved 2013-02-20)


    <titleInfo lang="chi" script="Hant">
    <titleInfo otherType="transliterated" transliteration="chinese/ala-lc">
    <titleInfo type="translated" lang="eng">

HOME >> Changes for MODS Version 3.5

Questions and comments:
Contact Us ( February 2, 2022 )
Legal | External Link Disclaimer