[ return to index ]

Name

mods:name [Required if Applicable]

Local Practices and Interpretations

mods:name is a wrapper element used to record all relevant personal, corporate or event names associated with a resource. At least one name is required if applicable. A name must be parsed into parts (i.e. use repeatable subelement mods:namePart as appropriate), and be assigned a role.

Supported Descendant Elements and Attributes

@type

[Required] Use the appropriate type attribute value supplied by the schema: personal, corporate, or conference.

@authority

[Required] Princeton's default policy for MODS records is to use the naf as our authority. When the naf is used, the value will always be "naf"

@lang, @script, @xlink:role, @xlink:title

[Required if Applicable] See Linking Parallel Data in Alternate Scripts

mods:namePart

[Required] mods:namePart is repeatable. A name should be parsed according to the values prescribed for the type attribute. Give them in the order in which the heading is constructed in the authority file.

mods:namePart/@type

[Required for personal names] The values of the type attribute are "date", "family", "given", and "termsOfAddress".

mods:role/mods:roleTerm

[Required] Used to record the MARC relator code. To record more than one roleTerm, repeat the entire role element.

mods:role/mods:roleTerm/@authority

[Required] The value is always "marcrelator".

mods:role/mods:roleTerm/@type

[Required] The value is always "code".

XML Examples

[ show / hide ]

Display Examples

[ show / hide ]

Content Standards

Other Sources of Documentation

MARC Mappings

100, 110, 111, 700, 710, 711

For names as subjects (600, 610, 611) see mods:name as subelement of mods:subject. In general, practices are the same except a role is not supplied.

[ return to index ]