PFAN - Other Documentation

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

LC Subject Cataloging Manual, H 405 - Establishing Certain Entities in the Name or Subject Authority File

Note 1 : LC SHM Instruction Sheet H 0405 - Establishing Certain Entities in the Name or Subject Authority File   (PDF, 76 KB)  . Please do not consult the document entitled "Autorités de noms propres: RVM (Sujets) ou catalogue d'autorités local?" published on the RVM website as it is not fully compatible with SHM H 405.

Note 2 : The following entities are considered by the PFAN to be part of Group 1 (entities established according to RDA in the Canadiana file):

• Cantons québécois (divisions cadastrales)

• Circonscriptions électorales

• Districts judiciaires

• Divisions d’enregistrement

• Divisions de recensement

• Régions et sous-régions administratives québécoises

Last update: 2021-02-16

Return to Table of Contents ⮝

PCC Post RDA Test Guidelines

PFAN follows PCC Post RDA Test Guidelines   

Last update: 2020-10-02

Return to Table of Contents ⮝

PCC Guidelines for the Application of Relationship Designators in NACO Authority Records

PFAN follows PCC Guidelines for the Application of Relationship Designators in NACO Authority Records with Adapted Examples for PFAN

Last Update with PFAN Examples: 2020-05-04
Return to Table of Contents ⮝

Authority File Comparison Rules

PFAN follows Authority File Comparison Rules (NACO Normalization)   (PDF, 72 KB)

Last update: 2020-04-09
Return to Table of Contents ⮝

Romanization

