PFAN - Name Authority Manual
 |
This article is actively undergoing a major edit for 24 h (Currently being edited by A. Dunnett, LAC). To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last revised at 08:09, 18 December 2020 (UTC) (3 years ago). Please remove this template if this page hasn't been edited in several hours. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
| About PFAN | News and Updates | Rules for Contributions | Name Authority Manual | Participant's Manual | PFAN Policy Statements | PFAN Training | Frequently Asked Questions (FAQ) | Other Documentation | LAC |
| Name Authority Manual | | Manual - MARC 21 Supplement | | 667 Field Examples | | 008 field : names |
Return to Table of Contents ⮝ | Supplement ⮞
Introduction
Return to Table of Contents ⮝ | Supplement ⮞
Name Authority Records
Return to Table of Contents ⮝ | Supplement ⮞
Series Authority Records
Return to Table of Contents ⮝ | Supplement ⮞
Fixed Fields
Return to Table of Contents ⮝ | Supplement ⮞
008/10 Descriptive cataloging code
Return to Table of Contents ⮝ | Supplement ⮞
008/11 Subject heading system/thesaurus
General
When applying RDA Chapter 9 for fictitious characters and RDA Chapiter 10 for family names assure that the NAR 008/11 is set to "n."
Corporate names for high government and religious officials
Assign value "n" (Not applicable) to name authority records for corporate names representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the authorized access point. Also assign value "b" in 008/15, and make a 667 note indicating the form of the access point used in subject cataloging.
Examples of corporate names not appropriate for use as subject headings:
États-Unis. Président (1953-1961 : Eisenhower) Iran. Shah (1941-1979 : Mohammed Reza Pahlavi) Illinois. Gouverneur (1973-1977 : Walker) Église catholique. Pape (1958-1963 : Jean XXIII) Church of England. Diocèse de Londres. Évêque (1675-1713 : Compton)
See also Manual 008/15 and the Manual 667 section "NARs and subject usage."
Follow these guidelines for newly-created NARs. Make these changes also when modifying existing name authority records for any reason.
Return to Table of Contents ⮝ | Supplement ⮞
008/15 Heading use-subject added entry
Family names When applying RDA Chapter 9 for fictitious characters and RDA Chapiter 10 for family names assure that the NAR 008/11 is set to "b."
Corporate names for high government and religious officials
Background: For Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes, descriptive catalogers may be required to establish an authorized access point for the corporate name for the office as well as a personal name for the office holder. It is subject cataloging policy to assign only the personal name, not the corporate name, as a subject access point. This policy was established for collocation purposes (cf. SHM H 430). For example:
États-Unis. Président (1789-1979 : Washington)
may be used in descriptive cataloging as an access point, but in subject cataloging only the personal name:
Washington, George, 1732-1799
would be used as a subject access point.
Assign value "b" (Not appropriate) to name authority records for corporate entities representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the entry. Also assign value "n" in 008/11, and make a 667 note indicating the form used in subject cataloging.
Example:
110 2# $a Église catholique. $b Pape (1958-1963 : Jean XXIII) 008/11 = n 008/15 = b
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Jean XXIII, pape, 1881-1963.
See also Manual 008/11 and the Manual 667 section "NARs and subject usage."
Follow these guidelines for newly-created authority records. Correct existing records when making any other change to the records.
Return to Table of Contents ⮝ | Supplement ⮞
008/32 Undifferentiated personal name
Return to Table of Contents ⮝ | Supplement ⮞
008/33 Level of establishment
Return to Table of Contents ⮝ | Supplement ⮞
008/39 Cataloging source
Return to Table of Contents ⮝ | Supplement ⮞
016 National Bibliographic Agency Control Number
Return to Table of Contents ⮝ | Supplement ⮞
022 International Standard Serial Number
Return to Table of Contents ⮝ | Supplement ⮞
024 Other standard identifier
Return to Table of Contents ⮝ | Supplement ⮞
034 Coded cartographic mathematical data
Return to Table of Contents ⮝ | Supplement ⮞
035 System Control Number
Return to Table of Contents ⮝ | Supplement ⮞
040 Cataloging source
Return to Table of Contents ⮝ | Supplement ⮞
042 Authentication Code
Return to Table of Contents ⮝ | Supplement ⮞
046 Special coded dates
Return to Table of Contents ⮝ | Supplement ⮞
050 Library of Congress Call Number
Return to Table of Contents ⮝ | Supplement ⮞
053 LC classification number
Return to Table of Contents ⮝ | Supplement ⮞
055 Library and Archives Canada Call Number
Return to Table of Contents ⮝ | Supplement ⮞
065 Other Classification Number
Return to Table of Contents ⮝ | Supplement ⮞
080 Universal Decimal Classification Number
Return to Table of Contents ⮝ | Supplement ⮞
082 Dewey Decimal Call Number
Return to Table of Contents ⮝ | Supplement ⮞
083 Dewey Decimal Classification Number
Return to Table of Contents ⮝ | Supplement ⮞
086 Government Document Call Number
Return to Table of Contents ⮝ | Supplement ⮞
087 Government Document Classification Number
Return to Table of Contents ⮝ | Supplement ⮞
1XX Headings - General Information
Return to Table of Contents ⮝ | Supplement ⮞
100 Heading - Personal Name
Return to Table of Contents ⮝ | Supplement ⮞
151 Heading - Geographic Name
Return to Table of Contents ⮝ | Supplement ⮞
336 Content Type
Return to Table of Contents ⮝ | Supplement ⮞
368 Other attributes of person or corporate body
Return to Table of Contents ⮝ | Supplement ⮞
370 Associated place
Return to Table of Contents ⮝ | Supplement ⮞
371 Address
Return to Table of Contents ⮝ | Supplement ⮞
372 Field of activity
Return to Table of Contents ⮝ | Supplement ⮞
373 Associated group
Return to Table of Contents ⮝ | Supplement ⮞
374 Occupation
Return to Table of Contents ⮝ | Supplement ⮞
375 Gender
Return to Table of Contents ⮝ | Supplement ⮞
376 Family information
Return to Table of Contents ⮝ | Supplement ⮞
377 Associated language
Return to Table of Contents ⮝ | Supplement ⮞
378 Fuller form of personal name
Return to Table of Contents ⮝ | Supplement ⮞
380 Form of work
Return to Table of Contents ⮝ | Supplement ⮞
381 Other distinguishing characteristics of work or expression
Return to Table of Contents ⮝ | Supplement ⮞
382 Medium of performance
Return to Table of Contents ⮝ | Supplement ⮞
383 Numeric designation of musical work
Return to Table of Contents ⮝ | Supplement ⮞
384 Key
Return to Table of Contents ⮝ | Supplement ⮞
385 Audience characteristics
Return to Table of Contents ⮝ | Supplement ⮞
386 Creator/contributor characteristics
Return to Table of Contents ⮝ | Supplement ⮞
4XX - See From Tracings - General Information
Return to Table of Contents ⮝ | Supplement ⮞
5XX - See Also From Tracings - General Information
Return to Table of Contents ⮝ | Supplement ⮞
500 See Also From Tracing - Personal Name
Return to Table of Contents ⮝ | Supplement ⮞
510 See Also From Tracing - Corporate Name
Return to Table of Contents ⮝ | Supplement ⮞
511 See Also From Tracing - Meeting Name
Return to Table of Contents ⮝ | Supplement ⮞
530 See Also From Tracing - Uniform Title
Return to Table of Contents ⮝ | Supplement ⮞
551 See Also From Tracing - Geographic Name
Return to Table of Contents ⮝ | Supplement ⮞
64X Series Numbering Peculiarities
Return to Table of Contents ⮝ | Supplement ⮞
642 Series Numbering Example
Return to Table of Contents ⮝ | Supplement ⮞
643 Series Place and Publisher/Issuing Body
Return to Table of Contents ⮝ | Supplement ⮞
644 Series Analysis Practice
Return to Table of Contents ⮝ | Supplement ⮞
645 Series Tracing Practice
Return to Table of Contents ⮝ | Supplement ⮞
646 Series Classification Practice
Return to Table of Contents ⮝ | Supplement ⮞
663 Complex See Also Reference - Name
Return to Table of Contents ⮝ | Supplement ⮞
665 History reference
Return to Table of Contents ⮝ | Supplement ⮞
667 Nonpublic general note
Return to Table of Contents ⮝ | Supplement ⮞
670 Sources found
Return to Table of Contents ⮝ | Supplement ⮞
General
The 672 field may be used to record a title that is related to the entity represented by the 100, 110, 111, or 151 in the name authority record.
For example, in an authority record for a corporate body, 672 fields may be used to record titles for which the corporate body is a creator, issuing body, or subject. The primary purpose of the 672 field is to document that there is a relationship between the 1XX entity and the title recorded in the 672 field.
Use of the 672 field does not negate the need to use the 670 field for the title for which the authority record is being created, nor to use the 670 fields to justify information recorded in the 1XX and 4XX such as preferred and variant forms of name.
New 672 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 672 fields when inputting new 672 fields.
Non-Latin script elements should be given in romanized form.
A title recorded in a 672 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 672 field.
Examples:
100 1# $a Boyer, Frédéric, $d 1961- 672 #3 $a La consolation 672 #0 $a Yeux noirs (672 fields with titles proper)
100 1# $a Boyer, Frédéric 672 #0 $a Cervantes (672 field with title proper)
111 2# $a Concile du Vatican $n (2e : $d 1962-1965 : $c Basilica di San Pietro in Vaticano) 672 #0 $a Constitutio de sacra liturgia (672 field with preferred title)
151 ## $a Espagne 672 #0 $a Llei d'enjudiciament civil i normes complementàries (672 field with variant title for the work associated with the Catalan expressionof the work and date of expression)
Subfield $b – Remainder of title
When recording a title proper, subfield $b may be used to record the other title information or parallel title proper to eliminate confusion for titles needing further identification.
Examples:
672 #3 $a La rivière $b initiations outaouaises (Subfield $b contains other title information)
672 #4 $a Las estrellas $b Stars (Subfield $b contains parallel title proper)
Subfield $f – Date
Subfield $f is used to record a date appropriate to the entity recorded in $a (e.g., use date of work for a preferred title and date of publication for a title proper). Do not use brackets in $f when recording a supplied date of publication or production. Do not give a date of distribution, date of manufacture, or copyright date in $f.
Examples:
672 for work: 672 #0 $a Amor en los tiempos del cólera $f 1985 (Date of work)
672 for expression: 672 #2 $a L'amour aux temps du choléra $f 1987 (Date of French expression of Amor en los tiempos del cólera)
672 for manifestation: 672 #0 $a Miłość w czasach zarazy $f 2005 (Date of publication of manifestation of Polish expression of Amor en los tiempos del cólera)
Subfield $w – Bibliographic record control number
Subfield $w is used to record bibliographic record control numbers (e.g., 001, 010, and 016 fields in bibliographic records). It is recommended that catalogers provide $w when readily available. Subfield $w should be repeated for each instance of a separate control number (e.g., an LCCN and an OCLC record number should be provided in separate subfields). For further instructions on inputting record control numbers, see the subfield $w section within the CONSER Editing Guide (CEG) – Section E.
MARC 21 Format for Serials as Applied within CONSER – Variable Data Fields – 76X-78X Linking Entries – Linking Entry Fields General Information.
Note: subfield $w should only be used with titles for the manifestation.
Example:
[in $w “#” = space input by cataloger]
672 #0 $a Bread and other bakery products industry $w (DLC)###88646267 $w (OCoLC)3774505 $w (CaOONL)84079116XE
[2020-12-14]
Return to Table of Contents ⮝ | Supplement ⮞
General
The 673 field may be used to record a title that is not related to the entity represented by the 100, 110, 111, or 151 in the name authority record. For example, in an authority record for a person, the 673 may be used to record the titles of works written by a different person with a similar name. The primary purpose of the 673 field is to document that there is no relationship between the 1XX entity and the title recorded in the 673 field.
Use of the 673 field does not negate the need to use the 675 field as described in the 675 section of DCM Z1.
New 673 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 673 fields when inputting new 673 fields.
Non-Latin script elements should be given in romanized form.
A title recorded in a 673 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 673 field. For specific subfields in the 673 field, apply the same instructions given in the 672 section of this Manual.
Examples:
[in $w “#” = space input by cataloger]
100 1# $a Boyer, Frédéric, $d 1961- 672 #0 $a Cervantes $f 1977 (Title proper associated with different Frédéric Boyer)
110 2# $a National Gallery of Art (É.-U.) 673 #0 $a Paintings and drawings on the backs of National Gallery pictures $w (DLC)### 47008205 $w (OCoLC)1654530 (Title proper associated with the National Gallery in London)
BUT NOT
110 2# $a National Gallery of Art (É.-U.) 673 #4 $a Impressed by light : $b British photographs from paper negatives, 1840-1860 (Although the National of Art is not the creator, it is the publisher so this title should be record in a 672)
[2020-12-14]
Return to Table of Contents ⮝ | Supplement ⮞
675 Sources not found
PFAN series practice
Transcription of the series statement is mandatory if applicable. Searching for series authority records, tracing the series, and the creation and maintenance of series authority records are optional.
In April 2012 this field was redefined as: “Citation for a consulted source in which no information is found related in any manner to the entity represented by the authority record or related entities.” PFAN catalogers are not required to change any existing 675 fields simply to meet this new definition.
When creating a new NAR always cite the resource being cataloged in the 675 field if the item being cataloged provides no information related in any manner to the entity represented in the authority record. Also cite in the 675 field other sources consulted that contain no information, when that very lack of information is considered worth recording for future users of the authority record.
Examples:
675 ## $a Oxford classical dictionary, 1996 675 ## $a GEOnet, consulté le 2 avril 2014
However, it is not always necessary to include in the 675 field every reference source consulted; use judgment in deciding what sources are important enough to retain in the permanent record.
[2020-12-14]
Return to Table of Contents ⮝ | Supplement ⮞
678 Biographical or historical data
General
When supplying biographical or historical data in a 678 note field, construct the note in concise but complete sentences, keeping in mind that the information will be used in public displays.
Examples:
678 0# $a Joseph Smith, Jr. (1805-1844) était un prophète mormon et le fondateur de l'Église de Jésus-Christ des saints des derniers jours.
678 1# $a L'Organisation du traité de l'Atlantique Nord (OTAN) est une alliance politique et militaire créée par la signature du Traité de l'Atlantique Nord, le 4 avril 1949. Elle regroupe des pays membres d'Amérique du Nord et d'Europe. Depuis 1999, plusieurs pays anciennement membres du Pacte de Varsovie ont rejoint l'OTAN, y compris la Hongrie, la Bulgarie et la Roumanie. D'autres pays non-membres participent aux programmes de l'OTAN tels que le Partenariat pour la paix.
In anticipation of LAC building the file in WMS and the batch addition of authority records from other institutions, the contents of all 665 fields in LAC and BAnQ records have been moved to 678 field. The original 665 field may have contained instructions on the access point(s) to be used as author and subject heading :
Example:
151 ## Cascapédia (Québec)
678 1# Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules. Comme auteur, on utilise : Cascapédia (Québec) ; Cascapédia-Saint-Jules (Québec) ; Grande-Cascapédia (Cascapédia-Saint-Jules, Québec) ; Saint-Jules (Cascapédia-Saint-Jules, Québec). Comme vedette-matière, on utilise Cascapédia-Saint-Jules (Québec).
Delete these instructions in 678 field if they have been retained. Consider adding a 667 field as a subject heading if applicable.
Example:
151 ## Cascapédia (Québec)
667 ## UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Cascapédia-Saint-Jules (Québec). 678 1# Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules.
Justification of field 678
Generally, a 678 field must be justified by a 670 field. If it is not justified and its contents are appropriate for a biographical or historical note, retain the field and add a 670 note citing the internal file of the institution that provided 678 field as follows :
670 ## Fichier interne de [ abréviation de la bibliothèque participante ], [date de consultation de Canadiana] …
Example :
670 ## Fichier interne de BAC, 29 octobre 2020 $b (établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail)
678 1# Établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail.
If the record has been modified after being migrated, the record history must be consulted to determine who originally added zone 678.
Example :
Existing Field 678 which will be deleted as the content is not appropriate for a biographical note. 678 1# Né le 6 juin 1973. 670 field added: 670 ## Fichier interne de l'ULaval, 29 octobre 2020 $b (né le 6 juin 1973)
Repeatability:
Do not repeat this field.
[2020-12-14]
Return to Table of Contents ⮝ | Supplement ⮞
7XX Heading linking entries
Note: This section does not apply to the 781 field used in 151 name authority records to provide geographic subdivision information. See Manual, 781 section, for instructions for that field.
General
The use of an established heading linking entry 7XX field in an NAR or SAR is limited to recording the authorized access point from a national bibliography or in a separate national authority file or a separate equivalence.
The form of heading in a 7XX field may match the 1XX form or a 4XX form in the same authority record. This is appropriate when the 7XX field form represents a form found in a different authority file than Canadiana.
Example:
100 1# $a Dion, Céline 700 10 $a Dion, Céline $0 (DLC)n 87834212
The source of the heading in the 7XX field may be specified using either second indicator value “7” with subfield $2 or a second indicator value that specifies the source. For access points coming from the LC/NACO file, prefer the second indicator with the value "0".
[2020-12-16]
Return to Table of Contents ⮝ | Supplement ⮞
781 Subdivision linking entry
PFAN optional practice:
For a geographic name heading that may also be used as a geographic subdivision, determine the form in which the heading is to be used as a geographic subdivision following the guidelines in instruction sheet H 830 of the Subject Headings Manual. Enter the text of the geographic subdivision form in a 781 field with second indicator 0. For a geographic heading that is used directly, such as a country, enter the data in a single $z subfield. For a geographic heading that is used indirectly through a larger geographic entity, such as a city, enter the data in two successive $z subfields. Use no other subfields. Make no changes to values in bytes of the 008.
Examples :
151 ## $a France 781 #6 $z France
151 ## $a Paris (France) 781 #6 $z France $z Paris
151 ## $a Lycie 781 #6 $z Turquie $z Lycie
151 ## $a Sydney (N.-G. du S.) 781 #6 $z Australie $z Sydney (N.-G. du S.)
151 ## $a León (Espagne : Province) 781 #6 $z Espagne $z León (Province)
Do not add a 781 field to a record for a geographic name heading that is not appropriate for use as a subject added entry (008/15 value Ab@), such as the earlier name of a jurisdiction that has undergone a linear name change, for example, Ceylon.
Do not add a 781 field to a NAR for a place name that is not appropriate for use as a geographic subdivision, such as a city section, for example, North End (Boston, Mass.)
Follow these guidelines for newly-created authority records. Add a 781 field to an existing record when making any other change to it. If revising an existing record that contains a 667 field subject cataloging usage note indicating the proper geographic subdivision form, delete the 667 field and replace it with a 781 field.
[2020-12-16]
Return to Table of Contents ⮝ | Supplement ⮞
Appendix 1: Undifferentiated entities
Return to Table of Contents ⮝ | Supplement ⮞
