ALCTS-CCS/PCC Name and Title Authority Training Materials
28 June 2003
1. Introduction
1.1. Purpose and Scope
1.2. What is Authority Work?
1.2.1. Difference between authority work and authority control
1.3. Why do Authority Work?
1.3.1. Objects of the catalog: uniform headings, commonly known principle
1.4. Relationship of the Authority Record to the Bibliographic File
1.4.1. Various ways systems handle authorization
1.4.2. Evaluating NARs: does the heading represent the name I need?
1.4.3. Special problems (e.g., authorization of 1XX/240 uniform titles)
1.4.4. Name or subject?
1.4.4.1. Use of name headings in subject fields (SCM H430, etc.)
1.5. Benefits of Authority Control
1.5.1. Catalogers/Technical Services librarians
1.5.2. Public Services Librarians
1.5.1. Vendors
1.5.2. Administrators
1.6. Administration of authority control
1.6.1. In-house authority control
1.6.1.1. Role of the copy cataloger vs. professional cataloger
1.6.1.2. Authority librarians
1.6.1.3. Maintenance of the file over time
1.6.2. Outsourcing
1.6.2.1. Various possibilities
2. Resources and how they work
2.1. AACR2
2.2. MARC21 Format for Authority Data
2.3. LCRIs
2.4. NACO Participants Manual
2.5. Maxwell, R. Maxwells Guide to Authority Work
2.6. Understanding MARC Authority Records
2.7. The Authority Files Themselves (incl. demo)
2.7.1. LC (http://authorities.loc.gov)
2.7.2. RLIN
2.7.3. OCLC
2.7.4. Other Authority Files, e.g.,
2.7.4.1. Biblioth่que nationale de France (http://noticesautorites.bnf.fr:8095/)
3. Basics of the MARC Authority Record
3.1. Purpose and scope
3.2. Headings (1XX)
3.3. See references (4XX)
3.4. See also references (5XX)
3.5. Notes (6XX)
3.6. Linking references (7XX)
3.7. Content designators
3.7.1. Leader and directory
3.7.2. Variable control fields
3.7.3. Variable data fields
4. Personal Names
4.1. Relationship of the authority 1XX to the bibliographic record (show how the heading looks in the bib record)
4.2. Heading (100)
4.2.1. Choice of name
4.2.2. Entry element
4.2.2.1. Normalization rules
4.2.3. Additions to names
4.2.3.1. Additions to distinguish identical names
4.2.3.2. Other types of additions (e.g., for titles of nobility, etc.)
4.2.4. Undifferentiated names
4.2.5. Names in unusual languages (short reference to AACR2 rules)
4.2.6. MARC coding
4.2.7. Punctuation
4.3. See references (400)
4.3.1. Formed as though chosen for the heading
4.3.2. Different forms of the name
4.3.2.1. Either side of the comma rule
4.3.3. Different entry elements
4.3.4. Pseudonyms dealt with by 400 reference
4.3.5. MARC coding
4.3.6. Punctuation
4.4. See also references (500)
4.4.1. Pseudonyms dealt with by 500 reference
4.4.2. References that conflict with established headings
4.4.3. Heads of government/state
4.4.4. Other situations
4.4.5. MARC coding
4.4.6. Punctuation
4.5. Complex see also references (663) [or discuss at 4.4.1]
4.6. Notes
4.6.1. 670
4.6.2. 667
4.6.3. 675
4.6.4. Format and punctuation
4.7. Literary author classification number (053)
5. Corporate Names (other than geographic or meeting names)
5.1. Scope (must be a named body, etc.--AACR2 21.1B1 & LCRI)
5.2. Relationship of the authority 110 to the bibliographic record (show how the heading looks in the bib record)
5.3. Subject or name? (LCRI 24.1; SCM H405)
5.3.1. Use of corporate names as subjects (SCM H 460)
5.4. Heading (110)
5.4.1. Choice of name
5.4.2. Form of name
5.4.2.1. Base form
5.4.2.2. Omissions
5.4.2.3. Additions
5.4.2.4. Other modifications
5.4.3. Subordinate bodies
5.4.3.1. Non-government
5.4.3.2. Government
5.4.4. Other types of corporate names (e.g., Religious bodies and officials)
5.4.5. MARC coding
5.4.6. Punctuation
5.5. See references (410)
5.5.1. Formed as though chosen for the heading
5.5.2. Different forms of the name
5.5.3. Initials (incl. how different systems handle spacing)
5.5.4. Numerals
5.5.5. Abbreviations
5.5.6. MARC coding
5.5.7. Punctuation
5.6. See also references (510)
5.6.1. Related corporate bodies
5.6.1.1. Chronological or sequential relationships
5.6.1.1.1. Subfield w coding
5.6.1.2. Other relationships
5.6.2. Heads of government/state
5.6.3. Other situations
5.6.4. MARC coding
5.6.5. Punctuation
5.7. Notes
5.7.1. 670
5.7.2. 667
5.7.3. 675
5.7.4. Format and punctuation
6. Meeting names
6.1. Scope
6.1.1. Includes conferences, meetings, events, expeditions, etc. (LCRI 21.1B1)
6.1.2. Must be named (how to tell, & where the name must appear)
6.1.3. Name or subject? (LCRI 24.7; SCM H1592)
6.2. Relationship of the authority 110 to the bibliographic record (show how the heading looks in the bib record)
6.3. Treatment of meeting names in the authority file (option not to authorize every form for recurring meetings)
6.4. Heading (111)
6.4.1. Choice of name
6.4.2. Form of name
6.4.2.1. Base form
6.4.2.2. Omissions
6.4.2.3. Additions
6.4.2.4. Other modifications
6.4.3. MARC coding
6.4.4. Punctuation
6.5. See references (411)
6.5.1. Formed as though chosen for the heading
6.5.2. Different forms of the name
6.5.3. MARC coding
6.5.4. Punctuation
6.6 See also references (511)
6.6.1. Related meetings
6.6.1.1. Chronological or sequential relationships
6.6.1.1.1. Subfield w coding
6.6.1.2. Other relationships
6.6.2. MARC coding
6.6.3. Punctuation
6.7. Notes
6.7.1. 670
6.7.2. 667
6.7.3. 675
6.7.4. Format and punctuation
7. Geographic names
7.1. Scope (jurisdiction names and names of areas both covered)
7.2. Relationship of the authority 151 to the bibliographic record (show how the heading looks in the bib record)
7.2.1. Bibliographic headings and added entries (110/710)
7.2.2. Subject entries (651/610)
7.3. Subject or name? (LCRI 24.1; SCM H405)
7.3.1. Variant for geographic names on ability to use forms as subject headings--latest form principle.
7.4. Heading (151)
7.4.1. Choice of name
7.4.2. Form of name (including sources: BGN, etc.)
7.4.2.1. Base form
7.4.2.2. Omissions
7.4.2.3. Additions
7.4.2.4. Other modifications
7.4.3. Subordinate bodies (110) [same as or similar to module 5.4.3.2]
7.4.4. MARC coding
7.4.5. Punctuation
7.5. See references (451 or 410 for subordinate forms)
7.5.1. Formed as though chosen for the heading
7.5.2. Different forms of the name
7.5.3. MARC coding
7.5.4. Punctuation
7.6. See also references (551 or 510 for subordinate forms)
7.6.1. Related names
7.6.1.1. Chronological or sequential relationships
7.6.1.1.1. Subfield w coding
7.6.1.2. Other relationships (splits, mergers, etc.)
7.6.2. MARC coding
7.6.3. Punctuation
7.7. Notes
7.7.1. 670
7.7.2. 667 (incl. note about subject usage)
7.7.3. 675
7.7.4. Format and punctuation
7.8. Geographic subdivision linking entry (781 field)
7.9. Use of place name as qualifier in other headings
8. Uniform titles
8.1. Scope
8.1.1. Name-title uniform titles
8.1.2. Uniform titles without name (note that this includes series, but not covered in this training)
8.1.3. Purpose of UT
8.1.3.1. AACR2 25.1A
8.1.3.2. Collocation
8.1.3.3. Differentiation
8.1.4. Works (AACR2 21.9) (different UTs assigned to different works--if two resources are for the same work, share UT)
8.2. Relationship of the authority 1XX to the bibliographic record (show how the heading looks in the bib record--1XX/240; 130; 6XX t; 630; 7XX t; 730; [mention 440, 8XX t, 830])
8.3. Heading (1XX t; 130)
8.3.1. General rules and procedures
8.3.1.1. Order of establishment (i.e., for name-title UTs, the established form of the name must be used or established before establishing the title portion)
8.3.1.2. LC guidelines for when UT must be established
8.3.2. Choice of title
8.3.3. Form of title
8.3.4. Collocation techniques
8.3.4.1. Translations
8.3.4.2. Collective titles
8.3.4.3. Music [this could develop into a separate module]
8.3.4.4. Laws [this could develop into a separate module]
8.3.5. Differentiation techniques
8.3.5.1. Monographs
8.3.5.2. Standardized qualifiers
8.3.5.3. Serials
8.3.6. Special cases (mention here; perhaps develop advanced module)
Sacred scriptures; Liturgical works; Manuscript headings; etc.
8.3.7. MARC coding
8.3.8. Punctuation
8.4. See references (4XX t; 430)
8.4.1. Formed as though chosen for the heading
8.4.2. Different forms of the title (only--different forms of the name not traced in UT authority record)
8.4.3. Part to whole relationships
8.4.4. Whole to part relationships
8.4.5. MARC coding
8.4.6. Punctuation
8.5. See also references (5XX t; 530)
8.5.1. Related titles (works)
8.5.2. MARC coding
8.5.3. Punctuation
8.6. Notes
8.6.1. 670
8.6.2. 667
8.6.3. 675
8.6.4. Format and punctuation
9. Appendices
9.1. RLIN authority file
9.1.1. Authority records
9.1.2. The authority file
9.2. OCLC authority file
9.2.1. Authority records
9.2.2. The authority file
9.3. LC authority file
9.2.1. Authority records
9.2.2. The authority file
9.4. Glossary
10. The NACO program
10.1. History of the PCC, relationship of NACO to the other programs
10.2. Description of the NACO program
10.3. How to become involved
10.3.1. Individual contributions
10.3.2. Funnel projects