Language	Writing System	Romanization Table
Arabic	Arabic alphabet	ISO 233-2:1993 Information and Documentation -- Arabic characters into Latin characters -- Part 2: Arabic language -- Simplified transliteration
Armenian	Armenian alphabet	BnF Translittération de l'arménien based on ISO 9985:1996 Information and Documentation -- Transliteration of Armenian characters into Latin characters
Assamese	Bengali alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Bengali	Bengali alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Belarusian	Cyrillic alphabet	BnF Translittération du russe, du biélorusse et de l'ukrainien contemporains based on ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages Exception: For Cyrillic letter Ё/ё, do not apply the instructions under "Remarque" in the BnF table. The letter Ё/ё is always romanized with the Latin letter Ë/ë (E umlaut/e umlaut), according to the following instructions: N° d'ordre ISO Majuscule Code Unicode de la majuscule Translittération de la majuscule Code Unicode de la translittération de la majuscule Minuscule Code Unicode de la minuscule Translittération de la minuscule Code Unicode de la translittération de la minuscule 9 Ё 0401 Ë 00CB ё 0451 ë 00EB
Bulgarian	Cyrillic alphabet	BnF Translittération du bulgare et du macédonien contemporains based on ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Chinese	Chinese characters	ISO 7098:2015 Information and Documentation -- Romanization of Chinese and ALA-LAC Romanization Table – Chinese follow the principle of Pinyin. In the absence of ISO ISO 7098:2015, it is appropriate to follow the ALA-LC Romanization table – Chinese, with the following exceptions: Names of continents and regions which have already become Chinese words are written as one word. Feizhou (非洲, Africa) NOT Fei Zhou Nanmei (南美, South America) NOT Nan Mei Dongnanya (东南亚, Southeast Asia) NOT Dong nan Ya Ethnic names and tribe names are written as one word with the initial letter capitalized. Hanzu (汉族, Han, Chinese ethnic group) NOT Han zu Maolizu (毛利族, Māori) NOT Maoli zu Weiwuerzu (维吾尔族, Uighur, Chinese ethnic group) NOT Weiwuer zu Language names are written as one word with the initial letter capitalized. Yingyu (英语，English) NOT Ying yu Kejiahua (客家话, Hakka) NOT Kejia hua Religions/religious followers are written as one word with the initial letter capitalized. Jidujiao (基督教, Christianity) NOT Jidu jiao Jidutu (基督徒, Christian) NOT Jidu tu ISO 7098:2015 specifies that " Tone marks may be written as a learning tool; however, they can be omitted for convenience." PFAN omits the tone marks when applying this instruction.
Georgian	Georgian alphabet	BnF Translittération du géorgien based on ISO 9984:1996 Information and Documentation -- Transliteration of Georgian characters into Latin characters
Greek	Greek alphabet	ISO 843:1997 Information and documentation -- Conversion of Greek characters into Latin characters
Gujarati	Gujarati alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Hebrew	Hebrew characters	ISO 259-2:1994 Documentation -- Transliteration of Hebrew characters into Latin characters -- Part 2: Simplified transliteration
Hindi	Devanagari alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Inuktitut	Canadian Aboriginal syllabics	ALA-LC 2011 Inuktitut romanization table
Japanese	Japanese script (hiragana, katakana et kanji)	ALA-LC 2012 Japanese Romanization Table
Kannada	Kannada alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Korean	Korean script	BnF Translittération du coréen (han kūl et han ča)
Slavic and non-Slavic Languages	Cyrillic alphabet	ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Macedonian	Cyrillic alphabet	BnF Translittération du bulgare et du macédonien contemporains based on ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Malayalam	Malayalam alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Marathi	Devanagari alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Mongolian	Cyrillic alphabet	ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Nepali	Devanagari alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Oriya (odia)	Odia alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Pali	Various including Bengali, Burmese, Devanagari, Sinhalese and Thai alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Persian	Persian alphabet	ISO 233-3:1999 Information and Documentation -- Transliteration of Arabic characters into Latin characters -- Part 3: Persian language -- Simplified transliteration
Russian	Cyrillic alphabet	BnF Translittération du russe, du biélorusse et de l'ukrainien contemporains based on ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages Exception: For Cyrillic letter Ё/ё, do not apply the instructions under "Remarque" in the BnF table. The letter Ё/ё is always romanized with the Latin letter Ë/ë (E umlaut/e umlaut), according to the following instructions: N° d'ordre ISO Majuscule Code Unicode de la majuscule Translittération de la majuscule Code Unicode de la translittération de la majuscule Minuscule Code Unicode de la minuscule Translittération de la minuscule Code Unicode de la translittération de la minuscule 9 Ё 0401 Ë 00CB ё 0451 ë 00EB If the Cyrillic letter Е/е is used instead of the letter Ё/ё in the source, it is the letter Е/е that should be romanized according to the instructions in the table.
Sanskrit, Prakrit	Devanagari alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Serbian	Cyrillic alphabet	ALA-LC Romanization Tables -- Serbian [Replaces ISO 9:1995 table as of 2021-11-12]
Tajiki	Cyrillic alphabet	ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Tamil	Tamil alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Telugu	Telugu alphasyllabary	ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
Thai	Thai alphasyllabary	ISO 11940:1998 Information and Documentation -- Transliteration of Thai (à confirmer)
Ukrainian	Cyrillic alphabet	BnF Translittération du russe, du biélorusse et de l'ukrainien contemporains based on ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
Yiddish	Hebrew alphabet	ISO 259-2:1994 Documentation -- Transliteration of Hebrew characters into Latin characters -- Part 2: Simplified transliteration

Last update: 2022-10-13

Return to Table of Contents ⮝

Non-exhaustive List of Verifications to Make to an Existing Record

General Information

• Verify that the characters used are only those in the MARC 8 character set.
• Generally, the information must be provided in French. When information quoted in field 670 comes from a source in a language other than French, the Guide asks cataloguers to “generally translate the information into French, in an informal manner, summarizing as appropriate”. If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English, fields 670 and 675 can remain in English but it must be ensured that the information recorded in other fields is in French. It is understood that all information in English will not necessarily have an equivalent in French. This would be the case, for example, for terms belonging to a controlled vocabulary for which there is no French version. In this case, the information must be deleted.

