The Library of Congress » Standards » MODS Official Web Site

Top-level Element: <originInfo>

Element <originInfo>
Definition Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource.
Attributes

Common:

Language-related: lang; xml:lang; script; transliteration

Internal Linking: altRepGroup

Miscellaneous: displayLabel

Specific: eventType

Subelements <place> <publisher> <dateIssued> <dateCreated> <dateCaptured> <dateValid> <dateModified> <copyrightDate> <dateOther> <edition> <issuance> <frequency>
Examples EXAMPLES
Mappings MAPPINGS

Guidelines for Use

<originInfo> is a container element that contains dates and other information related to publication, origination creation, and issuance of the resource. (Dates associated with the temporal content of the resource belong under <subject><temporal>, and dates associated with the metadata go in <recordInfo>.)

Different instances of <originInfo> may be supplied for different events. It is recommended, but not required, to use a separate instance of for each event, each with an event type.

Specific Attribute Information

eventType

Definition

A type of event.

Application

There is no controlled list of eventTypes. However, the MARC21 standard contains the following list as possible event types: publication, distribution, manufacture, and production. Other eventType can be used based on specific local needs, such as digitization, in effect, etc.

Top

Subelement: <place>

Definition Name of a place associated with the event.
Attributes

Common:

Miscellaneous: supplied

Specific: None

Subelements <placeTerm>

Guidelines for Use

Descriptive standards such as AACR2, RDA, or DACS may be used to determine which places to record for published resources. If a place of origin is known for an unpublished resource, it should also be recorded in <place><placeTerm>.

Places as subjects are included under <subject><geographic> or <subject><hierarchicalGeographic>.

The <place> element is repeatable.

Specific Attribute Information

supplied

Definition

An indication that the place information did not come from the resource itself.

Application

This attribute is used as supplied="yes" when the place information has been supplied from an external source, not from the resource.

Top

Subelement: <place><placeTerm>

Definition Used to express place in a textual or coded form.
Element <placeTerm>
Attributes

Common:

Authority: authority; authorityURI; valueURI;

Language-related: lang; xml:lang; script; transliteration

Specific: type

Subelements None

Guidelines for Use

If both a code and a term are given that represent the same place, use one <place> and multiple occurrences of <placeTerm>. For different places, repeat <place><placeTerm>.

Specific Attribute Information

type

Definition
Indicates whether the place is expressed in a coded or textual form.
Application
This attribute may be used with the following values:
  • text – This value is used to express place in a textual form.
  • code – This value is used to express place in a coded form.

Top

Subelement: <publisher>

Definition The name of the entity that published, printed, distributed, released, issued, or produced the resource.
Attributes

Common:

Language-related: lang; xml:lang; script; transliteration

Miscellaneous: supplied

Specific: None

Subelements None

Guidelines for Use

Record in <publisher> a named entity determined to be the publisher/originator for a resource or a statement about publication/origin. Descriptive standards such as AACR2, RDA, or DACS may be used to format the name of the publisher

For digitized resources, information about an institution responsible for digitizing and delivering online a previously published resource should be included in <note>, rather than <originInfo><publisher>.

Specific Attribute Information

supplied

Definition

An indication that the publisher information did not come from the resource itself.

Application

This attribute is used as supplied="yes" when the publisher information has been supplied from an external source, not from the resource.

Top

Subelement: <dateIssued>

Definition The date that the resource was published, released, or issued.
Attributes

Common:

Language-related: lang; xml:lang; script; transliteration

Date: encoding; point; keyDate; qualifier; calendar

Specific: None

Subelements None

Guidelines for Use

The date may be in textual or structured form. If it is structured, the encoding attribute should specify the format. No good standard for encoding BCE dates in a structured form currently exists; until such time as these recommendations emerge, BCE dates may be represented in textual forms only.

The MODS schema includes several date elements intended to record different events that may be important in the life of a resource. When multiple date elements apply but would contain identical data, institutions may choose to use only one of the relevant date elements. Mark one and only one date as a key date using keyDate="yes" attribute.

When a date is uncertain or cataloger-supplied, indicate this through the use of the qualifier attribute rather than inserting characters such as "ca.", brackets, or a question mark as part of the date string. When only a decade is known, enter a date range for the entire decade and mark the date as questionable. When only a century is known, enter a date range for the entire century and mark the date as questionable.

Top

Subelement: <dateCreated>

Definition The date of creation of the resource.
Attributes

Common:

Date: encoding; point; keyDate; qualifier

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

If creation date is also the origination date (as in MARC 21 field 260 subfield $c), use the <dateIssued> element or repeat both <dateCreated> and <dateIssued>.

Top

Subelement:<dateCaptured>

