PFAN - Other Documentation - Revision history

Nathalie.mainville: /* Non-exhaustive List of Qualifiers */

2025-06-13T16:59:04Z

Non-exhaustive List of Qualifiers

Nathalie.mainville: /* Romanization */

2025-05-30T14:25:51Z

Romanization

Nathalie.mainville: /* Procedures for Duplicates */

2025-01-31T15:32:22Z

Procedures for Duplicates

Nathalie.mainville: /* Procedures for Duplicates */

2025-01-31T15:32:07Z

Procedures for Duplicates

Nathalie.mainville: /* Romanization */

2025-01-31T14:36:07Z

Romanization

Show changes

Nathalie.mainville: /* Procedures for Duplicates */

2024-10-08T19:23:36Z

Procedures for Duplicates

Nathalie.mainville: /* Establishing certain entities in the name authority file */

2024-08-26T14:05:13Z

Establishing certain entities in the name authority file

Nathalie.mainville: /* Establishing certain entities in the name authority file */

2024-04-18T16:05:48Z

Establishing certain entities in the name authority file

Nathalie.mainville at 16:05, 18 April 2024

2024-04-18T16:05:21Z

Nathalie.mainville: /* LC Subject Cataloging Manual, H 405 - Establishing Certain Entities in the Name or Subject Authority File */

2024-04-16T19:33:26Z

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

@@ Line 1,389: / Line 1,389: @@
 | style="width:125px;" |Corporate Body
 |- style="vertical-align:top;"
-|<span style="color:red>Lyrics
+|Lyrics
-|<span style="color:red>Paroles
+|Paroles
-|<span style="color:red>Work</span>
+|Work
 |- style="vertical-align:top;"
-|<span style="color:red>Libretto
+|Libretto
-|<span style="color:red>Livret
+|Livret
-|<span style="color:red>Work</span>
+|Work
 |- style="vertical-align:top;"
 |Program
@@ Line 1,466: / Line 1,466: @@
 |Fichier informatique
 |Work
 |}
@@ Line 1,489: / Line 1,497: @@
 Lastly, note that a ''senior lecturer'' is more of a "professeur associé" than a "chargé de cours".
-''Last Update: 2022-03-22'' <!--(2022-03-22)-->
+''Last Update: 2025-06-13'' <!--(2025-06-13)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 1,042: / Line 1,042: @@
 |Georgian alphabet
 |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
-|-
+|-style="vertical-align: top;"
 |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;"
+<span style="color:red>Tool : [https://transliteration.nlg.gr/?lang=e  transliteration.nlg.gr] (box ISO 843:1997)</span>
 |Gujarati
 |Gujarati alphasyllabary
@@ Line 1,228: / Line 1,229: @@
 |}
-''Last update: 2025-01-31'' <!--(2025-01-30)-->
+''Last update: 2025-05-30'' <!--(2025-05-30)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 1,507: / Line 1,507: @@
 <li>Prefer a more complete record over one that is less complete.</li>
 <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  is not RDA compliant; record 2 comes from BAnQ and is RDA compliant. Record 1 from LAC is retained because <span style="color:red>criteriion 1 has</span> priority over criterion <span style="color:red>3</span>.</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  is not RDA compliant; record 2 comes from BAnQ and is RDA compliant. Record 1 from LAC is retained because <span style="color:red>criterion 1 has</span> priority over criterion <span style="color:red>3</span>.</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 <span style="color:red>2</span> has priority over criteria <span style="color:red>3</span> and <span style="color:red>4</span>.</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 <span style="color:red>3</span> has priority over criterion <span style="color:red>4</span>.</div>

@@ Line 1,507: / Line 1,507: @@
 <li>Prefer a more complete record over one that is less complete.</li>
 <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  is not RDA compliant; record 2 comes from BAnQ and is RDA compliant. Record 1 from LAC is retained because <span style="color:red>criteriion 1 has</span> priority over criterion <span style="color:red>3</span>.</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 <span style="color:red>2</span> has priority over criteria <span style="color:red>3</span> and <span style="color:red>4</span>.</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 <span style="color:red>3</span> has priority over criterion <span style="color:red>4</span>.</div>
 </div></ol>
@@ Line 1,571: / Line 1,571: @@
 <br>
-''Last update: 2024-10-08''<!--(2024-10-08)-->
+''Last update: 2025-01-31''<!--(2025-01-31)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 1,432: / Line 1,432: @@
 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.
@@ Line 1,449: / Line 1,449: @@
 <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>
+Keep the pre-June 2nd, 2020 LAC record, or the migrated record, following the order of priority outlined above (under Situation 1). Follow steps <span style="color:red">1 and 2</span>.<br>
 </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.
+Keep the first record (the older one), according to the date entered on file, in field 008 (character positions 00-05). Follow steps <span style="color:red">1 and 2</span>.
 </div>
@@ Line 1,476: / Line 1,476: @@
 <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"><span style="color:red">Add a variant form (4XX) based on the form of name or title used as the authorized access point in the record to be deleted (whether it’s been evaluated or not), if it is considered a useful variant form for the record that will be retained. Please note the following:</li>