Field	Verification
008	Verify that the coding is correct. For names (except name-title series), verify that the coding complies with the instructions relating to field 008: names (except name-titles series). Position 10 (Descriptive cataloging rules) : must be changed to "z". Note: When 008/10 is changed to "z" (Other), a field 040 $e rda is automatically added. The reverse is not true. Position 39 (Source of cataloging): the value initially recorded in this field is retained; do not modify this value when updating a record, except if the initial value was incorrect. The initial value is incorrect if it is not " " [blank] for a record created originally by LAC, BAnQ or LC (symbol CaOONL, CaQMBN or DLC in field 040 $a) or "c" (Cooperative cataloguing program) for a record created originally by an university or NACO participant (symbol for the university or NACO participant appearing in field 040 $a).
010	Delete this field if it is present.
016	If there is no Canadiana number, verify in the LC field if the same entity is represented by an authority and if it contains a Canadiana number (it is possible to refine the search by using cs:caoonl). If yes, add this number to the record by changing the language code E at the end of the field to the code F (or by adding the code if it is absent). If there is a Canadiana number but it does not end with the language code F, add this code to the end of the number.
024	Verify the coding (in particular subfields $0 and $1 for URIs).
040	Ensure that subfield $e rda is present, after having verified that field 1XX, fields 4XX and fields 5XX comply with RDA.
043	This field cannot be used in records for geographic names (records with field 151). Delete this field in other cases such as when the record contains an occurrence of field 100, 110, 111 or 130.
053	Ensure that classification numbers for class PS8000 are moved to field 065 and that field 053 is deleted. Example: 053 #4 PS8539.R47 $5 CaOONL becomes 065 ## PS8539.R47 $2fcps $5CaOONL Be sure to add a period between the classification number and the Cutter if one exists. Example: 053 #4 PS8595 I5834 $5 CaOONL becomes 065 ## PS8595.I5834 $2 fcps $5 CaOONL Caution: Field 053 remains valid for LC classification numbers (PA-PT), including the classification numbers PR9180-9199.4 for French-Canadian literature, the classification numbers PR9180-9199.4 for English-Canadian literature and classification numbers PS1-3626 for American literature.
083	BAnQ records that were loaded into Canadiana and that contain this field do not contain subfield $2, which prevents the record from being saved. To be able to save the record, change the value in the first indicator to 7 and add subfield $2 23 before subfield $5 CaQMBN. Exemple : 083 04 C841.6 C439 $5 CaQMBN becomes 083 74 C841.6 C439 $2 23 $5 CaQMBN
1XX	If the record is not RDA compliant, correct the access point if necessary to make it RDA compliant.
4XX	If the record is not RDA compliant, correct the access points if necessary to make them RDA compliant. Add missing dates in field 400 when field 100 contains dates (LAC has had a policy in the past not to add dates systematically.) Delete non-compliant $w subfields. In particular, delete all occurrences of subfield $w containing only a single code (for ex. $w d) delete all occurrences of subfield $w containing only two codes if the codes are not "nh" (for ex. $w na). For more information about subfield $w, see the Manual - MARC 21 Supplement, section 4XX.
5XX	If the record is not RDA compliant, correct the access points if necessary to make them RDA compliant, which involves upgrading the authorities attached to the access points. In the case of a name change for a corporate body, the 5XX fields should link the corporate body in field 1XX only to the immediately preceeding and immediately succeeding entities. Delete all 5XX fields for an entity that preceeds the immediately preceeding entity or succeeds the immediately succeeding entity. For example, in the case of corporate body A which becomes B, which becomes in turn C, the authority for entity A should not contain a 5XX field for entity C and the authority for entity C should not contain a 5XX field for entity A.
663	Ensure that the wording of the note complies with the most recent practice (see: FAQ – LC-PCC practice for creating NARs for persons who use pseudonyms (PFAN documentation) (PDF, 829 KB)).
665	This field is not permitted in Canadiana. If possible, transfer the biographical or historical information to a 678 field and delete the 665 field. Example: 151 Viernyï (Kazakhstan) 665 Fondée en 1854, cette ville a porté le nom de Viernyï jusqu'en 1921. Elle s'appelle maintenant Alma-Ata. Comme auteur, on utilise : Alma-Ata (Kazakhstan) ; Viernyï (Kazakhstan). Comme vedette-matière, on utilise : Alma-Ata (Kazakhstan). In this example, only the first two phrases can be transferred to a 678 field. The two other phrases are not retained. As the access point is not valid as a subject heading, it is necessary to consider adding the following note in field 667: 667 ## $a 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 Alma-Ata (Kazakhstan).
667	Ensure that the contents of this field are general enough to be pertinent to cataloguers in other institutions. If not, delete the field. Examples of 667 fields to delete: 667 Corpus UL 667 UQAC-AU. $5 CaQCU 667 Pour le 055, utiliser PS8623. BAnQ: Before sending records to OCLC, ensure that all of the 667 fields have been copied into field 899 in Portfolio to preserve their contents in the event that local content is deleted by another PFAN participant, except fields 667 beginning with one of the following expressions: "En subdivision :", "Ne pas utiliser en subdivision" and "UTILISATION COMME VEDETTE-MATIÈRE :". If the content of a 667 field copied into field 899 is no longer pertinent for BAnQ, consider also deleting the corresponding 899 field in Portfolio. Delete the 667 field containing "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" after finalizing the record.
670	If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English, it is not necessary to translate the field into French, as the case may be. It is generally not necessary to modify an existing 670 field except in cases provided in the FAQ for field 670 (Source data found) in the name authority record for NACO.
675	If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English, it is not necessary to translate the field into French, as the case may be. Occurrences of subfield $a following the first occurrence must be preceeded by a semi-colon, space. Add this punctuation if it is missing. Delete any $a subfield that cites the Canadian authority file (ex. Autorités Canadiana) without accompanying this citation with a consultation date.
678	Ensure that the contents of the field truly consist of biographical or historical, that it is appropriate for public viewing, and that it is supported by sources given in a 670 field. For further information, see the Name Authority Manual, section 678 .
7XX	Delete this field if subfield $2 lacnaf is present.