Definition The date on which the resource was digitized or a subsequent snapshot was taken.
Attributes

Common:

Date: encoding; point; keyDate; qualifier; calendar

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

<dateCaptured> is particularly useful for Web resources because of their changeability. This would be a date that the resource was captured and archived.

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

Top

Subelement: <dateValid>

Definition A date in which the content of a resource is valid.
Attributes

Common:

Date: encoding; point; keyDate; qualifier; calendar

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

Top

Subelement: <dateModified>

Definition The date in which a resource is modified or changed.
Attributes

Common:

Date: encoding; point; keyDate; qualifier; calendar

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

Note that <dateModified>is used for modification of the resource, not of the metadata. In some cases a modified resource may be considered a new resource and described as such.

Top

Subelement: <copyrightDate>

Definition A date in which a resource is copyrighted.
Attributes

Common:

Date: encoding; point; keyDate; qualifier; calendar

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

Top

Subelement: <dateOther>

Definition A date that does not fall into another category but is important to record.
Attributes

Common:

Date: encoding; point; keyDate; qualifier; calendar;

Language-related: lang; xml:lang; script; transliteration

Specific: type

Subelements None

Guidelines for Use

See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components.

<dateOther> may be used with the type attribute to designate a specific kind of date which was not deemed of sufficient general use to have its own date element.

Specific Attribute Information

type

Definition

Indicates the kind of date being recorded in this element.

Application

This attribute allows for extensibility of date types so that other specific date types may be designated if not given a separate element in MODS.

Top

Subelement: <edition>

Definition Information identifying the version of the resource.
Attributes

Common:

Language-related: lang; xml:lang; script; transliteration

Miscellaneous: supplied

Specific: None

Subelements None

Guidelines for Use

Resources that constitute the same "edition" generally embody essentially the same content. If no edition statement applies to the resource, do not include the <edition> element.

Top

Subelement: <issuance>

Definition A term that designates how the resource is issued.
Attributes None
Subelements None

Guidelines for Use

<issuance> may be used with the following values:

  • monographic – A resource that is either complete in one part or intended to be completed in a finite number of separate parts. Alternatively, more specific values distinguishing "single unit" from "multipart monograph" may be used.
  • single unit – A type of monographic resource that is issued either as a single physical unit (e.g., as a single-volume monograph) or, in the case of an intangible resource, as a single logical unit (e.g., as a PDF file mounted on the Web).
  • multipart monograph – A type of monographic resource issued in two or more parts (either simultaneously or successively) that is complete or intended to be completed within a finite number of parts (e.g., a dictionary in two volumes or three audiocassettes issued as a set).
  • continuing – A resource that is issued over time with no predetermined conclusion. Continuing resources include serials and ongoing integrating resources, i.e. those that are continuously updated. Alternatively, more specific values distinguishing "serial" from "integrating resource" may be used.
  • serial – A type of continuing resource issued in successive parts, usually bearing numbering, that has no predetermined conclusion (e.g., a periodical, a monographic series, or a newspaper). Includes resources that exhibit characteristics of serials, such as successive issues, numbering, and frequency, but whose duration is limited (e.g., newsletters of events) and reproductions of serials.
  • integrating resource – A type of continuing resource that is added to or changed by means of updates that do not remain discrete and are integrated into the whole. An integrating resource may be tangible (e.g., a loose-leaf manual that is updated by means of replacement pages) or intangible (e.g., a Web site that is updated either continuously or on a cyclical basis).

Collection, which designates an aggregation level, is included in the collection attribute in the <typeOfResource> element.

Top

Subelement: <frequency>

Definition A statement of publication frequency in textual form.
Attributes

Common:

Authority: authority; authorityURI; valueURI

Language-related: lang; xml:lang; script; transliteration

Specific: None

Subelements None

Guidelines for Use

Use to define the publication pattern of the item.

Specific Attribute Information

authority

Definition

Indicates the controlled list from which the value is taken.

Application

The name of the authoritative list for a controlled value is recorded here. See Frequency of Issue Code and Term Source Codes for a list of authority sources. Use the value of "marcfrequency" if the authority used is MARC Frequency of Issue Term List.

authorityURI

Definition

A URI uniquely identifying the vocabulary from which the controlled term has been selected, as assigned by the body responsible for the maintenance of the vocabulary.

Application

URIs identifying authorities may or may not be dereferenceable to human- or machine-readable information on the authority file, controlled vocabulary, or thesaurus.

valueURI

Definition

A URI uniquely identifying the term or controlled value from a vocabulary, as assigned by the body responsible for the maintenance of the vocabulary.

Application

URIs identifying terms may or may not be dereferenceable to human- or machine-readable records for the term.

