Changes

PFAN - Other Documentation (view source)

Revision as of 11:20, 18 January 2023

8,068 bytes added , 11:20, 18 January 2023

m

→‎Useful External Resources

Line 26: Line 26:

=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]]

+

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]]

''Last Update with PFAN Examples: 2020-05-04''

Line 40: Line 40:

=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%"

Line 53: Line 59:

|Armenian

|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;"

|Assamese

Line 65: Line 71:

|Belarusian

|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;"

|Bulgarian

|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;"

|Chinese

|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;"

|Georgian

|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

Line 98: Line 148:

|Canadian Aboriginal syllabics

|[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;"

|Kannada

|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

+

|- 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;"

|Slavic and non-Slavic Languages

Line 109: Line 167:

|Macedonian

|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;"

|Malayalam

Line 141: Line 199:

|Russian

|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;"

|Sanskrit, Prakrit

Line 149: Line 231:

|Serbian

|Cyrillic alphabet

−

|[https://www.loc.gov/catdir/cpso/romanization/serbian.pdf ALA-LC Romanization Tables -- Serbian] ~~<span style="color:red>~~[Replaces ISO 9:1995 table as of 2021-11-12]~~</span>~~

+

|[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;"

|Tajiki

Line 170: Line 252:

|Ukrainian

|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;"

|Yiddish

Line 177: Line 259:

|}

−

''~~Late~~ update: ~~2021~~-11-18''

+

''Last update: 2022-12-15''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

Line 317: Line 399:

| style="width:300px;" |Véhicule spatial

| 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;"

|Program

Line 410: Line 500:

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

−

''Last Update: ~~2020~~-06-19''

+

''Last Update: 2022-03-22''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

Line 445: Line 535:

'''Step 2 : Modifications''' <br>

−

~~<span style="color:red">~~''Record to be retained''</span><span id="046$u$v"~~></span~~>

+

''Record to be retained''</span><span id="046$u$v">

<br>

PFAN et BAC <br>

Line 456: Line 546:

Exemple :

+

</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>

+

+

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>

Line 461: Line 557:

<br>

</ol></ol>

−

~~<span style="color:red">~~''Record(s) to be deleted~~</span>~~<br><span id="046$u$v"~~></span~~>

+

''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 ([date]). »</li>

+

<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>

−

~~<span style="color:red">~~<li type="a">If there is already a field 016 with a Canadiana number, do not change field 016. </li~~></span~~>

+

<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. ~~<span style="color:red">~~Proceed to step 3.~~</span>~~<br><br>

+

_____<br>BAC : Does not apply. Proceed to step 3.<br><br>

−

'''Step 3 : Deletion'''~~</span>~~<br>PFAN :

+

'''Step 3 : Deletion'''<br>PFAN :

−

<ol~~><span style="color:red"~~>

+

<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>

−

~~</span>~~</ol>

+

</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”.~~</span>~~ <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: ~~2021~~-09-23''

+

''Last update: 2022-11-22''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

Line 510: Line 606:

* 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([data])</span>

+

** 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>

−

*~~<span style="color:red">~~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. ~~</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'''

Line 545: Line 641:

</div>

−

''Last update: ~~2021~~-06-29''

+

''Last update: 2022-12-09''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

−

= ~~<span style="color:red">~~Procedure for partial modification of records describing works and expressions ~~[NEW]</span>~~ =

+

= 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.

Line 557: Line 653:

'''Conditions:'''

−

# 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.

+

# Applying this procedure is not mandatory, it is entirely up to the participant.

−

~~# 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]].

Line 573: Line 669:

<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; padding-right:25px; padding-left:~~15px~~; padding-top:10px; padding-bottom:10px; 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>

+

<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 b). </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>

Line 587: Line 683:

<br>

−

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

+

'''Example 1: Name authority record, and batch-loaded work authority record<span style="color:red>s</span> '''

Line 605: Line 701:

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>~~

−

+

<div style="font-family:sans-serif">Work authority record, batch-loaded and not evaluated, after the partial modification:</div>

Line 618: Line 713:

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 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>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>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 '''

Line 629: Line 739:

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>~~

−

+

<div style="font-family:sans-serif">Name authority record, after revision:</div>

Line 647: Line 756:

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>~~

−

+

<div style="font-family:sans-serif">Batch-loaded work authority record, not revised, after the partial modification:</div>

Line 660: Line 768:

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-01-26''

+

''Last update: 2022-11-22''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

=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)

* [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?]

−

''Last update: ~~2021~~-03-12''

+

''Last update: 2023-01-16''

[[#toc|''Return to Table of Contents'' <big>⮝</big>]]

[[Category:PFAN]]

Nathalie.mainville

1,990

edits

Changes

PFAN - Other Documentation (view source)

Revision as of 11:20, 18 January 2023

Navigation menu

Search