Place of Publication or Origin

 Click here to show Table of Contents...

Abstract

REPEATABLE MULTILINGUAL

MODS Element name: <originInfo><place>

Short definition: Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource.

Input guidelines: Refer to content standards like RDA or DACS to determine which places to input. Indicate the language of the Place by entering the appropriate three-letter language code from ISO-639-3 language codes. Designate a primary place, even if only one place is entered.

Definition

Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource.

DAMS input form fields

Place(s) of Publication/Origin

DAMS form field nameform field typerequiredMODS elementCollections Portal displaynotes
Place Nametext fieldnooriginInfo/place/placeTermPlace Name
Primary Origin?

dropdown selection

  • yes
  • no
no

originInfo/place/placeTerm[@usage]

(attribute of placeTerm)

N/A

Designate a primary place, even if only one place is entered.

Language of Place Nametext fieldno

originInfo/place/placeTerm[@lang]

(attribute of placeTerm)

N/AEnter the appropriate three-letter language code from ISO-639-3 language codes.

MODS Element description

Element <originInfo>

http://www.loc.gov/standards/mods/userguide/origininfo.html

Guidelines for use

<originInfo> is a container element that contains all subelements related to publication and origination information. It includes all dates associated with the creation, issuance, and/or publication of the resource. Dates associated with the temporal content of the resource go under <subject>, and dates associated with the metadata go in <recordInfo>. Data is input only within each subelement.

Attributes

Currently no attributes for originInfo are implemented in the DAMS.

Subelements

The following subelements of <originInfo> are used in the DAMS:

  • place
  • (dateCreated)
  • (dateIssued)
  • (copyrightDate)
  • (publisher)

Subelement <originInfo><place>

Guidelines for use

<place> is a container element for <placeTerm> to indicate place of publication/origin. <place> is used in connection with the origin of a resource, i.e., creation, publication, issuance, etc. The <place> element should be omitted if no information about the originating place of the resource is known.

Descriptive standards such as 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>.

Repeat <place> for recording multiple places.

Attributes

No attributes for <place>.

Subelements

The following subelement of <originInfo><place> is used in the DAMS:

  • placeTerm

Subelement <originInfo><place><placeTerm>

Guidelines for use

Used to express place in a textual form.

Attributes

Attribute name

Details

XPath syntax examples

type

value:

  • text
originInfo/place/placeTerm[@type="text"]
lang

values:

Enter ISO-639-3 language code (3 letters).

originInfo/place/placeTerm[@lang="eng"]
usage

value:

  • primary

Designate a primary place, even if only one place is entered.

(Not part of the MODS standard.)

originInfo/place/placeTerm[@usage="primary"]

Subelements

No subelements for placeTerm.

XML Examples

<originInfo>
	<place>
		<placeTerm type="text" lang="eng" usage="primary">Oxford</placeTerm>
	</place>
</originInfo>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

MARC 21

see http://www.loc.gov/standards/mods/mods-mapping.html#publication. The following specific guidelines apply for the DAMS:

MARC 21 fieldMapping conditionMODS elementNotes
008/15-17
N/ADo not use coded data in DAMS MODS.
004$c
N/ADo not use coded data in DAMS MODS.
260$a
placeTerm[@type="text"]

Solr

In general, all MODS metadata is imported into the DAMS Solr server upon ingest. The ingest process generates Solr fields typically named according to the following schema:

mods_value*_suffix

where

  • value* can be one or multiple element, subelement or attribute names that allow to distinguish Solr fields
  • suffix is s, t, ss, ms or mt, which refers to the type of data stored in a Solr field and how it is indexed. The Solr index usually contains multiple copies of each field with the same content, distinguished by their suffix.

The following table shows mappings between MODS elements and Solr fields for those fields that are currently used for display in the Collections portal, or where additional processing happens in Islandora or during the publishing process. Suffixes are ignored, unless relevant for the mapping.

MODS elementMapping conditionSolr DAMSSolr Collections PortalNotes
originInfo/place/placeTerm

mods_originInfo_place_placeTerm

mods_originInfo_place_placeTerm