Last update: 2021-03-30

Return to Table of Contents ⮝

Non-exhaustive List of Qualifiers

The non-exhaustive list of qualifiers comprises a series of terms to be used when an RDA instruction requires an added element to distinguish or specify an access point that represents a person, a corporate body or a work (for example, RDA 9.19.1.6).

The following list is a selection of terms whose use is encouraged by the Standards Committee to ensure the consistency of name authorities when a choice between several possible terms must be made. When you have the choice between two terms, give preference to the terms in this list. For example: "Organisme", rather than "Organisation".

This is not a closed list and suggestions are welcome: pfan-fnap@bac-lac.gc.ca.

English Term	French Term	Entity
Spacecraft	Véhicule spatial	Corporate Body
Lyrics	Paroles	Work
Libretto	Livret	Work
Program	Programme	Corporate Body
Firm	Firme	Corporate Body
Organization	Organisme	Corporate Body
Musical group	Groupe musical	Corporate Body
	Congrès	Corporate Body
	Conférence	Corporate Body
Radio station	Station de radio	Corporate Body
Television station	Station de télévision	Corporate Body
Contest	Concours	Corporate Body
Play	Pièce de théâtre	Work
Motion picture	Film	Work
Series	Collection	Work
Association	Association	Corporate Body
Lecturer *	Professeur d’université Maître de conférences Chargé de cours For more information, see Lecturer	Person
Computer program See Computer file
Computer file	Fichier informatique	Work

* Lecturer

According to the Cambridge dictionary, the term lecturer designates a person who teaches at a college or university, in Anglo-Saxon countries.

Ex. : Lecturer in psychology

This title corresponds to different cases in reality depending on the country where it is used. It would be desirable to use the equivalent French term in relation to what the title represents in the educational system where the author holds the title of lecturer.

Suggestions of French equivalents

• For an author in France who is designated as being "un maître de conférences", use (Maître de conférences)
  • According to the Larousse dictionary, the title used by professors of the first rank of the second class of the teaching faculty of universities in France. Equivalent of the Anglo-Saxon term lecturer according to Wikipedia.
