skip navigationThe Library of Congress » Standards » MODS Official Web Site |
Top-level Element: <location>
Guidelines for Use<location> is a container element; specific data is recorded in the subelements. Subelement: <physicalLocation>
Guidelines for UseThis subelement identifies the physical, institutional home of a resource. <physicalLocation> typically includes specific information used to locate a resource, such as the name or code of an institution/repository, and perhaps a subcollection. A shelf number is given in <shelfLocator>. <physicalLocation> may be expressed as text and/or as a code. Use the authority attribute to designate the source of the code. Recommended values for the authority attribute are "marcorg" or "oclcorg". Use the naming authority appropriate to each value as identified in Organization Code Source Codes. If the the authority attribute is not used, the <physicalLocation> value is assumed to be a textual, natural language name and/or address. Specific Attribute Informationtype Definition
Identifies the type of location recorded.
Application
Use to indicate different kinds of locations if more specificity is needed, e.g. current, discovery, former, creation.
Subelement: <shelfLocator>
Guidelines for UseIf more detailed holdings information is given at the item level, use <shelfLocator> under <holdingSimple>. Subelement: <url>
Guidelines for Use<url> is for an electronic location from which the resource is available. Note that <identifier> is used for persistent identifiers that may or may not be resolvable. It is recommended that all URLs used with the <location> element be persistent. The <location> element with the <url> subelement may be used to indicate locations of additional versions of the digital resource such as thumbnails of the digital resource. Best practice is that the "primary display" URL is a link to the resource with its contextual material (for example metadata, navigation to the collection homepage). If the primary link to a resource is to a stand-alone version of the resource (such as a JPEG image only), an end user will have no context except for the metadata on the service provider's site. At a minimum, the URL should point to a page that contains the resource and a navigation bar that allows users to reach the collection homepage. It is highly desirable that this page also include the descriptive metadata for the resource. The <location> element with the <physicalLocation> subelement may also be used to point to the location of the equivalent analog resource. When <physicalLocation> and <url> appear within the same <location> element, then the <url> is understood to point to the corresponding digitized version of the physical copy held by that institution. If the url points to a digital version originating from a different institution, a separate <location> element should be used. It is not necessary nor always desirable to include the location of all digital and/or analog versions of the described resource. Only include that information which is useful and important to the aggregator and to the end user. Use of the access attribute is recommended with all instances of <location><url>. This attribute helps a metadata aggregator determine what a URL is likely to link to and can help determine which URL to use for specific purposes. Use the note attribute only when other attributes (access, usage, or displayLabel) are not appropriate. Specific Attribute InformationdateLastAccessed Definition
Intended to express the date that a digital resource has been accessed remotely.
Application
This attribute may be useful to a user because of the volatility of Web content. There is no encoding scheme specified for use with this attribute, however, a structured date is recommended.
note Definition
Includes notes that are associated with the link that is included as the value of the <url> element.
Application
This attribute is generally free text.
access Definition
Indicates the type of resource that the user will access when following the URL link.
Application
This attribute is particularly useful to provide a flag in the context of OAI service providers harvesting metadata.
The following values may be used with the access attribute:
Subelement: <holdingSimple>
Guidelines for UseHoldings information consists of copy-specific information about the resource, information about the specific location within an institution, version information, and other information that is peculiar to the institution. <holdingSimple> is a set of MODS internally defined elements and corresponds roughly to summary holdings information. If more granularity is required, <holdingExternal> may be used in lieu of <holdingSimple> with elements from an external schema. <holdingSimple> is a container element for the single subelement, <copyInformation> which has several subelements. <holdingSimple> is not repeatable; if additional holdings statements are needed for the resource, repeat <location> with appropriate subelements. For more information see MODS Holdings Information. Subelement: <holdingSimple><copyInformation>
Guidelines for Use<copyInformation> is a container element. Data is entered in the subelements. Subelement: <holdingSimple><copyInformation><form>
Guidelines for UseThe <form> subelement is equivalent to MODS <physicalDescription><form>. It may be included under <copyInformation> when the MODS record refers to multiple forms and there is different detailed holdings information associated with each form. Form is not repeatable; <copyInformation> is repeated within <holdingSimple> for multiple forms. When using the authorities attribute, it is recommended to use a code from the list of Genre/Form Code and Term Source Codes maintained by the Library of Congress. Specific Attribute Informationtype Definition
May be used to specify whether the form concerns materials or techniques, for example:
<form type="material>oil paint</form>
<form type="technique>painting</form> Application
There are no controlled values for the type attribute.
Subelement: <holdingSimple><copyInformation><subLocation>
Guidelines for Use<subLocation> may be repeated for multiple equivalent items in different sublocations within the institution named in <physicalLocation>. Subelement: <holdingSimple><copyInformation><shelfLocator>
Guidelines for Use<shelfLocator> may be given at the bibliographic description level under <location> (i.e. shelfLocator of the entire resource) or at the item level under <holdingSimple> (when <shelfLocator> may vary by each physical piece). Subelement: <holdingSimple><copyInformation><electronicLocator>
Guidelines for UseThis is a copy-specific form of <location><url>, without its attributes. Subelement: <holdingSimple><copyInformation><note>
Guidelines for UseUse for notes relating to the specific copy information of a resource that do not fit in one of the other available subelements. A link may be supplied in lieu of or in addition to the content. Each note should be entered in a separate <note> subelement. Specific Attribute Informationtype Definition
Describes the type of note that is recorded.
Application
This attribute is not controlled by a list and thus is open-ended.
Subelement: <holdingSimple><copyInformation><enumerationAndChronology>
Guidelines for Use<enumerationAndChronology> is an unparsed string that comprises a summary holdings statement. If more granularity is needed, a parsed statement using an external schema may be used within <holdingExternal>. Specific Attribute InformationunitType Definition
The category of bibliographic entity for which <enumerationAndChronology> is given.
Application
This attribute may contain the following values:
Subelement: <holdingSimple><copyInformation><itemIdentifier>
Guidelines for UseMODS makes a distinction between a persistent identifier and its electronic location. This element is used for the former. Specific Attribute Informationtype Definition
Identifies the type of itemidentifier, for example 'barcode' or 'itemnumber'.
Application
There is no controlled list for item identifier types.
Subelement: <holdingExternal>
Guidelines for Use<holdingExternal> may include more detailed holdings information than that accommodated by the MODS schema. An example is ISO 20775 and its accompanying schema. EXAMPLES<location>
<physicalLocation authority="marcorg">DLC</physicalLocation>
</location>
<location>
<physicalLocation authorityURI="https://id.loc.gov/authorities/names" valueURI="https://id.loc.gov/authorities/names/n81079447">Library of Congress, Music Division</physicalLocation>
[Linked data example - with link to id.loc.gov] <location>
<physicalLocation authorityURI="http://id.loc.gov/vocabulary/organizations" valueURI="http://id.loc.gov/vocabulary/organizations/macbhcl">Harvard University, Harvard College Library</physicalLocation>
[Linked data example - with link to id.loc.gov] </location>
<location>
<physicalLocation xlink:href="http://www.loc.gov/rr/mss/">Library of Congress Manuscript Division</physicalLocation>
</location>
[xlink attribute -- with link to the web page of the institution represented by the value] <location>
<physicalLocation displayLabel="Correspondence">National Archives and Records Service. Genealogical Research Recording. Pennsylvania Ave. at 8th St., N.W., Washington, D.C. USA </physicalLocation>
</location>
<location>
<url displayLabel="French version">http://www.cgiar.org/ifpri/reports/0297rpt/0297-ft.htm</url>
</location>
<location>
<url dateLastAccessed="2004-01-27">http://www.loc.gov/marc/</url>
</location>
<location>
<url access="raw object">http://www.loc.gov/standards/relreport.pdf</url>
</location>
<location>
<url access="preview">http://purl.dlib.indiana.edu/iudl/lilly/slocum/thumbnail/LL-SLO-000077</url>
<url access="object in context">http://purl.dlib.indiana.edu/iudl/lilly/slocum/LL-SLO-000077</url> <url access="raw object">http://purl.dlib.indiana.edu/iudl/lilly/slocum/full/LL-SLO-000077</url> </location>
< location>
<url note="Adobe Acrobat Reader required"> http://purl.access.gpo.gov/GPO/LPS31437 </url>
</location>
<location>
<physicalLocation>University of Chicago </physicalLocation>
<url"> http://pi.lib.uchicago.edu/1001/dig/chopin/373</url> </location>
<location>
<physicalLocation>Library of Congress </physicalLocation>
<holdingSimple> <copyInformation>
<subLocation>Prints and Photographs Division Washington, D.C. 20540 USA</subLocation>
<shelfLocator>DAG no. 1410</shelfLocator> </copyInformation>
</holdingSimple>
</location>
<location>
<physicalLocation authority="marcorg">MnRM</physicalLocation>
<holdingSimple> <copyInformation>
<subLocation>Patient reading room</subLocation>
<shelfLocator>QH511.A1J68</shelfLocator> <enumerationAndChronology unitType="1"> v.1-v.8 1970-1976</enumerationAndChronology> </copyInformation>
</holdingSimple>
</location>
<location>
<physicalLocation authority="marcorg"> CaOON</physicalLocation>
<holdingSimple> <copyInformation>
<form authority="marcform">print</form>
<subLocation>Chem</subLocation> <shelfLocator> QD.C454L55</shelfLocator> <enumerationAndChronology unitType="1"> v. 1-24 1994-2000</enumerationAndChronology> </copyInformation>
<copyInformation> <form authority="marcform">electronic</form>
<electronicLocator>http://cisti-icist.nrc-cnrc.gc.ca/journal1.html</electronicLocator> <enumerationAndChronology unitType="1">v. 16-24 1998-2000</enumerationAndChronology> </copyInformation>
</holdingSimple>
</location>
<location>
<physicalLocation>Menlo Park Public Library</physicalLocation>
<holdingExternal> <holding xmlns:iso20775="info:ofi/fmt:xml:xsd:iso20775" xsi:schemaLocation="info:ofi/fmt:xml:xsd:iso20775 http://www.loc.gov/standards/iso20775/N130_ISOholdings_v6_1.xsd">
<institutionIdentifier>
<value>JRF</value>
<typeOrSource> <pointer>http://worldcat.org/registry/institutions/</pointer>
</typeOrSource>
</institutionIdentifier>
<physicalLocation>Menlo Park Public Library</physicalLocation> <physicalAddress> <text>Menlo Park, CA 94025 United States </text>
</physicalAddress>
<electronicAddress> <text>http://www.worldcat.org/wcpa/oclc/15550774? page=frame&url=%3D%3FUTF-
8%3FB%FaHR0cDovL2NhdGFsb2cucGxzaW5mby5vcmcvc2VhcmNoL2kwMTk1MDM4NjMw%3F%3D &title=Menlo+Park+Public+Library&linktype=opac&detail=JRF%3AMenlo+Park+Public+Library%3APublic &app=wcapi&id=OCL-OCLC+Staff+use</text> </electronicAddress>
<holdingSimple> <copiesSummary>
<copiesCount>1</copiesCount>
</copiesSummary>
</holdingSimple>
</holding>
</holdingExternal>
</location>
<location>
<url usage="primary display" access="object in context">http://hemi.es.its.nyu.edu/journal/2_1/ramalho_por.html</url>
</location>
<location>
<physicalLocation authority="oclcorg">NNU</physicalLocation>
<physicalLocation>New York University, E. H. Bobst Library (New York, NY)</physicalLocation> </location>
<location>
<url usage="primary display" access="object in context">http://webapp1.dlib.indiana.edu/cushman/results/detail.do?pnum=P04995</url>
<url access="raw object">http://webapp1.dlib.indiana.edu/collections/cushman/full/P04995.jpg</url> </location>
MAPPINGSMARC Mapping (Bibliographic)See MARC Mapping to MODS for the <location> element. Dublin Core MappingSee MODS to Dublin Core Metadata Element Set Mapping. Last Updated: November 3, 2022 |