LC-PCC PS for 9.19.1.1
GENERAL GUIDELINES ON CONSTRUCTING AUTHORIZED ACCESS POINTS TO REPRESENT PERSONS
Authority Records in the LC/NACO Authority File
LC practice/PCC practice: Consult the PCC Post RDA Test Guidelines for up-to-date instructions on the issues related to RDA and AACR2 authority records and their use in bibliographic records.
Giving Dates for Persons
LC Practice/PCC practice: If giving both a date of birth and a date of death or giving a span of dates for period of activity, separate the dates with a hyphen. If giving only a date of birth, use a hyphen after the date; do not use the term “born” with the date. If giving only a date of death, use a hyphen before the date; do not use the term “died” with the date. If giving a date or dates for period of activity, use “active” and “century” rather than the abbreviations “fl.” and “cent.” The term "active" should appear before the first period of activity date (e.g., "active 12th century) unless another term such as "jin shi" is used.
Differentiating Authorized Access Points for Persons
LC practice/PCC practice: When creating a new authority record for a person, and there are no additions readily available to differentiate the access point in the new authority record, make an addition to the existing authorized access point.
Changes to Authorized Access Points for Persons
LC practice/PCC practice: Generally, do not change the authorized access point in an existing authority record coded "rda" that is fully established unless one or more of these conditions applies:
1.
a date of death is added to an authorized access point that has an open date of birth, or a date of birth is added to an authorized access point that has only a date of death
2.
the authorized access point must be changed to break a conflict with another authorized access point
3.
an error in the authorized access point must be corrected (e.g., "1979-" instead of "1970-")
4.
a person has requested a change to their authorized access point that can be accommodated by current cataloging instructions
5.
there has been a change in cataloging instructions affecting the authorized access point.
On rare occasions, a person requests that the formulation of their authorized access point be changed (e.g., to remove a date of birth or a fuller form of name). LC and PCC should attempt to honor such requests by changing the appropriate fields in the record, and indicate in a note that the person's preference has been followed.
For instructions on updating authorized access points on records that are not coded "rda" (e.g., AACR2 or AACR2-compatible) see the PCC Post RDA Test Guidelines.
Printer’s Widows
1.
If a woman is referred to as a "printer’s widow" in the resource being cataloged and/or in reference sources and her personal name is known, use her personal name for constructing the authorized access point. In the authority record, add a variant access point for the personal name of the printer and qualify by "widow of."
2.
If the widow of a printer is identified only as the widow of the printer, establish the authorized access point as a phrase in direct order. In the authority record add a variant access point consisting of the husband’s name followed by "widow of".
3.
If the widow of a printer is identified only by a surname and term such as “widow,” establish the authorized access point following the provisions in 9.2.2.9.3, and add a variant access point for the name in direct order.
EXAMPLE
source
Printed by the Widow Cuthbert | |
100 1# | $a Cuthbert, $c Widow |
400 0# | $a Widow Cuthbert |
[2017-07]
LC-PCC PS for 9.19.1.1
OPTION
LC practice/PCC practice for Optional addition: See Policy Statement 9.19.1.2.6, Option (Other Designation Associated with the Person), Policy Statement 9.19.1.3, Option (Date of Birth and/or Death), Policy Statement 9.19.1.4, Option (Fuller Form of Name), Policy Statement 9.19.1.5, Option (Period of Activity of the Person), Policy Statement 9.19.1.6, Option (Profession or Occupation), Policy Statement 9.19.1.7, Option (Other Term of Rank, Honour, or Office), and Policy Statement 9.19.1.8, Option.
[2015-03]
LC-PCC PS for 9.19.1.2.6
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Apply if the cataloger considers it important for identification.
Existing Authority Records
LC practice/PCC practice for Optional addition: 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.
[2014-02]
LC-PCC PS for 9.19.1.3
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Add a date of birth and/or date of death to new authority records, even if not needed to distinguish between access points.
Existing Authority Records
LC practice/PCC practice for Optional addition: Unless otherwise changing the 100 field, do not add a date of birth and/or date of death to an existing AACR2 or RDA authorized access point without dates.
Optionally, add a death date to an authorized access point that has an open birth date, and add a birth date to an authorized access point that has only a death date.
[2017-07]
LC-PCC PS for 9.19.1.4
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Apply the option to provide a fuller form of name if a part of the forename or surname used in the preferred name is represented by an initial or an abbreviation, if the cataloger considers it important for identification. Add unused forenames or surnames only if needed to distinguish one access point from another (see 9.19.1.4).
Existing Authority Records
LC practice/PCC practice for Optional addition: Unless otherwise changing an existing heading (e.g., conflict), do not change an existing AACR2 or RDA heading merely to add or remove a fuller form of name.
[2013-01]
LC-PCC PS for 9.19.1.5
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Generally do not apply.
Existing Authority Records
LC practice/PCC practice for Optional addition: 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 a Period of activity.
[2015-03]
LC-PCC PS for 9.19.1.6
PROFESSION OR OCCUPATION
LC practice/PCC practice: When adding a profession or occupation term to an access point in 100 subfield $c, use a singular form of the term. See Policy Statement 9.16.1.3 for instructions on recording profession or occupation as an element.
[2015-03]
LC-PCC PS for 9.19.1.6
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Generally do not apply.
Existing Authority Records
LC practice/PCC practice for Optional addition: 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 a Profession or Occupation.
[2015-03]
LC-PCC PS for 9.19.1.7
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Apply if the cataloger considers it important for identification.
Existing Authority Records
LC practice/PCC practice for Optional addition: 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 term of rank, honour or office.
[2015-03]
LC-PCC PS for 9.19.1.8
OPTION
New Authority Records
LC practice/PCC practice for Optional addition: Generally do not apply.
Existing Authority Records
LC practice/PCC practice for Optional addition: 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.
[2015-03]
LC-PCC PS for 9.19.2.1
GENERAL GUIDELINES ON CONSTRUCTING VARIANT ACCESS POINTS TO REPRESENT PERSONS
Additions to the Variant Access Point to Resolve Conflicts
LC practice/PCC practice: In addition to the reason given in the instruction, also make additions to a variant access point when needed to break a conflict with an authorized access point in another record, or with another variant access point in the same record.
Printer’s Widows
See the section on printer’s widows in Policy Statement 9.19.1.1.
[2012-10]