Top

EXAMPLES

<originInfo eventType="publisher">
<place>
<placeTerm type="code" authority="marccountry">dcu</placeTerm>
<placeTerm type="text">Washington, DC</placeTerm>
</place>
<publisher>Library of Congress, Cataloging Distribution Service, in collaboration with Follett Software Company</publisher>
<dateIssued>2003</dateIssued>
<edition>7th ed.</edition>
<issuance>monographic</issuance>
</originInfo>
<originInfo eventType="manufacture">
<place>
<placeTerm type="text">Cambridge</placeTerm>
</place>
<publisher>Kinsey Printing Company</publisher>
<dateOther type="manufacture" keyDate="yes" qualifier="inferred">1922</copyrightDate>
</originInfo>
<originInfo eventType="publication">
<copyrightDate encoding="iso8601">20000122</copyrightDate>
<dateCaptured encoding="iso8601">20010712</dateCaptured>
<issuance>continuing</issuance>
</originInfo>
<originInfo eventType="production">
<dateValid encoding="iso8601" point="start">20011008</dateValid>
<dateValid encoding="iso8601" point="end">20011027</dateValid>
</originInfo>
<originInfo eventType="publication">
<place>
<placeTerm type="text">Milan</placeTerm>
</place>
<publisher>F. Lucca</publisher>
<place>
<placeTerm type="text">Florence</placeTerm>
</place>
<publisher>Ducci</publisher>
<place>
<placeTerm type="text">Chiasso</placeTerm>
</place>
<publisher>Euterpe Ticinese</publisher>
<place>
<placeTerm type="text">Naples</placeTerm>
</place>
<publisher>Girard et C.</publisher>
<dateIssued>between 1856 and 1862</dateIssued>
<dateIssued encoding="marc" point="start">1856</dateIssued>
<dateIssued encoding="marc" point="end">1862</dateIssued>
<issuance>monographic</issuance>
</originInfo>
<originInfo eventType=publication>
<place supplied="yes">
<placeTerm type="code" authority="marccountry">nyu</placeTerm>
<placeTerm type="text">New York</placeTerm>
</place>
<publisher>Published for the American Vacuum Society by the American Institute of Physics</publisher>
<dateIssued>1994</dateIssued>
<issuance>monographic</issuance>
</originInfo>
<originInfo eventType="manufacture">
<dateModified encoding="iso8601">20031008</dateModified>
</originInfo>
<originInfo eventType="manufacture">
<dateCreated keyDate="yes">1972-10-08</dateCreated>
</originInfo>
<originInfo eventType="production">
<dateCreated encoding="iso8601" keyDate="yes" qualifier="inferred">1916</dateCreated>
</originInfo>
<originInfo eventType="publication">
<place>
<placeTerm type="code" authority="iso3166">usa</placeTerm>
<placeTerm type="text">United States</placeTerm>
</place>
<dateIssued>1975</dateIssued>
</originInfo>
<originInfo eventType="publication">
<place>
<placeTerm type="code" authority="marccountry">dcu</placeTerm>
<placeTerm type="text">Washington, D.C</placeTerm>
</place>
<publisher>Library of Congress</publisher>
<dateIssued>1998-</dateIssued>
<dateIssued encoding="marc" point="start">1998</dateIssued>
<dateIssued encoding="marc" point="end">9999</dateIssued>
<issuance>monographic</issuance>
</originInfo>
<originInfo eventType="publication>
<place>
<placeTerm type="code" authority="marccountry">cau</placeTerm>
<placeTerm type="text">Menlo Park, CA</placeTerm>
</place>
<publisher>Center for Computer Assisted Research in the Humanities</publisher>
<dateIssued>1985-1988</dateIssued>
<dateIssued encoding="marc" point="start">1985</dateIssued>
<dateIssued encoding="marc" point="end">1988</dateIssued>
<issuance>continuing</issuance>
<frequency authority="marcfrequency">Annual</frequency>
</originInfo>
<originInfo eventType=publication>
<place>
<placeTerm type="code" authority="marccountry">enk</placeTerm>
<placeTerm type="text">England</placeTerm>
</place>
<dateIssued encoding="w3cdtf" keyDate="yes" qualifier="inferred">1855</dateIssued>
<issuance>monographic</issuance>
</originInfo>
<originInfo eventType="publication">
<dateOther point="start">20011008</dateOther>
<dateOther point="end">20011027</dateOther>
</originInfo>

Top

MAPPINGS

MARC Mapping (Bibliographic)

See MARC Mapping to MODS for the <originInfo> element.

Dublin Core Mapping

See MODS to Dublin Core Metadata Element Set Mapping.

Top

Last Updated: August 10, 2020