MARC 100 Heading Personal Name: Difference between revisions

(→‎Policy and formulation: Added more stuff)
(→‎Basic formulation of personal names: updates from NACO meeting notes 2014-12-10)
Line 22: Line 22:
===Basic formulation of personal names===
===Basic formulation of personal names===
*In general, avoid creating unqualified personal name access points, even in the absence of a conflict. Use judgment, however, as some names may be unusual enough in themselves, so that the addition of active dates or a title or another designation would be superfluous.  
*In general, avoid creating unqualified personal name access points, even in the absence of a conflict. Use judgment, however, as some names may be unusual enough in themselves, so that the addition of active dates or a title or another designation would be superfluous.  
**Example: [http://lccn.loc.gov/no2014170428 Edward J. Geisweidt] was established without any additional qualifications: he is the only ''Geisweidt'' in the name authority file, and with a middle initial, a conflict or ambiguity in identifying this person is highly unlikely.  
**Example: [http://lccn.loc.gov/no2014170428 Edward J. Geisweidt] was established without any additional qualifications: he is the only ''Geisweidt'' in the name authority file, and with a middle initial, a conflict or ambiguity in identifying this person is highly unlikely.
*Leave spaces in between initials in personal names (for example: Urwin, G. G. ǂq (George Glencairn))
*Add birth and/or death dates to the authorized access point whenever available. In the absence of a conflict, do not change an existing authority record solely to add dates. (However, closing out an open birth date is acceptable.)
*Add birth and/or death dates to the authorized access point whenever available. In the absence of a conflict, do not change an existing authority record solely to add dates. (However, closing out an open birth date is acceptable.)
*Make the following additions to the preferred name if applicable:
*Make the following additions to the preferred name if applicable:

Revision as of 10:37, 15 September 2015

MARC field 100 in the authority and bibliographic formats contains information on formulating a personal name used as a main entry in a bibliographic record. Since the same instructions apply for formulating access points of persons regardless of where it is used in a bibliographic record, this article covers MARC fields 600, 700, and 800.

Commonly-used tags

First Indicator - Type of personal name entry element

0 - Forename
1 - Surname
3 - Family name 

Second indicator

Undefined

Subfields

ǂa - Personal name (NR)
ǂb - Numeration (NR)
ǂc - Titles and words associated with a name (R)
ǂd - Dates associated with a name (NR)
ǂe - Relator term (R)
ǂf - Date of a work (NR)

Policy and formulation

Basic formulation of personal names

  • In general, avoid creating unqualified personal name access points, even in the absence of a conflict. Use judgment, however, as some names may be unusual enough in themselves, so that the addition of active dates or a title or another designation would be superfluous.
    • Example: Edward J. Geisweidt was established without any additional qualifications: he is the only Geisweidt in the name authority file, and with a middle initial, a conflict or ambiguity in identifying this person is highly unlikely.
  • Leave spaces in between initials in personal names (for example: Urwin, G. G. ǂq (George Glencairn))
  • Add birth and/or death dates to the authorized access point whenever available. In the absence of a conflict, do not change an existing authority record solely to add dates. (However, closing out an open birth date is acceptable.)
  • Make the following additions to the preferred name if applicable:
    • title of royalty (see 9.19.1.2.1)
    • title of nobility (see 9.19.1.2.2)
    • title of religious rank (see 9.19.1.2.3)
    • the term Saint (see 9.19.1.2.4)
    • the term Spirit (see 9.19.1.2.5)
    • an other designation associated with the person (see 9.19.1.2.6)
  • Make the following additions to the preferred name in this order of preference, in case of conflict (RDA 9.19.1.3-7)
    • Fuller form of name (RDA 9.19.1.4)
    • Period of activity of the person and/or profession or occupation (RDA 9.19.1.5). Folger practice: in general, prefer century dates over specific years of activity, and over profession or occupation
    • Other term of rank, honour, or office (RDA 9.19.1.6)
      • New authority records: Folger practice: include 'Sir', etc., if the person used the title.
      • Existing authority records: LC practice/PCC practice. Unless otherwise changing an existing authorized access point (e.g., conflict), do not change an existing AACR2 or RDA heading merely to add or remove an Other designation associated with a person.
    • Other designation (RDA 9.19.1.7)
  • Existing authority records
    • Folger practice: do not change an existing access point merely to upgrade to our current practice as long as it is technically RDA-correct

External links