Add Bookmark

Please click in the document at the location of desired bookmark.

Find URL

Please click in the document at the location for the desired URL.

Warning

Content displayed is Filtered. Hits in filtered content are not currently visible in the document as displayed. To view all hits, select the Full view from the View Text menu.

LC-PCC
Policy Statement for Chapter 9: Identifying Persons
LC-PCC PS for 9.0
PURPOSE AND SCOPE
LC practice/PCC practice: In addition to the languages named here, see Policy Statement Appendix F.0 for the following languages:
Congolese, Ethiopian, and Somali names
Filipino names
Fictitious Entities and Real Non-Human Entities
LC practice/PCC practice: Apply this chapter to fictitious entities and real non-human entities following the guidelines below:
No LCSH Authority Record Exists
Create a name authority record for the entity following RDA instructions and NACO guidelines, whether needed as a creator, contributor, etc., under RDA, or needed only for subject access. Do not create a subject proposal for LCSH.
LCSH Authority Record Exists
If needed as a creator, contributor, etc., under RDA, create a new name authority record and notify the Policy & Standards Division (policy@loc.gov) to cancel the existing subject authority record.
Optionally, a new name authority record may be created for such an entity if needed only for subject access. If a name authority record is created, notify the Policy & Standards Division (policy@loc.gov) to cancel the existing subject authority record.
Future activity: A project to transition all fictitious and real non-human entities from LCSH will be conducted as resources are available.
[2013-12]
LC-PCC PS for 9.2.2.4
RECORDING PREFERRED NAME FOR PERSON
LC practice/PCC practice: In addition to the languages named here, see Policy Statement Appendix F.0 for the following languages:
Congolese, Ethiopian, and Somali names
Filipino names
[2017-07]
LC-PCC PS for 9.2.2.5.2
ALTERNATIVE
LC practice/PCC practice for Alternative: Do not apply the alternative.
[2012-09]
LC-PCC PS for 9.2.2.5.3
NAMES WRITTEN IN A NON-PREFERRED SCRIPT
Language and Script Preferred by LC and PCC
For the instructions related to RDA 9.2.2.5.3, the language preferred by the Library of Congress for reference sources is English; the preferred script is the Latin script.
Authorized access points in authority and bibliographic records should be in the Latin script. When transliteration is necessary, follow the ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts, approved by the Library of Congress and American Library Association, with note to the exceptions recorded at http://hdl.loc.gov/loc.standards/docs.roman
Non-Latin forms may be recorded as variant access points in authority records (MARC field 4XX) and/or as parallel fields in bibliographic records (MARC field 880) for these languages/scripts: Perso-Arabic script (e.g., Arabic, Persian, Pushto, Urdu); Hebrew, Yiddish; Chinese, Japanese, Korean; Cyrillic-based scripts; and Greek.
Applicability
LC practice/PCC practice: Persons who bear names derived from a non-Latin script but who write in a Latin script language should not be treated under this instruction. The decision that the person is writing in a Latin script language is based on the first item cataloged, i.e., the fact that the text of this item was originally written in a Latin script language. If it becomes evident later that most of the person’s works were written in a non-Latin script, apply the provisions of this policy statement.
[2012-10]
LC-PCC PS for 9.2.2.5.3
ALTERNATIVE
LC Practice/PCC Practice for Alternative:
Chinese, Japanese, Korean, Cyrillic: Apply the alternative when the first element of the preferred name begins with either a given name or a surname. If a person is likely to appear in general English-language reference sources, search Academic American Encyclopedia, The Encyclopedia Americana, and the New Encyclopaedia Britannica. If the name is found in all three sources in a single form, use that form. If the form varies in these three sources, use the form found in New Encyclopaedia Britannica. If the name is not found in all three of these sources, use the systematically romanized form of the name. Exception: For famous persons entered under given name but not found in all three of the general English-language encyclopedias because of specialized fame, consult major specialized encyclopedias (e.g., New Catholic Encyclopedia, The Oxford Classical Dictionary) to determine if there is a well-established English-language form of the name. ("Found in" the reference source means that there is an article under the person’s name.)
For persons of too recent fame to be included in the three general English-language encyclopedias named above (e.g., new authors, dancers, persons recently becoming famous as political or cultural figures), consult the yearbooks of the encyclopedias and such major newspapers as The New York Times and The Washington Post to determine if there is a well-established English-language form of the name.
Hebrew Alphabet: Follow this order of preference in choosing the heading for persons with names in the Hebrew alphabet:
1.
If the name is found prominently in a romanized form in the resource being cataloged in a language using the Hebrew alphabet, use this form.
2.
If the name is found as the heading for an article about the person in The Encyclopaedia Judaica or The Encyclopedia of Jews in the Islamic World, use this form. If the form varies in these two sources, use the form found in The Encyclopaedia Judaica.
3.
If the name is found in a romanized form in a widely-known and easily-consulted free online source, use this form, especially where a person who writes or is written about primarily in the Hebrew script provides a preferred romanized form of the name in that source (e.g., Facebook, Linkedin) or, failing such a source, a general source (e.g., Wikipedia).
4.
Otherwise, use the systematically romanized form of the name.
5.
However,
a)
If the authorized access point for an author who writes in a language using the Hebrew alphabet reflects the systematically romanized form and a subsequently-received resource containing the name in a Hebrew-alphabet language shows a non-systematically romanized name (i.e., a “found romanization”), generally do not change the authorized access point. This means that only in exceptional cases will systematically romanized names be candidates for change.
b)
If the authorized access point for an author who writes in a language using the Hebrew alphabet reflects a non-systematically romanized form and a subsequently received resource containing the name in a Hebrew-alphabet language shows a different non-systematically romanized form (i.e., a different “found romanization”), do not change the authorized access point until the different form clearly predominates.
All Other Languages Written in Non-Latin Scripts: Apply the alternative to use a well-established form in English as the preferred name if the cataloger’s judgment and experience suggests that the person is likely to be found in general English-language reference sources. Consider providing variant access points for forms not selected as the preferred name.
[2012-10]
LC-PCC PS for 9.2.2.8
INDIVIDUALS WITH MORE THAN ONE IDENTITY
LC practice/PCC practice: If an authorized access point is needed for a bibliographic identity recorded as a variant name in a 400 field in an existing name authority record, create a separate RDA name authority record for that identity. Modify the existing authority record to convert the 400 field to a 500 field.
See the FAQ-LC/PCC practice for creating NARs for persons who use pseudonyms for additional information on individuals with more than one identity.
[2013-12]
LC-PCC PS for 9.2.2.11.1
ARTICLES AND PREPOSITIONS
LC practice/PCC practice: For the application of this instruction, treat English as the preferred language of the agency creating the data.
[2012-10]
LC-PCC PS for 9.2.2.25
ALTERNATIVE
LC practice/PCC practice for Alternative: Apply the alternative.
[2012-10]
LC-PCC PS for 9.2.2.26
ALTERNATIVE
LC practice/PCC practice for Alternative: Apply the alternative.
[2012-10]
LC-PCC PS for 9.3.1.3
RECORDING DATES ASSOCIATED WITH PERSONS
LC practice/PCC practice: Record dates in terms of the Gregorian calendar.
When supplying dates in MARC 046 field, use the Extended Date Time Format (EDTF) schema in all cases except for centuries. For EDTF, supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd, and 'edtf' in $2. Follow the instructions below if encoding date(s) in a name authority record.
 
 
 