• For an author in Europe who is designated as being a lecturer, use (Maître de conférences) or (Professeur d'université)
• For an author who is designated as a lecturer in Australia, use (Professeur d'université)
• For an author who is designated as a lecturer in the United Kingdom, use (Maître de conférences) or (Professeur d'université)
• For an author who is designated as a lecturer in the United States, use (Professeur d'université) or (Chargé de cours)
• For an author who is designated as a lecturer in Canada, use (Chargé de cours)

When in doubt about which French equivalent to use, consult the List of academic ranks de Wikipédia in particular for the countries not mentioned above.

Lastly, note that a senior lecturer is more of a "professeur associé" than a "chargé de cours".

Last Update: 2022-03-22

Return to Table of Contents ⮝

Procedures for Duplicates

Step 1: Selection
Situation 1: Duplicates between migrated records, and LAC records which existed before the migration (June, 2 2020). Choose the authority record to retain when there are duplicates by following the following order of priority:

1. Prefer a record that already has a 016 field over one that does not.
2. Prefer a LAC record over a record from BAnQ or universities.
Note for PFAN: If there is more than one LAC record amongst the duplicate records, inform LAC; send LAC the OCLC record numbers, by email, to the following address : pfansuppression-deletionfnap@bac-lac.gc.ca mentioning in the subject line: Doublons de BAC. LAC will determine which record should be kept, and will replace the record(s) to be deleted. If the duplicate records also include records from other participants, simply follow Steps 2 and 3 below, once LAC has identified which record will be retained.
Note for LAC: If there are more than one LAC records among the duplicates, the cataloguer has to determine which record will be kept, and he/she must delete the other records. The oldest record will usually be preferred. Do not forget to do any bibliographic file maintenance (including the LBD), as required.
3. Prefer a record from BAnQ over a record from universities. Note for PFAN and LAC : University records have a code other than CaOONL or CaQMBN in field 040 $a.
4. Prefer an RDA record over a non-RDA record.
5. Prefer a more complete record over one that is less complete.
Example 1:
Record 1 comes from LAC and has a 016 field but is not RDA compliant; record 2 comes from BAnQ and is RDA compliant. Record 1 from LAC is retained because criteria 1 and 2 have priority over criterion 4.
Example 2:
Record 1 comes from BAnQ and is not RDA compliant; record 2 comes from a university but is RDA compliant and more complete. Record 1 from BAnQ is retained because criterion 3 has priority over criteria 4 and 5.
Example 3:
Record 1 comes from a university and is not RDA compliant; record 2 comes from another university but is RDA compliant although less complete. Record 2 is retained because criterion 4 has priority over criterion 5.

Situation 2: Duplicates between an LAC records which existed before the migration (June 2, 2020), or a migrated record, and any new record created in Canadiana on or after June 2nd, 2020.
Keep the pre-June 2nd, 2020 LAC record, or the migrated record, following the order of priority outlined above (under Situation 1). Follow steps 2 and 3.

Situation 3: Duplicates between any new records created in Canadiana on or after June 2nd, 2020.
Keep the first record (the older one), according to the date entered on file, in field 008 (character positions 00-05). Follow steps 2 and 3.

Step 2 : Modifications
Record to be retained
PFAN et BAC

1. Update the preferred record.
2. Make the following modifications to the record to be retained:
1. If the record to be deleted contains a 016 field, copy the Canadiana number from the record to be deleted into sub-field $z of field 016 in the record to be retained. Do not add the code F to the end of a Canadiana number transferred into the record to be retained if one does not exist.

Exemple :

016 ## 1026F7926F $z 1030B8987




2. If the record to be deleted contains a 035 field with the symbol CaQQLA, copy this field to the record to be retained. Do not copy a 035 field with any other symbol.

Example :

035 ## (CaQQLA)XX4513984




3. Copy into the record to be retained all information or fields present in the record to be deleted and judged to be useful to retain.

Record(s) to be deleted
PFAN

1. Make the following modifications to the record(s) to be deleted:
1. Add a 667 field containing the note "Notice doublon, signalée pour suppression car remplacée par [numéro Canadiana de la notice à conserver] ([date]). »
2. If there is no 016 field, add one using the number 0000X0000F. This is a generic number intended to be used in all duplicate records to be deleted that do not contain a Canadiana and only in these records. Adding this number is necessary so that the record can be saved.
3. If there is already a field 016 with a Canadiana number, do not change field 016.

_____
BAC : Does not apply. Proceed to step 3.

Step 3 : Deletion
PFAN :

1. Do not notify LAC regarding records to be deleted identified by the generic number 0000X0000F. They will be replaced by the record identified in a note 667.
3. Notify LAC regarding records to be deleted that have a unique Canadiana number XXXXAXXXX(F) by communicating the OCLC control number by email to pfansuppression-deletionfnap@bac-lac.gc.ca with subject line: Doublons avec 016 valide.

_____
LAC: The LAC cataloguer will delete the records we are not keeping. Please make sure to use the function “Supersede / Mark for deletion”, under the “Record” tab, and not the function “Delete”.
_____
Note for PFAN and LAC:For undifferentiated records, see the instructions in section 008/32 Undifferentiated personal name in the Name Authority Manual.

Last update: 2022-11-10

Return to Table of Contents ⮝

Procedures for records derived from LC/NAF

This procedure explains the changes to be made to an LC/NAF authority record when deriving it from the Canadiana file to create a new record.

1XX	The authorized access point does not need to be identical to the LC/NAF access point. The same entity may have two different or two identical access points in the two files. Note : In LC/NAF, some records are coded “RDA compatible”. These are records which are coded AACR2, but where the authorized access point would be constructed in the same way according to RDA and according to any relevant LC-PCC PS. Just as they would do for any new access point being established in Canadiana, which has to conform to RDA, PFAN cataloguers must make sure to evaluate the access point and to code the record RDA. “Evaluate” means that the cataloguer will check the usage(s) as recorded in the 670 field(s) in the authority record, and will evaluate that the authorized access point is exact based on the usage recorded in the bibliographic records. If the year of birth or year of death are known, the cataloguer will always add them to the access points, when creating a new authority record.
3XX	All 3XX fields must be translated.
670	The first 670 should be citing the resource in hand being catalogued by the PFAN cataloguer (even if this resource is quoted in the derived record). Do not retain a 670 field if the resource quoted is not consulted by the PFAN cataloguer. Combine into a single 670 field all the 670 fields from the record being derived which are not retained. This 670 field may also include information from fields 046 and 3XX. Combine the most important information into a single 670 field, in French.. Example : 670 ## LC/NAF, [date of the search] $b([data]) Note : It is possible to record, in field 672, any title associated with the AAP and cited in any 670 field, if deemed important to identify the entity represented by the AAP.

Example

"Dérived" from LC/NAF:

100 1# Bruland, Kristine

670 ## Her British technology and European industrialization, 1989: $b CIP t.p. (Kristine Bruland) bk. t.p. (Kristine Bruland) jkt. (research fellow at the Centre for Technology and Culture, Univ. of Oslo, and at the Economic History Dept. of the Norwegian School of Management, Oslo)

670 ## Technological revolutions in Europe industrialization, 1998: $b CIP t.p. (Kristine Bruland, prof. Economic Hist., Univ. Oslo, Norway) data sheet (b. 02/10/50)

New Canadiana record (when the resource on hand is not cited in the derived record):

100 1# Bruland, Kristine, $d 1950-

670 ## [Title of the resource on hand], [date] : $b source d'information privilégiée ([usage]) autre emplacement([other information])

670 ## LC/NAF, 20 juillet 2020 $b (point d'accès : Bruland, Kristine; née le 10 février 1950; "research fellow" [en 1989], Centre for Technology and Culture, Univ. of Oslo, et Economic History Dept., Norwegian School of Management, Oslo; professeure d'économie historique [en 1998], Univ. Oslo)

New Canadiana record (when the resource on hand is cited in the derived record):

100 1# Bruland, Kristine, $d 1950-

670 ## British technology and European industrialization, 1989 : $b page de titre (Kristine Bruland) jaquette ("research fellow", Centre for Technology and Culture, Univ. of Oslo, et Economic History Dept., Norwegian School of Management, Oslo)

670 ## LC/NAF, 20 juillet 2020 $b (point d'accès : Bruland, Kristine; née le 10 février 1950; professeure d'économie historique [en 1998], Univ. Oslo)

Last update: 2021-06-29

Return to Table of Contents ⮝

Procedure for partial modification of records describing works and expressions [NEW]

When an authorized access point for a personal name is modified, it may happen that it then no longer matches the access point for that person as used in the access points representing works and expressions, already present in Canadiana. For instance, it may happen that an access point for a person is modified to add the death date, but that the access points for that person’s works and expressions include only the person’s birth date. It may also happen that a cataloguer is revising the access point for a personal name, in an authority record that was batch-loaded, but some access points for works and expressions, by this person, include a different form of name.

A PFAN cataloguer may then do some partial modifications to the records for works and expressions associated with that person, according to the following instructions:

Conditions:

1. Applying this procedure is not mandatory, it is entirely up to the participant.
2. This procedure only applies when, in an authorized access point for a work or expression, the name part is a personal name, and the form of this name does not match the AAP in the person’s authority record.
3. The access points representing the person’s works and expressions may be modified only in part, or completely – that is, the cataloguer may evaluate only the name part, or both the name part and the title part. The procedure below applies only for those cases when the access point is modified only partially. If the entire access point is verified [validated], then the entire record has to be evaluated – that is, it has to be revised in order to be RDA compliant, and it has to follow PFAN standards. In that case, please consult the following document : List of Verifications to Make to an Existing Record.
4. 4. In case of duplicate records, this procedure only applies to the records that are retained. Any duplicate records should be reported for deletion, according to the Procedures for Duplicates.

Procedure:

1. Modify the person’s access point in the authority record for that person, making sure that the record is RDA compliant and follows all PFAN standards..
2. Partially modify the records representing the person’s works and expressions, that is, modify the « Name » part of the access point, without editing the rest of the access point or any other existing field. It is not mandatory to modify all the records representing the person’s works and expressions:
   1. Update the “personal name” part of the Authorized Access Point, in the records representing the person’s works and expressions, so that the name is identical to the name in the authority record representing the person. Make sure that the update is done both in the 100 field and in any existing 400 fields.
   2. b. If the record includes the 667 note "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN", keep the note, and proceed as follow:
      1. Add the generic Canadiana number 1111X1111F in field 016. Please note that this generic number will have to be replaced by a unique number when the record is assessed at a later point, at which time the 667 note mentioned above will be deleted.
      2. Add the following 667 note:
         667 $a CETTE NOTICE A FAIT L’OBJET D'UNE MODIFICATION PARTIELLE. LE NUMÉRO CANADIANA GÉNÉRIQUE 1111X1111F DANS LA 016 DOIT ÊTRE REMPLACÉ PAR UN NUMÉRO UNIQUE LORSQUE LA NOTICE EST ÉVALUÉE.
3. If the record does not include the note « CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN », then update the name part of the access point, without making the changes described under b).
4. Do not add a cross-reference to the former access point (either with a subfield $w nne or $w nnea). Please note that such a cross-reference could be required, for instance in cases where the former access point was RCAA2, when the authority record is reassessed, at a later stage, and the 667 note " CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN " is deleted. At that point, the cross-reference to be added is the former access point which displayed in field 1XX before the record was reassessed.

Examples
Note: Only relevant fields have been included in these examples.

Example 1: Name authority record, and batch-loaded work authority record

Name authority record modified to add a date of death in the authorized access point:

016 ## 0100D5363F

100 1# Blais, Marie-Claire, $d 1939-2021

Work authority record, batch-loaded and not revised, before the partial modification:

[No 016 field]

100 1# Blais, Marie-Claire, $d 1939- $t Dans la foudre et la lumière

667 ## CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN

Work authority record, batch-loaded and not evaluated, after the partial modification:

016 ## 1111X1111F

100 1# Blais, Marie-Claire, $d 1939-2021. $t Dans la foudre et la lumière

667 ## CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN

667 ## CETTE NOTICE A FAIT L'OBJET D'UNE MODIFICATION PARTIELLE. LE NUMÉRO CANADIANA GÉNÉRIQUE 1111X1111F DANS LA 016 DOIT ÊTRE REMPLACÉ PAR UN NUMÉRO UNIQUE LORSQUE LA NOTICE EST ÉVALUÉE.

Example 2: Batch-loaded name authority record, and batch-loaded expression authority record

Batch-loaded name authority record, before revision:

[No 016 field]

100 0# Arrien, $d environ 95-environ 175

667 ## CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN

Name authority record, after revision:

016 ## 1038H8594F

100 0# Arrien, $d environ 95-environ 175

Batch-loaded work authority record, not revised, before the partial modification:

[No 016 field]

100 0# Arrien. $t Traité de tactique. $l Français

667 ## CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN

Batch-loaded work authority record, not revised, after the partial modification:

016 ## 1111X1111F

100 0# Arrien, $d environ 95-environ 175. $t Traité de tactique. $l Français

667 ## CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN

667 ## CETTE NOTICE A FAIT L'OBJET D'UNE MODIFICATION PARTIELLE. LE NUMÉRO CANADIANA GÉNÉRIQUE 1111X1111F DANS LA 016 DOIT ÊTRE REMPLACÉ PAR UN NUMÉRO UNIQUE LORSQUE LA NOTICE EST ÉVALUÉE.

Last update: 2022-01-26

Return to Table of Contents ⮝

Useful External Resources

• The British Library Guide to RDA Name Authority Records : A Guide to Best Practice for RDA Name Authority records in NACO (including 2013 and 2014 changes)
• A Handbook of Examples For Use in Authority Records Created By the NACO-Music Project
• What Unicode character is this?

Last update: 2021-03-12

Return to Table of Contents ⮝