Publisher
Abstract
REPEATABLE MULTILINGUAL
MODS Element name: <originInfo><publisher>
Short definition: The name of the entity that published, printed, distributed, released, issued, or produced the resource, or a statement about publication/origin.
Input guidelines: Input a named entity determined to be the publisher/originator for a resource or a statement about publication/origin. Descriptive standards such as RDA or DACS should be used to format the name of the publisher.
Definition
The name of the entity that published, printed, distributed, released, issued, or produced the resource, or a statement about publication/origin.
DAMS input form fields
Publisher(s)
DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
---|---|---|---|---|---|
Publisher Name/Statement | text field | no | originInfo/publisher | Publisher | |
Publisher Language | text field | no | originInfo/publisher[@lang] (attribute of publisher) | N/A | No default language. If information about publisher is a statement (rather than name), enter the appropriate three-letter language code from ISO-639-2b 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:
- publisher
- (dateCreated)
- (dateIssued)
- (copyrightDate)
- (place)
Subelement <originInfo><publisher>
Guidelines for use
Input named entity determined to be the publisher/originator for a resource or a statement about publication/origin. Descriptive standards such as RDA or DACS should be used to format the name of the publisher.
Attributes
Attribute name | Details | XPath syntax examples |
---|---|---|
lang | value: | No default language. If information about publisher is a statement (rather than name), enter the appropriate three-letter language code from ISO-639-2b language codes. |
Subelements
No subelements for <publisher>.
XML Examples
Mappings
Dublin Core
Depending on the direction of mapping necessary, check
- DC to MODS: https://www.loc.gov/standards/mods/dcsimple-mods.html
- MODS to DC: http://www.loc.gov/standards/mods/mods-dcsimple.html
MARC 21
Map from MARC field 260$b - see http://www.loc.gov/standards/mods/mods-mapping.html#publication.
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 element | Mapping condition | Solr DAMS | Solr Collections Portal | Notes |
---|---|---|---|---|
originInfo/publisher | dc.publisher | dc.publisher | ||
originInfo/publisher | mods_originInfo_publisher | N/A |
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.