EXAMPLE
RDA dates in EDTF date scheme (provide ‘edtf’ in 046 $2)
CategoryRDA presentationEDTF coding in 046
Single year19641964
Year/Month/Day1964 June 271964-06-27
Year/Month1964 June1964-06
Early A.D. date65 A.D.0065
B.C. date361 B.C.-0360 (note there is a difference of one because the B.C. system has no year zero)
Probable date1816?1816?
Approximate dateApproximately 9310931~
Known to be one of two years1666 or 1667[1666,1667]
RDA dates in ISO 8601 date scheme (no need to provide a source in $2)
CategoryRDA presentationISO 8601 coding in 046
Century20th century19
 
 
 
[2017-07]
LC-PCC PS for 9.3.1.3
OPTION
LC practice/PCC practice for Optional addition: Apply the optional addition to record a more complete date when recording the element in MARC field 046, if considered important. See 9.19.1.3 for instructions on adding more complete dates to authorized access points for persons. Use English for the month in the access point.
[2015-09]
LC-PCC PS for 9.3.2.3
RECORDING DATE OF BIRTH
LC practice/PCC practice: Use a hyphen after date of birth when recording the date in an authorized access point; do not use the term “born” with the date.
[2013-05]
LC-PCC PS for 9.3.3.3
RECORDING DATE OF DEATH
LC practice/PCC practice: Use a hyphen before the date of death when recording the date in an authorized access point; do not use the term “died” with the date.
[2012-07]
LC-PCC PS for 9.3.4.3
RECORDING PERIOD OF ACTIVITY OF PERSON
LC practice/PCC practice: When recording the 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.
[2017-03]
LC-PCC PS for 9.4.1.4.1
PERSON WITH THE HIGHEST ROYAL STATUS WITHIN A STATE, ETC.
LC practice/PCC practice: Record the person’s title and the name of the state or people in English.
[2012-10]
LC-PCC PS for 9.4.1.4.2
CONSORTS OF ROYAL PERSONS
LC practice/PCC practice: Record the title of the consort in English.
[2012-10]
LC-PCC PS for 9.4.1.4.3
CHILDREN AND GRANDCHILDREN OF ROYAL PERSONS
LC practice/PCC practice: Record the title in English.
[2012-10]
LC-PCC PS for 9.4.1.7
BISHOPS, ETC.
LC practice/PCC practice: Record the title and the name of the see in English.
[2012-10]
LC-PCC PS for 9.6.1.3
RECORDING OTHER DESIGNATION ASSOCIATED WITH PERSON
LC practice/PCC practice: When recording an Other designation associated with person for RDA 9.6.1.6-RDA 9.6.1.9, choose a term that is sufficiently specific to distinguish the person from other persons with the same name. Prefer a controlled vocabulary, when appropriate (see DCM Z1 for MARC field 368).
 
 
 
