1,990
edits
Changes
Jump to navigation
Jump to search
mLine 26:
Line 26: − <!-- Version à confirmer avec Nathalie Mainville. En attendant, je cache ce lien. -AD 2020-12-19.+ − − + − --> Line 42:
Line 40: + + + + + + Line 55:
Line 59: − + Line 67:
Line 71: − + + + + + + + + + + + + + + + + + + + + + + + + − + − + + + + + + + + + + + + + + + + + + + + + + − + + + + + Line 96:
Line 148: + + + + + + + + Line 107:
Line 167: − + Line 139:
Line 199: − + + + + + + + + + + + + + + + + + + + + + + + + + Line 147:
Line 231: − + Line 168:
Line 252: − + Line 175:
Line 259: − + Line 304:
Line 388: − + Line 315:
Line 399: + + + + + + + + Line 408:
Line 500: − + − + − # 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.+ − # Prefer an RDA record over a non-RDA record.+ − # Prefer a more complete record over one that is less complete.+ + + + + + + + + + + + + − 2) Make the following modifications in the record or records 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).) + + − 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − Exemple:+ − + + + + + + + + + + + + + + + + + + + + + + + + + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − 4) Report the records to be deleted to LAC by sending the corresponding OCLC control numbers by email : [mailto:bac.pfansuppression-deletionfnap.lac@canada.ca?subject=Doublons%20/%20Duplicates&body=Hello,%0D%0DRecord%20to%20retain%3A%20%20%5BOCLC%20number%5D%0D%0DRecord(s)%20to%20delete%3A%20%20%5BOCLC%20number(s)%5D%0D%0D bac.pfansuppression-deletionfnap.lac@canada.ca]. Generic message suggested: − <div style="margin-left:25px;"> − <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">Subject line: Doublons / Duplicates<br><br> − Message :<br><br>+ − Hello, <br><br>+ − Record to retain: [OCLC number]<br><br>+ − Record(s) to delete: [OCLC number(s)]<br><br>+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + + + + + + + + + + + + + + + + + + + + + + − +
PFAN - Other Documentation (view source)
Revision as of 11:20, 18 January 2023
, 11:20, 18 January 2023→Useful External Resources
=PCC Guidelines for the Application of Relationship Designators in NACO Authority Records=
=PCC Guidelines for the Application of Relationship Designators in NACO Authority Records=
PFAN follows [[Media:Lignes directrices du PCC pour l'application des indicateurs de relation dans les notices d'autorité de NACO PFAN ENG.pdf| PCC Guidelines for the Application of Relationship Designators in NACO Authority Records with Adapted Examples for PFAN]]
[[Media: Lignes directrices du PCC pour l'application des indicateurs de relation dans les notices d'autorité de NACO_PFAN_ENG.pdf | PCC Guidelines for the Application of Relationship Designators in NACO Authority Records with Adapted Examples for PFAN]]
''Last Update with PFAN Examples: [[:File:Lignes directrices du PCC pour l'application des indicateurs de relation dans les notices d'autorité de NACO_PFAN_ENG.pdf | 2020-05-04]]''
''Last Update with PFAN Examples: 2020-05-04''
<br>
<br>
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
=Romanization=
=Romanization=
<span style="color:red>Generally speaking, the PFAN prefers to use current ISO romanization standards. These internationally-accepted standards normally make it possible for the user to reverse the romanization; automatic data processing is also possible.</span>
<span style="color:red>However, for some languages or scripts, it sometimes happens that no ISO standard is available, as in the case of Inuktitut, or that the relevant ISO standard ignores some essential linguistic elements or some important aspects of romanization, such as reversibility of the operation. For instance, the ISO transliteration table for Armenian does not include letters used with a numerical value; for this reason, the BnF table (used as a basis for the ISO standard) has been preferred. The following table shows which romanization standard has been chosen for each individual language.</span>
<span style="color:red>These were all individually selected; in each case, the goal is always to allow for a standard transliteration which is both reversible and as complete as possible. </span>
{| class="wikitable sortable mw-collapsible" style="background:none; width:100%"
{| class="wikitable sortable mw-collapsible" style="background:none; width:100%"
|Armenian
|Armenian
|Armenian alphabet
|Armenian alphabet
|[https://www.iso.org/en/standard/17893.html ISO 9985:1996] Information and Documentation -- Transliteration of Armenian characters into Latin characters
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-de-larmenien Translittération de l'arménien] based on [https://www.iso.org/en/standard/17893.html ISO 9985:1996] Information and Documentation -- Transliteration of Armenian characters into Latin characters
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Assamese
|Assamese
|Belarusian
|Belarusian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-russe-du-bielorusse-et-de-lukrainien-contemporains Translittération du russe, du biélorusse et de l'ukrainien contemporains] based on [https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages <br>
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:
{| class="wikitable" style="background:none; width:50%"
|+
! style="background-color:#f8f9fa; border:solid 1px grey;width:5%" |N° d'ordre ISO
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Translittération de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la translittération de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Translittération de la minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la translittération de la minuscule
|- style="vertical-align: top;"
|9
|Ё
|0401
|Ë
|00CB
|ё
|0451
|ë
|00EB
|}
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Bulgarian
|Bulgarian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-bulgare-et-du-macedonien-contemporains Translittération du bulgare et du macédonien contemporains] based on [https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Chinese
|Chinese
|Chinese characters
|Chinese characters
|[https://www.iso.org/en/standard/61420.html ISO 7098:2015] Information and Documentation -- Romanization of Chinese
|[https://www.iso.org/en/standard/61420.html ISO 7098:2015] Information and Documentation -- Romanization of Chinese and ALA-LAC Romanization Table – [https://www.loc.gov/catdir/cpso/romanization/chinese.pdf Chinese] follow the principle of Pinyin. In the absence of [https://mcas-proxyweb.mcas.ms/certificate-checker?login=false&&originalUrl=https://www.iso.org.mcas.ms/fr/standard/61420.html?McasTsid=20893&&McasCSRF=04aadd76f607132bd68928974deeaeec2ed98cb4c3366e74a2d39a4e38683437 ISO ISO 7098:2015], it is appropriate to follow the ALA-LC Romanization table – [https://www.loc.gov/catdir/cpso/romanization/chinese.pdf Chinese], with the following exceptions:<br>
<br>
<ul>
<li>Names of continents and regions which have already become Chinese words are written as one word.</li>
* Feizhou (非洲, Africa) '''NOT''' Fei Zhou
* Nanmei (南美, South America) '''NOT''' Nan Mei
* Dongnanya (东南亚, Southeast Asia) '''NOT''' Dong nan Ya <br>
<li>Ethnic names and tribe names are written as one word with the initial letter capitalized.</li>
* Hanzu (汉族, Han, Chinese ethnic group) '''NOT''' Han zu
* Maolizu (毛利族, Māori) '''NOT''' Maoli zu
* Weiwuerzu (维吾尔族, Uighur, Chinese ethnic group) '''NOT''' Weiwuer zu <br>
<li>Language names are written as one word with the initial letter capitalized.</li>
* Yingyu (英语，English) '''NOT''' Ying yu
* Kejiahua (客家话, Hakka) '''NOT''' Kejia hua <br>
<li>Religions/religious followers are written as one word with the initial letter capitalized.</li>
* Jidujiao (基督教, Christianity) '''NOT''' Jidu jiao
* Jidutu (基督徒, Christian) '''NOT''' Jidu tu </ul><br>
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.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Georgian
|Georgian
|Georgian alphabet
|Georgian alphabet
|[https://www.iso.org/en/standard/17892.html ISO 9984:1996] Information and Documentation -- Transliteration of Georgian characters into Latin characters
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-georgien Translittération du géorgien] based on [https://www.iso.org/en/standard/17892.html ISO 9984:1996] Information and Documentation -- Transliteration of Georgian characters into Latin characters
|-
|Greek
|Greek alphabet
|[https://www.iso.org/standard/5215.html ISO 843:1997] Information and documentation -- Conversion of Greek characters into Latin characters
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Gujarati
|Gujarati
|Canadian Aboriginal syllabics
|Canadian Aboriginal syllabics
|[https://www.loc.gov/catdir/cpso/romanization/inuktitut.pdf ALA-LC 2011] Inuktitut romanization table
|[https://www.loc.gov/catdir/cpso/romanization/inuktitut.pdf ALA-LC 2011] Inuktitut romanization table
|- style="vertical-align: top;"
|Japanese
|Japanese script (hiragana, katakana et kanji)
|[https://www.loc.gov/catdir/cpso/romanization/japanese.pdf ALA-LC 2012] Japanese Romanization Table
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Kannada
|Kannada
|Kannada alphasyllabary
|Kannada alphasyllabary
|[https://www.iso.org/en/standard/28333.html ISO 15919:2001] Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
|[https://www.iso.org/en/standard/28333.html ISO 15919:2001] Information and Documentation -- Transliteration of Devanagari and related Indic scripts into Latin characters
|- style="vertical-align: top;"
|Korean
|Korean script
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-coreen-han-kul-et-han-ca Translittération du coréen (han kūl et han ča)]
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Slavic and non-Slavic Languages
|Slavic and non-Slavic Languages
|Macedonian
|Macedonian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|[https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-bulgare-et-du-macedonien-contemporains Translittération du bulgare et du macédonien contemporains] based on [https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Malayalam
|Malayalam
|Russian
|Russian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-russe-du-bielorusse-et-de-lukrainien-contemporains Translittération du russe, du biélorusse et de l'ukrainien contemporains] based on [https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages <br>
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:
{| class="wikitable" style="background:none; width:50%"
|+
! style="background-color:#f8f9fa; border:solid 1px grey;width:5%" |N° d'ordre ISO
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Translittération de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la translittération de la majuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Translittération de la minuscule
! style="background-color:#f8f9fa; border:solid 1px grey; width:5%" |Code Unicode de la translittération de la minuscule
|- style="vertical-align: top;"
|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.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Sanskrit, Prakrit
|Sanskrit, Prakrit
|Serbian
|Serbian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|[https://www.loc.gov/catdir/cpso/romanization/serbian.pdf ALA-LC Romanization Tables -- Serbian] [Replaces ISO 9:1995 table as of 2021-11-12]
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Tajiki
|Tajiki
|Ukrainian
|Ukrainian
|Cyrillic alphabet
|Cyrillic alphabet
|[https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|BnF [https://kitcat.bnf.fr/consignes-catalogage/translitteration-du-russe-du-bielorusse-et-de-lukrainien-contemporains Translittération du russe, du biélorusse et de l'ukrainien contemporains] based on [https://www.iso.org/en/standard/3589.html ISO 9:1995] Information and Documentation -- Transliteration of Cyrillic characters into Latin characters -- Slavic and non-Slavic languages
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|Yiddish
|Yiddish
|}
|}
''Late update: 2020-04-26'' <!--(2020-04-26)-->
''Last update: 2022-12-15'' <!--(2022-12-15)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
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".
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: [Mailto:bac.pfan-fnap.lac@canada.ca bac.pfan-fnap.lac@canada.ca].
This is not a closed list and suggestions are welcome: [Mailto:pfan-fnap@bac-lac.gc.ca pfan-fnap@bac-lac.gc.ca].
{| class="wikitable sortable mw-collapsible" style="background:none;"
{| class="wikitable sortable mw-collapsible" style="background:none;"
| style="width:300px;" |Véhicule spatial
| style="width:300px;" |Véhicule spatial
| style="width:125px;" |Corporate Body
| style="width:125px;" |Corporate Body
|- style="vertical-align:top;"
|<span style="color:red>Lyrics
|<span style="color:red>Paroles
|<span style="color:red>Work</span>
|- style="vertical-align:top;"
|<span style="color:red>Libretto
|<span style="color:red>Livret
|<span style="color:red>Work</span>
|- style="vertical-align:top;"
|- style="vertical-align:top;"
|Program
|Program
Lastly, note that a ''senior lecturer'' is more of a "professeur associé" than a "chargé de cours".
Lastly, note that a ''senior lecturer'' is more of a "professeur associé" than a "chargé de cours".
''Last Update: 2020-06-19'' <!--(2020-06-19)-->
''Last Update: 2022-03-22'' <!--(2022-03-22)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
=Procedures for Duplicates=
=Procedures for Duplicates=
1) Choose the authority record to retain when there are duplicates by following the following order of priority:
'''Step 1: Selection'''<br>
''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:
<span id="046$u$v"></span><ol>
<li>Prefer a record that already has a 016 field over one that does not.</li>
<li>Prefer a LAC record over a record from BAnQ or universities. </li>
<ol>''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 : [mailto:pfansuppression-deletionfnap@bac-lac.gc.ca 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.
<br>
''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. </ol>
<li>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.
</li>
<li>Prefer an RDA record over a non-RDA record.
<li>Prefer a more complete record over one that is less complete.</li>
<div style="margin-left:25px;">
<div style="margin-left:25px;">
Example 1: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
Example 1: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
Example 2: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
Example 2: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
Example 3: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
Example 3: <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div>
</div></ol>
<div style="margin-bottom:0px; margin-left:0px; padding-right:25px; padding-left:75px; padding-top:10px; padding-bottom:10px; text-indent:-75px;">
''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.<br>
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.<br>
</div>
</div>
<div style="margin-bottom:0px; margin-left:0px; padding-right:25px; padding-left:75px; padding-top:0px; padding-bottom:10px; text-indent:-75px;">
''Situation 3:'' Duplicates between any new records created in Canadiana on or after June 2nd, 2020.<br>
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.
</div>
'''Step 2 : Modifications''' <br>
''Record to be retained''</span><span id="046$u$v">
<br>
PFAN et BAC <br>
<ol>
<li> Update the preferred record.</li>
<li>Make the following modifications to the record to be retained:</li>
<ol>
<li type="a">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.</li>
<div style="margin-left:25px;">
Exemple :
<div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">016 ## 1026F7926F $z 1030B8987</div>
</div>
<br>
<li type="a">If the record to be deleted contains a 035 field with the symbol CaQQLA <span style="color:red>and a field 373 with the mention Université Laval,</span> copy <span style="color:red>the information from both fields into</span> the record to be retained. Do not copy a 035 field with any other symbol.</li>
<div style="margin-left:25px;">
<div style="margin-left:25px;">
Example :
<div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">035 ## (CaQQLA)XX4513984</div>
</div>
<br>
<li type="a">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.</li>
<br>
</ol></ol>
''Record(s) to be deleted<br><span id="046$u$v">
PFAN <br>
<ol>
<li> Make the following modifications to the record(s) to be deleted:</li>
<ol>
<li type="a">Add a 667 field containing the note "Notice doublon, signalée pour suppression car remplacée par [numéro Canadiana de la notice à conserver<span style="color:red>]</span> ([date]). »</li>
<li type="a">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. </li>
<li type="a">If there is already a field 016 with a Canadiana number, do not change field 016. </li>
</ol></ol>
_____<br>BAC : Does not apply. Proceed to step 3.<br><br>
'''Step 3 : Deletion'''<br>PFAN :
<ol>
<li type="a">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. <li>
<li type="a">Notify LAC regarding records to be deleted that have a unique Canadiana number XXXXAXXXX(F) by communicating the OCLC control number by email to [mailto:pfansuppression-deletionfnap@bac-lac.gc.ca pfansuppression-deletionfnap@bac-lac.gc.ca] with subject line: Doublons avec 016 valide. <li>
</ol>
_____<br>
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”. <br>
_____<br>
''Note for PFAN and LAC:''For undifferentiated records, see the instructions in section [[PFAN_-_Name_Authority_Manual#008.2F32_Undifferentiated_personal_name|008/32 Undifferentiated personal name]] in the ''Name Authority Manual''.
<br>
''Last update: 2022-11-22''<!--(2022-11-22)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
= 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.
{| class="wikitable" style="background:none;"
|+
|- style="vertical-align: top;"
|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.
<div style=margin-left:23px;>''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.</div>
* 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.
|- style="vertical-align: top;"
|3XX
|
* All 3XX fields must be translated.
|- style="vertical-align: top;"
|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 : <span style="font-family:courier new;">670 ## LC/NAF, [date of the search] $b(<span style="color:red>point d'accès : [access point]; [other</span> data])</span>
* Note : It is possible to record, in field [[PFAN_-_Name_Authority_Manual#672_Title_related_to_the_entity|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'''
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">"Dérived" from LC/NAF:</div>
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)
</div>
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">New Canadiana record (when the resource on hand is not cited in the derived record):</div>
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)
</div>
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">016 ## 1026F7926F $z 1030B8987</div>
<div style="font-family:sans-serif">New Canadiana record (when the resource on hand is cited in the derived record):</div>
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)
</div>
</div>
''Last update: 2022-12-09''<!--(2022-12-09)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
= Procedure for partial modification of records describing works and expressions =
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:'''
# Applying this procedure is not mandatory, it is entirely up to the participant.
# 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.
# 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 : [[PFAN_-_Other_Documentation#Non-exhaustive_List_of_Verifications_to_Make_to_an_Existing_Record Non-exhaustive|List of Verifications to Make to an Existing Record]].
# 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 [[PFAN_-_Other_Documentation#Procedures_for_Duplicates|Procedures for Duplicates]].
'''Procedure:'''
<ol>
<ol>
<li value="2">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.</li>
<li>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..</li>
<li>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:
<ol>
<li type="a">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.</li>
<li type="a">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:
<ol>
<li type="i">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. </li>
<li type="i">Add the following 667 note:
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">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.</div></li>
</ol>
</li>
</ol>
</li>
<li>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 <span style="color:red>2</span>b). </li>
<li>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.</li>
</ol>
</ol>
<br>
'''Examples'''<br>
''Note: Only relevant fields have been included in these examples.''
<br>
'''Example 1: Name authority record, and batch-loaded work authority record<span style="color:red>s</span> '''
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">Name authority record modified to add a date of death in the authorized access point:</div>
016 ## 0100D5363F
100 1# Blais, Marie-Claire, $d 1939-2021
</div>
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">Work authority record, batch-loaded and not revised, before the partial modification:</div>
[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
<div style="font-family:sans-serif">Work authority record, batch-loaded and not evaluated, after the partial modification:</div>
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.
</div>
</div>
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif"><span style="color:red>Work authority record with a unique Canadiana number before change:</span></div>
<span style="color:red>016 ## 0100D5363F</span>
<span style="color:red>100 1# Blais, Marie-Claire, $d 1939- $t Saison dans la vie d'Emmanuel</span>
<div style="font-family:sans-serif"><span style="color:red>Work authority record with a unique Canadiana number after change:</span></div>
<span style="color:red>016 ## 0100D5363F</span>
<span style="color:red>100 1# Blais, Marie-Claire, $d 1939-2021. $t Saison dans la vie d'Emmanuel</span>
</span></div>
'''Example 2: Batch-loaded name authority record, and batch-loaded expression authority record '''
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">Batch-loaded name authority record, before revision:</div>
[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
<div style="font-family:sans-serif">Name authority record, after revision:</div>
016 ## 1038H8594F
100 0# Arrien, $d environ 95-environ 175
</div>
</div>
''Last update: 2020-07-28''<!--(2020-07-28)-->
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-60px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">Batch-loaded work authority record, not revised, before the partial modification:</div>
[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
<div style="font-family:sans-serif">Batch-loaded work authority record, not revised, after the partial modification:</div>
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.
</div>
''Last update: 2022-11-22''<!--(2022-11-22)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
=Useful External Resources=
=Useful External Resources=
* [https://boundingbox.klokantech.com/ Bounding Box Tool] <span style="color:red>[NEW]</span>
* [http://access.rdatoolkit.org/wka1881.html 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)
* [http://access.rdatoolkit.org/wka1881.html 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)
* [https://web.library.yale.edu/cataloging/music/nmphdbk A Handbook of Examples For Use in Authority Records Created By the NACO-Music Project]
* [https://web.library.yale.edu/cataloging/music/nmphdbk A Handbook of Examples For Use in Authority Records Created By the NACO-Music Project]
* [https://www.babelstone.co.uk/Unicode/whatisit.html What Unicode character is this?]
* [https://www.babelstone.co.uk/Unicode/whatisit.html What Unicode character is this?]
''Last update: 2021-03-12''<!--(2021-03-04)-->
''Last update: 2023-01-16''<!--(2023-01-12)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[Category:PFAN]]
[[Category:PFAN]]
