Optional Fields
For the optional fields in a name authority record, include or add these fields whenever the information is readily available in the resource being cataloged, and can quickly be added. No significant research should be done, and no extra sources need be consulted, to find values for the optional attributes in a name authority record.
Research in OCLC
Personal Names
- When creating a personal name authority record (NAR), search the OCLC bibliographic file in addition to the Name Authority File (NAF):
- Keyword search using terms from the work cat
- e.g., "robert b miller" "american institutes for research"
- Browse search by personal name
- e.g., miller, robert b
- Keyword search using terms from the work cat
Citing Catalog Sources in Authority Records
- Add a 670 NAR citation for any transcribed names (“usage”) and unauthorized access points found in the OCLC bibliographic file (“catalog”) when both of the following conditions are met:
- Results retrieved in the OCLC bibliographic file are clearly for the person represented by the NAR
- Retrieved bibliographic records (“catalog sources”) provide biographical information not already present in the NAR’s 670 citations
Example:
Work cat (CGP 1200796) citation in draft NAR:
670__ Development of a taxonomy of human performance. Design of a systems task vocabulary, 1971: ǂb t.p. (Robert B. Miller) Literature cited (Miller, R. B.)
Searching and browsing of the OCLC bib file revealed publications written by the same person under different names:
Each bibliographic record was opened to confirm similar subject matter and to check for additional personal name usage (transcribed in 245 or 500).
Resulting citation in NAR:
670 __ OCLC, May 24, 2022 ǂb (access points: Miller, Robert B. (Robert Bruce), 1910- , Miller, Robert Bruce, 1910- ; usage: Robert B. Miller)
Citing Non-Catalog Sources in Authority Records
- Whenever possible, use non-catalog sources to verify biographical details that appear in catalog sources.
- Whenever possible, provide 670 citations from non-catalog sources to justify additions to names in authorized access points.
Example:
no2018141858
100 1_ Bright, Michael R. ǂq (Michael Richard), ǂd 1978-
670 __ United States. Congress. Senate. Committee on Banking, Housing, and Urban Affairs. Nominations of Elad Roisman, Michael R. Bright, Rae Oliver Davis, and Dino Falaschetti, 2018: ǂb t.p. (Michael R. Bright, of the District of Columbia, to be President, Government National Mortgage Association) p. 2 (Michael Bright; career as a Senate staffer; Mr. Bright; leading voice on housing finance policy) p. 48 (Michael Richard Bright; date of birth: 29 Sept. 1978; place of birth: Warren, Ohio)
The middle name “Richard” and birth year of 1978 are both justified by the text viewed on page 48 of the work cited, not from a bibliographic record.
Using Data from Catalog Sources in Access Points
- Under rare circumstances, authorized access points for persons may be formed using information from unauthorized access points found in existing bibliographic records (that is, from access points created by catalogers but not established in the NAF).
- Although these biographical details cannot be verified by GPO, their use in an authorized access point is permitted by the NACO Participants’ Manual, pages 21-22.
- Generally, for access points found in the OCLC bibliographic file which have not become a person’s authorized access point, add a variant access point (MARC 400 field) to the person’s NAR.
- Reminder: Check the NAF to ensure none of the added variants conflict with an authorized access point (MARC 1XX field).
Example:
[Hypothetical example]
100 1_ Hill, Robert B., ǂd 1934-
400 1_ Hill, Robert B. ǂq (Robert Bernard), ǂd 1934-
400 1_ Hill, Robert Bernard, ǂd 1934-
670 __ OCLC, Sept. 24, 2022 ǂb (access points: Hill, Robert B. (Robert Bernard), 1934- , Hill, Robert Bernard, 1934- ; usage: Robert B. Hill)
The middle name “Bernard” and birth year of 1934 are both taken from unauthorized access points in existing bibliographic records. The accuracy of these details could not be confirmed by a reasonable amount of additional research. Nevertheless, the information is used to distinguish the authorized and variant access points in this NAR from n92802682 and n79017954.
Bibliographic File Maintenance
- When establishing a NAR for a person who already exists in the OCLC bibliographic file, maintenance may be needed for the Library of Congress (LC) catalog. For information about when and how to report records to LC, see Guidelines for reporting NACO BFM.
Example:
A GPO cataloger created a name authority record:
no2022100199
100 1_ Whitehead, Joan M.
400 1_ Whitehead, Joan Margaret
670 __ OCLC, July 25, 2022 ǂb (access points: Whitehead, Joan; Whitehead, Joan M.; Whitehead, Joan Margaret; usage: Joan Whitehead; Joan M. Whitehead)
The cataloger then performed a Browse search in the LC catalog for AUTHORS/CREATORS beginning with: Whitehead, Joan
There was one result: https://lccn.loc.gov/73169541
At the time of the cataloger’s search, the access point in LCCN 73169541 was: Whitehead, Joan. Because the access point represented the same entity as the new NAR but did not match the 100 in the NAR, it met the criteria for NACO’s Reportable BFM.
The cataloger emailed [email protected] to report that BFM was needed for LCCN 73169541 due to the creation of no2022100199.
Corporate/Conference Names
Before adding a new corporate name to the authority file, always search the OCLC authority file to see if the name is already established. If no record for the name is found, additionally search the OCLC authority file for any possible earlier (predecessor) names. One way to do this, is to conduct a keyword search using the parent body (should one exist), plus only one (at a time) of the following significant keywords. For example, when establishing: "United States. Environmental Protection Agency. Management Information Systems Division," enter the keywords: "Environmental Protection Agency Management." Conduct two additional searches: "Environmental Protection Agency Information," and: "Environmental Protection Agency System*." Use wildcards as needed to retrieve differing forms of a keyword.
If you find a similar name to the one you are creating, you must determine the relationship between the two names through research. For example: consult the publication in hand (the resource being cataloged), the Internet (including uncataloged publications found there), back issues of Carroll's Federal Directory, and of course, make phone calls or send emails. If you identify the existing authority record as the immediate predecessor, link the two records using properly coded reciprocal 510 or 511 fields. Only link immediately consecutive names; do not link names that are "twice removed." If a different type of relationship is found between your name and the existing name, and you feel it is important to bring out, you may add that information, reciprocally, to both records in the appropriate fields. Sometimes, it is helpful to add a 667 note such as: "cannot link directly to: [insert other name]," or "not same as: [insert other name]."
How Much Research Should Be Performed … ?
Perform the following research:
1. Quickly check the work cataloged and the agency Web site, to see if either contains a history section, which may include the very information you are seeking.
2. Search Carroll's Federal Directory for the name you are establishing (or updating). Use the year of Carroll's that matches the resource cataloged (or the closest year available). Next, search Carroll's Federal Directory for the similar, pre-existing name you found in OCLC. For this name, start with the same issue of Carroll's used to search for the name you are establishing, but if not found, search the next issue of Carroll's that matches (or comes closest to) the year cited in a 670 field of the OCLC record for the similar, pre-existing name. If both names are found, work your way through the intervening years of Carroll's (you may sample every few years), in order to identify name changes. This research may prove to be either conclusive or inconclusive.
Examples of a conclusive relationship:
Example:
a. A linear name change is identified. (Record the relationship)
b. Both names co-exist simultaneously. (Usually, no relationship is recorded. A 667 note may be added, in the form of "Not same as [other name]" or "Do not confuse with [other name]."
Negative evidence may also be considered conclusive. Examples:
Example:
a. Multiple name changes are found in between the two names; and two or more of these are not found in the OCLC authority file. No relationship is recorded. Option: if two intervening names are found in Carroll's which are not in OCLC's authority file, and the linear progression appears straightforward, you may search OCLC's bibliographic file for these names. If one or more are found, and the task of recording this progression appears to be fairly straightforward, you may apply the option in number 3 below, of establishing one or more of these names from the bibliographic records found in OCLC.
b. Two name changes are found, so that the two bodies you are seeking are linked to the same intervening body. If the intervening body is found in the OCLC authority file, all 3 bodies can be sequentially linked. If the intervening body is not found in the OCLC authority file, no relationship is recorded. You may, however, add a 667 note to the records for both bodies, in the form of "Cannot link directly to [other name]" or "Unable to link directly to [other name]." At the same time, you may also include the information found in Carroll's about the intervening body in a 670 note. Follow the name of the intervening body with "[no access point in OCLC, (insert date searched)]." (Or: "[no publications in OCLC database, (insert date searched)]") See LC-PCC PS 32.1.1.3: Earlier names not likely to be needed as relationships.
3. Now, you should search OCLC's bibliographic file for the intervening corporate body. If not found, you are done. However, if you do find the name in even one bibliographic record in OCLC, you may create an authority record for this name, with the caveat that the name is transcribed in the descriptive portion of the record. If the name is only found in access points (1XX, 6XX, 7XX) but not in the description (245, 260, 264, 5XX), do not create an authority record for it. If the name is found in the description, create an authority record for this intervening corporate body, formatting the first 670 in accordance with Name Authorities: 67X Citation Fields, OCLC Database. Be selective. You may list multiple usages that seem to be accurate transcriptions, and multiple headings that adhere to the rules under which the record was created. Once you create the authority record for the intervening corporate body, link it to its predecessor and successor records, and remove any preliminary 667 notes and "[no publications in OCLC database]" phrases. [Note: the procedure just described is somewhat out of sequence. This paragraph, which begins with "Now, you should search OCLC's bibliographic file," should logically occur after the third sentence in the paragraph just above this, after "no relationship is recorded." This somewhat illogical sequence is offered as a time-saver, since: (1) the information recorded from Carroll's provides a convenient place-holder, and (2), this information usually remains in the record since publications are not usually found in OCLC.]
Examples of an inconclusive relationship:
Example:
a. Only one or none of the names are found in Carroll's.
b. The names found in Carroll's are different, and cannot be matched with those you are seeking.
If searching Carroll's is inconclusive, contact the agency via phone call or email, asking if a direct relationship can be identified between the two names. If not, your research is completed, and you may establish the new corporate body without recording any relationship.
While the above research may seem excessive when similarly named corporate bodies are only cited in publications that may be 35 or more years old, surprises have come up, when the earlier name has persisted, and only recently changed to the name that is being established. It is worth a couple of hours of research to identify or dismiss such relationships, in order to expand user access to successors and predecessors.
When to Consult Additional Sources
If research in OCLC does not result in any possible related names, it is usually not necessary to consult any additional sources beyond the resource cataloged. However, if the resource cataloged is not issued by the entity whose name you are establishing in the authority file, do consult at least one additional source. This guidance would apply to all names, corporate or personal, that are needed as subjects for the resource cataloged (unless said name also issued the work). For a corporate body, it will usually suffice to consult its Web site, in addition to the resource cataloged. For a personal name, a few searches on the Internet will usually suffice to determine the preferred name. GPO's local policy is based on its experience that publications issued by an entity tend to be more accurate in rendering their name than publications not issued by them.
Therefore, for corporate bodies, GPO prefers the name found in items issued by that body. When a resource is not issued by a corporate body, consult an additional source such as its Web site, which is issued by that body. If the name on the Web site or other source issued by the body differs from the name in the resource cataloged, use the name on the Web site as the preferred name, and the name on the resource cataloged as the variant name. Use the resource cataloged as the first 670, even though the name cited therein was not chosen for the 1XX. Use the Web site (or other source issued by the body) as the second 670. Many USGS reports (in various series) exemplify this situation.
Example:
On the t.p. of the resource cataloged: "prepared in cooperation with City of Hopkinsville, Kentucky, Community Development Services." This body did not issue this USGS report, therefore, consult: City of Hopkinsville, Community and Development Services Web site: "City of Hopkinsville, Community and Development Services." [Note the addition of the word "and" after "Community."]
Thus: 1101 Hopkinsville (Ky.). ǂb Community and Development Services
4101 Hopkinsville (Ky.). ǂb Community Development Services
670 Flood-inundation maps for an 8.9-mile reach of the South Fork Little River at Hopkinsville, Kentucky, 2013: ǂb PDF t.p. (City of Hopkinsville, Kentucky, Community Development Services)
670 Community and Development Services, City of Hopkinsville [Ky.] Web site, Apr. 9, 2013. [Note: no ǂb is needed, because it would add nothing to the ǂa, which itself adds nothing to the 1XX.]
What if the Web site contains the same exact name as the item—should the Web site still be cited even though it contains no additional information? In this situation, when the item is not issued by the body, go ahead and cite the Web site in an additional 670, even though the name found is redundant. Thus:
Example:
On the t.p. of the resource cataloged: "prepared in cooperation with the Massachusetts Department of Fish and Game, Division of Ecological Restoration."
1101 Massachusetts. ǂb Department of Fish and Game. ǂb Division of Ecological Restoration
670 Estimated sediment thickness, quality, and toxicity to benthic organisms in selected impoundments in Massachusetts, 2013: ǂb PDF t.p. (Massachusetts Department of Fish and Game, Division of Ecological Restoration)
670 Massachusetts Department of Fish and Game, Division of Ecological Restoration Web site, Apr. 10, 2013.
When searching the Internet for names, in the situations described above, generally avoid citing Wikipedia. This instruction applies to names, not to subjects. For the Wikipedia policy on subjects, see Subject Cataloging: Subject Heading Proposals, Background and Tips. For names, use sources other than Wikipedia whenever possible.
Tips for contacting agencies
- Take time to identify knowledgeable contacts. Use the agency's Web site, or Carroll's Federal Directory.
- Do your homework first so you can determine, identify, and develop your questions.
- Begin with: "Hello, I'm calling/emailing from the U.S. Government Publishing Office."
- Explain what we do, why, and what your questions have to do with this.
- Use layperson language, not cataloger language. Instead of using the term "corporate body," which might connote "corporations," speak in terms of "government authors and issuing bodies of publications," for which we provide "access points" for searching.
- Explain what you found, and what you don't know.
- Ask open-ended questions.
How to Recode an Existing NAR from AACR2 to RDA
- Change coding in Rules ("z") and 040 (ǂe "rda") to identify the record as RDA.
- Ensure the 1XX is RDA compliant. If it is not, change it.
- If you change the 1XX, enter the former 1XX in a 4XX field. Add a ǂw to this 4XX field using either of the following values: (a) nnea for an old, valid AACR2 heading, or, (b) nne for a valid RDA variant access point. In case of doubt, use nnea. Don't forget to apply the rules of NACO Normalization to ensure that this 4XX does not normalize to the same form as the 1XX. If it does, remove it.
- If there is a 7XX field in the record:
- If the 7XX field matches the 1XX field, delete the 7XX field.
- If the 7XX field has a 2nd indicator 4, delete the 7XX field.
- If the 7XX and the 1XX field do not match, then do not delete the 7XX field.
- At the time of the re-coding, add references (4XX and 5XX) and 670 citations to the authority record as needed, either with new information, or using information already contained in the record. You may optionally add optional fields such as 046, 368, 37X, etc., if the information is readily and speedily available. Otherwise, do not add any optional fields.
- 5XX references in AACR2 format do not need to be changed to RDA. They are acceptable under PCC rules.
- If present, delete the MARC 667 instruction to re-evaluate before use in RDA.