+<li type="a">Add a variant form (4XX) based on the form of name or title used as the authorized access point in the record to be deleted (whether it’s been evaluated or not), if it is considered a useful variant form for the record that will be retained. Please note the following:</li>
-*<span style="color:red">Do not systematically add as a variant form (4XX) the authorized access point present in the record to be deleted. Keep in mind the instructions in the Participant’s Manual: « Do not add references solely for automatic conflict detection and updating of bibliographic records » . (See the [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D | Participant’s Manual, Cross-references (4XX et 5XX)]].)
+*Do not systematically add as a variant form (4XX) the authorized access point present in the record to be deleted. Keep in mind the instructions in the Participant’s Manual: « Do not add references solely for automatic conflict detection and updating of bibliographic records » . (See the [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D | Participant’s Manual, Cross-references (4XX et 5XX)]].)
-*<span style="color:red">Cataloguers must make sure that a variant form deemed useful in the record to be retained is a valid RDA access point and is established according to PFAN practices. For instance, if the authorized access point includes a date of birth, this date must also appear in the cross-reference, even if this form is derived from an authorized access point that did not include a date of birth (in the record to be deleted). The reverse is also true: normally, dates are not included in variant forms if not present in the authorized access point, unless a date is added to resolve a conflict between this variant form and an authorized access point in another record. Another example: in a name-title access point, the name element must be identical to the authorized access point for the agent, even if the form of this access point was different in the record to be deleted.
+*Cataloguers must make sure that a variant form deemed useful in the record to be retained is a valid RDA access point and is established according to PFAN practices. For instance, if the authorized access point includes a date of birth, this date must also appear in the cross-reference, even if this form is derived from an authorized access point that did not include a date of birth (in the record to be deleted). The reverse is also true: normally, dates are not included in variant forms if not present in the authorized access point, unless a date is added to resolve a conflict between this variant form and an authorized access point in another record. Another example: in a name-title access point, the name element must be identical to the authorized access point for the agent, even if the form of this access point was different in the record to be deleted.
-*<span style="color:red">Use subfield $w when appropriate, that is, when the variant form is absolutely identical to the authorized access point in the record to be deleted. Subfield $w may be used in more than one 4XX field. Since the variant form must be a valid RDA access point, code nnea should not be used.</span>
+*Use subfield $w when appropriate, that is, when the variant form is absolutely identical to the authorized access point in the record to be deleted. Subfield $w may be used in more than one 4XX field. Since the variant form must be a valid RDA access point, code nnea should not be used.</span>
 <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>
@@ Line 1,506: / Line 1,506: @@
 <br>
-''Last update: 2024-03-14''<!--(2024-03-14)-->
+''Last update: 2024-10-08''<!--(2024-10-08)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 18: / Line 18: @@
 = Establishing certain entities in the name authority file =
-<span style="color:red>[NEW]</span>
 Most access points belong to well-defined categories and are established either as names of persons, corporate bodies, jurisdictions, uniform titles, named meetings, etc. in the name authority file, or as subject headings such as automobiles, geographical entities, etc. in the subject authority file. However, certain named entities have caused problems in the past with regard to
@@ Line 110: / Line 110: @@
+|
 |-style="vertical-align:top"
-|Avions nommés
+|<span style="color:red>Avions individuels</span>
-|Airplanes, Named
+|<span style="color:red>Airplanes, Individual</span>
 |110
+|
@@ Line 912: / Line 912: @@
 -->
-''Last update: 2024-04-18''<!--(2024-04-18)-->
+''Last update: 2024-08-26''<!--(2024-08-26)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 3: / Line 3: @@
 {{Template:PFAN Tabs}}
 <br>
 <!--
@@ Line 9: / Line 11: @@
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]
 -->
+<!--
 =LC Subject Cataloging Manual, H 405 - Establishing Certain Entities in the Name or Subject Authority File=
 <blockquote>'''''Note 1 :''''' LC SHM Instruction Sheet [https://www.loc.gov/aba/publications/FreeSHM/H0405.pdf H 0405 - Establishing Certain Entities in the Name or Subject Authority File]  &nbsp;&nbsp;(PDF, 76 KB)&nbsp;&nbsp;. 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 [https://www.loc.gov/aba/publications/FreeSHM/H0405.pdf SHM H 405].</blockquote><blockquote>'''''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):</blockquote><blockquote>• Cantons québécois (divisions cadastrales)</blockquote><blockquote>• Circonscriptions électorales</blockquote><blockquote>• Districts judiciaires</blockquote><blockquote>• Divisions d'enregistrement</blockquote><blockquote>• Divisions de recensement</blockquote><blockquote>• Régions et sous-régions administratives québécoises</blockquote>
 = Establishing certain entities in the name authority file =
 Most access points belong to well-defined categories and are established either as names of persons, corporate bodies, jurisdictions, uniform titles, named meetings, etc. in the name authority file, or as subject headings such as automobiles, geographical entities, etc. in the subject authority file. However, certain named entities have caused problems in the past with regard to
 <li>if the access point should be included in the name authority file according to descriptive cataloging conventions or in the subject authority file according to subject cataloging conventions; and
@@ Line 879: / Line 883: @@
+|
 |}
--->
 <!--
 |- style="vertical-align:top"
@@ Line 908: / Line 912: @@
 -->
-''Last update: 2021-02-16''<!--(2021-02-01)-->
+''Last update: 2024-04-18''<!--(2024-04-18)-->
 [[#toc|''Return to Table of Contents'' <big>⮝</big>]]

@@ Line 214: / Line 214: @@
 |Circonscriptions électorales
 [Electoral districts]
 |n/a
 |151
@@ Line 381: / Line 387: @@
 |Divisions de recensement
 [Census divisions]
 |n/a
 |151