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
PCC Post RDA Test Guidelines
PFAN follows PCC Post RDA Test Guidelines
Last update: 2020-10-02
PCC Guidelines for the Application of Relationship Designators in NACO Authority Records
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 | 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 | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
| Bulgarian | Cyrillic alphabet | 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 |
| Georgian | Georgian alphabet | ISO 9984:1996 Information and Documentation -- Transliteration of Georgian 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 |
| Kannada | Kannada alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
| 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 | 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 | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
| Sanskrit, Prakrit | Devanagari alphasyllabary | ISO 15919:2001 Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters |
| Serbian | Cyrillic alphabet | ISO 9:1995 Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages |
| 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 | 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 |
Late update: 2020-04-26
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,
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 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
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: bac.pfan-fnap.lac@canada.ca.
| English Term | French Term | Entity |
|---|---|---|
| Spacecraft | Véhicule spatial | Corporate Body |
| 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 |
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: 2020-06-19
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:
- Prefer a record that already has a 016 field over one that does not.
- Prefer a LAC record over a record from BAnQ or universities.
- 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.
- Prefer an RDA record over a non-RDA record.
- Prefer a more complete record over one that is less complete.
- Update the preferred record.
- PFAN: Make the following modifications in the record(s) to be deleted:
- 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])."
- 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. It is not permitted to used any other number when the record to be deleted does not already contain a Canadian number. (Note: If the record to be deleted contains a 016 field, do not add the code F to the end of a Canadian number transferred into the record to be retained if one does not exist (see point 3).)
- Make the following modifications to the record to be retained:
- 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.
- 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.
- 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.
- 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.
- All 3XX fields must be translated.
- 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 for PFAN: If there is more than one LAC record among the duplicates, report them to LAC by emailing the OCLC control numbers to bac.pfansuppression-deletionfnap.lac@canada.ca and with the subject line: LAC Duplicates. LAC will determine which record will be retained and delete the LAC record(s) not retained. If duplicates also include records from other participants, follow steps 2 and 3 below once LAC has identified which record to retain.
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.
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.
----
LAC : Does not apply.
Exemple:
Step 3 : Deletion
PFAN : There is no need to notify LAC by email regarding records to be deleted. All records identified by the Canadiana number 0000X0000F will be superseded by the record identified in note 667.
---
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 the 008/32 Nom de personne indifférencié in Name Authority Manual.
Last update: 2021-05-28
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 |
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.
|
| 3XX |
|
| 670 |
|
Example
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)
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)
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-05-04
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