EXAMPLE
Biblical patriarch
Uses a more specific term to distinguish the Biblical patriarch Jacob from other Biblical figures named Jacob
 
 
 
[2017-03]
LC-PCC PS for 9.16.1.3
RECORDING PROFESSION OR OCCUPATION
LC practice/PCC practice: Prefer a controlled vocabulary, such as LCSH or MeSH, when recording profession or occupation terms. Use judgment when deciding the appropriate level of specificity. When recording as an element in MARC 374 subfield $a, capitalize the term (or first word of the term) in each subfield $a, and record the source in subfield $2. See Policy Statement 9.19.1.6 for instructions on adding a profession or occupation term to an access point.
 
 
 
EXAMPLE
 
100 1#$a Sweeney, George $c (Notary)
374 ##$a Notaries $2 lcsh
 
100 1#$a Christov, Christo $c (Flute player)
374 ##$a Flute players $2 lcsh
 
100 1#$a Schneider, Catherine $c (Pianist)
374 ##$a Pianists $2 lcsh
 
100 1#$a Thompson, Simon $c (Professor)
374 ##$a College teachers $2 lcsh
374 ##$a University and college faculty members $2 lcdgt
 
100 1#$a Frey, Viola, $d 1933-2004
374 ##$a Ceramicists $2 aat
Term for profession or occupation not needed in access point
 
 
 
Use terms for profession or occupation without indication of the person’s gender, nationality, religion, etc., unless such characteristics are part of the definition of the term itself (e.g., a Rabbi is a Jewish religious leader).  Prefer gender-neutral terms to gender-specific terms when possible (e.g., Actor instead of Actress and Fire fighter instead of Fireman). Information not included as part of the profession or occupation term may be appropriate for other elements, such as Other designation associated with the person, see 9.6.1.9.
 
 
 
EXAMPLE
 
100 1#$a Allen, Debbie, $d 1950-
374 ##$a Choreographers $2 lcsh
not 374 ##$a African American choreographers $2 lcsh
not 374 ##$a Women choreographers $2 lcsh
 
100 1#$a Ishihara, Fumio, $d 1900-1971
374 ##$a Novelists $2 lcsh
not 374 ##$a Novelists, Japanese $2 lcsh
but
 
100 1#$a Iwasaki, Mineko, $d 1949-
374 ##$a Geishas $2 lcsh
 
 
 
When the term for the profession or occupation includes words that are part of the profession or occupation rather than an indication of the person’s gender, nationality, etc., these may be recorded.
 
 
 
EXAMPLE
 
100 1#$a Siegemund, Justina, $d 1636-1705
374 ##$a Midwives $2 ilot
 
100 1#$a Griffin, Chad $c (Gay rights activist)
374 ##$a Gay rights activist
 
100 1#$a Lockett, Tony, $d 1966-
374 ##$a Australian football players $2 lcdgt
A professional athlete in the sport of Australian football
 
 
 
[2017-03]