Changes

64 bytes added ,  19:22, 9 February 2023
no edit summary
Line 19: Line 19:  
== When a person's name in a Latin resource is derived from a non-Latin script, can I create the AAP using the form found in the resource? ==
 
== When a person's name in a Latin resource is derived from a non-Latin script, can I create the AAP using the form found in the resource? ==
   −
It must first be determined whether instruction 9.2.2.5.3 applies in this case by looking at the [[PFAN_-_%C3%89nonc%C3%A9s_de_politique_du_PFAN#9.2.2.5.3_.5BNOUVEAU.5D|related policy statement]]. In the case of textual works, if the text of that person's first work to be catalogued was originally written in a Latin script language, 9.2.2.5.3 does not apply and the CIP may be based on the form in the catalogued resource. If it later becomes apparent that most of the person's works were written in a non-Latin script, the provisions of the policy statement should be applied.
+
It must first be determined whether instruction 9.2.2.5.3 applies in this case by looking at the [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Names_found_in_a_non-preferred_script_.5BNEW.5D|related policy statement]]. In the case of textual works, if the text of that person's first work to be catalogued was originally written in a Latin script language, 9.2.2.5.3 does not apply and the CIP may be based on the form in the catalogued resource. If it later becomes apparent that most of the person's works were written in a non-Latin script, the provisions of the policy statement should be applied.
   −
If 9.2.2.5.3 is applicable, cataloguers must follow the alternative of this instruction, as directed in the [[PFAN_-_Énoncés_de_politique_du_PFAN#9.2.2.5.3.2C_Alternative|associated policy statement]].
+
If 9.2.2.5.3 is applicable, cataloguers must follow the alternative of this instruction, as directed in the [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Alternative|associated policy statement]].
    
== What do I do when I need to create the AAP for a person for whom I have the non-Latin name in the resource I have in my hands? ==
 
== What do I do when I need to create the AAP for a person for whom I have the non-Latin name in the resource I have in my hands? ==
   −
In this case, 9.2.2.5.3 is applicable and cataloguers must follow the alternative of this instruction, following the guidelines in the [[PFAN_-_Énoncés_de_politique_du_PFAN#9.2.2.5.3.2C_Alternative|related policy statement]].
+
In this case, 9.2.2.5.3 is applicable and cataloguers must follow the alternative of this instruction, following the guidelines in the [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Alternative|related policy statement]].
    
== For a name in Chinese, Japanese, Korean or Cyrillic script, I have consulted the three preferred sources (Encyclopédie Larousse, Le Petit Robert and Encyclopédie Universalis) in vain. I must now use the systematically romanised form of the name. What does this mean? How do I proceed? ==
 
== For a name in Chinese, Japanese, Korean or Cyrillic script, I have consulted the three preferred sources (Encyclopédie Larousse, Le Petit Robert and Encyclopédie Universalis) in vain. I must now use the systematically romanised form of the name. What does this mean? How do I proceed? ==
   −
This means determining the person's preferred name in non-Latin script by consulting the sources mentioned under 9.2.2.2 and then converting that preferred name to Latin script using the PFAN-approved romanization table for the language or script concerned. The PFAN-approved tables can be found on the [[PFAN_-_Autre_documentation#Romanisation|PFAN wiki]].
+
This means determining the person's preferred name in non-Latin script by consulting the sources mentioned under 9.2.2.2 and then converting that preferred name to Latin script using the PFAN-approved romanization table for the language or script concerned. The PFAN-approved tables can be found on the [[PFAN_-_Other_Documentation#Romanization|PFAN wiki]].
    
== Should preferred titles and variant titles of works be transliterated in fields 1XX and 4XX of authority records? ==
 
== Should preferred titles and variant titles of works be transliterated in fields 1XX and 4XX of authority records? ==
   −
The basic instruction under 6.2.2.7 says to transliterate a title of a work found in a script that differs from a script preferred by the agency creating the data according to the transliteration method adopted by the agency. RDA provides an alternative for selecting as the preferred title a title or form of title established by usage in the reference sources in a language preferred by the agency creating the data.  According to the PFAN PS for [[PFAN_-_Énoncés_de_politique_du_PFAN#6.2.2.7.2C_Alternative_.5BNouveau.5D|6.2.2.7]], PFAN participants may apply the alternative only "for anonymous works created before 1501 that are not in Greek or Latin script." For these works, "choose as the preferred title a title established by usage in French if one exists."  For works in Greek created before 1501, whether anonymous or not, refer to 6.2.2.5. In all other cases, the basic instruction should be applied.
+
The basic instruction under 6.2.2.7 says to transliterate a title of a work found in a script that differs from a script preferred by the agency creating the data according to the transliteration method adopted by the agency. RDA provides an alternative for selecting as the preferred title a title or form of title established by usage in the reference sources in a language preferred by the agency creating the data.  According to the PFAN PS for [[PFAN_-_PFAN_Policy_Statements#6.2.2.7.2C_Alternative_.5BNew.5D|6.2.2.7]], PFAN participants may apply the alternative only "for anonymous works created before 1501 that are not in Greek or Latin script." For these works, "choose as the preferred title a title established by usage in French if one exists."  For works in Greek created before 1501, whether anonymous or not, refer to 6.2.2.5. In all other cases, the basic instruction should be applied.
    
== I have located the authority of the person for whom I need to create the AAP in the LC/NAF file after checking that 9.2.2.5.3 applies. Can I take the preferred name form as is? ==
 
== I have located the authority of the person for whom I need to create the AAP in the LC/NAF file after checking that 9.2.2.5.3 applies. Can I take the preferred name form as is? ==
Line 39: Line 39:  
Not necessarily. Firstly, it may happen that the name or form of name registered as the preferred name by a PFAN cataloguer is not the same as that chosen by the LC/PCC cataloguer. Secondly, although LC and PCC follow the same criteria on the applicability of instruction 9.2.2.5.3 and also apply the alternative under 9.2.2.5.3, they prefer reference sources in English while PFAN prefers sources in French. According to the sources consulted, it could therefore be that the form chosen by the LC/PCC cataloguer is different from that found in the French reference works. It could also be that the form chosen for one file was found in a reference source in the language preferred by the program, while the form chosen for the other file had to be romanised following unsuccessful searches in the reference sources. Furthermore, the romanization tables used are not necessarily the same depending on the language, so that a romanised form found in the LC/NAF file would not necessarily be valid in Canadiana.
 
Not necessarily. Firstly, it may happen that the name or form of name registered as the preferred name by a PFAN cataloguer is not the same as that chosen by the LC/PCC cataloguer. Secondly, although LC and PCC follow the same criteria on the applicability of instruction 9.2.2.5.3 and also apply the alternative under 9.2.2.5.3, they prefer reference sources in English while PFAN prefers sources in French. According to the sources consulted, it could therefore be that the form chosen by the LC/PCC cataloguer is different from that found in the French reference works. It could also be that the form chosen for one file was found in a reference source in the language preferred by the program, while the form chosen for the other file had to be romanised following unsuccessful searches in the reference sources. Furthermore, the romanization tables used are not necessarily the same depending on the language, so that a romanised form found in the LC/NAF file would not necessarily be valid in Canadiana.
   −
Where 9.2.2.5.3 is applicable  (see [[PFAN_-_%C3%89nonc%C3%A9s_de_politique_du_PFAN#9.2.2.5.3_.5BNOUVEAU.5D|related policy statement]]), the LC/NAF form can only be taken as is if both of the following conditions are met:
+
Where 9.2.2.5.3 is applicable  (see [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Names_found_in_a_non-preferred_script_.5BNEW.5D|related policy statement]]), the LC/NAF form can only be taken as is if both of the following conditions are met:
 
* the preferred name used as the basis for the AAP is in a non-Latin script and is the same as that which would be used by the PFAN;
 
* the preferred name used as the basis for the AAP is in a non-Latin script and is the same as that which would be used by the PFAN;
 
* the ALA-LC romanization table used to convert the name into Latin script is the one approved by the PFAN for the language or script concerned.
 
* the ALA-LC romanization table used to convert the name into Latin script is the one approved by the PFAN for the language or script concerned.
Line 45: Line 45:  
== Can I take the form found in the BnF authority file? ==
 
== Can I take the form found in the BnF authority file? ==
   −
Not necessarily. Where 9.2.2.5.3 is applicable  (see [[PFAN_-_%C3%89nonc%C3%A9s_de_politique_du_PFAN#9.2.2.5.3_.5BNOUVEAU.5D|related policy statement]]), the form found in the BnF file can only be taken as is if both of the following conditions are met:
+
Not necessarily. Where 9.2.2.5.3 is applicable  (see [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Names_found_in_a_non-preferred_script_.5BNEW.5D|related policy statement]]), the form found in the BnF file can only be taken as is if both of the following conditions are met:
 
* the preferred name used as the basis for the AAP is in a non-Latin script and is the same as that which would be used by the PFAN;
 
* the preferred name used as the basis for the AAP is in a non-Latin script and is the same as that which would be used by the PFAN;
 
* the romanization table used by the BnF to convert the name into Latin script is the one approved by the PFAN for the language or script concerned.
 
* the romanization table used by the BnF to convert the name into Latin script is the one approved by the PFAN for the language or script concerned.
Line 55: Line 55:  
== Can I correct the AAP in an existing notice that contains 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 "? ==
 
== Can I correct the AAP in an existing notice that contains 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 "? ==
   −
Any AAP in a record with this note should be reassessed. Care should be taken to ensure that the AAP is consistent with the standards of the PFAN, and therefore with the application of the PS for [[PFAN_-_Énoncés_de_politique_du_PFAN#9.2.2.5.3_.5BNOUVEAU.5D|9.2.2.5.3]].
+
Any AAP in a record with this note should be reassessed. Care should be taken to ensure that the AAP is consistent with the standards of the PFAN, and therefore with the application of the PS for [[PFAN_-_PFAN_Policy_Statements#9.2.2.5.3.2C_Names_found_in_a_non-preferred_script_.5BNEW.5D|9.2.2.5.3]].
    
== Does the PFAN plan to use the MARC 880 (alternative script) field or use the 4XX fields instead? ==
 
== Does the PFAN plan to use the MARC 880 (alternative script) field or use the 4XX fields instead? ==
Line 61: Line 61:  
Like NACO, the PFAN applies [https://www.marc21.ca/M21/CLAS/C062-Annexe-C.html MARC 21 Model B] for records with different writing systems. For this reason, the use of the 880 field is not currently permitted under the  [https://wiki.gccollab.ca/PFAN_-_Guide_des_autorit%C3%A9s_de_noms_-_Suppl%C3%A9ment_MARC_21#880_Graphie_alternative MARC21 Supplement to the Guide to Name Authorities].
 
Like NACO, the PFAN applies [https://www.marc21.ca/M21/CLAS/C062-Annexe-C.html MARC 21 Model B] for records with different writing systems. For this reason, the use of the 880 field is not currently permitted under the  [https://wiki.gccollab.ca/PFAN_-_Guide_des_autorit%C3%A9s_de_noms_-_Suppl%C3%A9ment_MARC_21#880_Graphie_alternative MARC21 Supplement to the Guide to Name Authorities].
   −
== Do I have to create authorities for names and titles that are not originally in Latin script ==
+
== Do I have to create authorities for names and titles that are not originally in Latin script? ==
   −
According to the PFAN General Contribution Rules, " participating libraries are not obligated to establish an authority record for each access point included in a bibliographic record nor all the authority records related to a particular access point except in the following cases”. This includes access points for names and titles not originally in Latin script. For a list of these exceptions, see the [[PFAN_-_Règles_de_contribution|contribution rules]].
+
According to the PFAN General Contribution Rules, " participating libraries are not obligated to establish an authority record for each access point included in a bibliographic record nor all the authority records related to a particular access point except in the following cases”. This includes access points for names and titles not originally in Latin script. For a list of these exceptions, see the [[PFAN_-_Rules_for_contribution|contribution rules]].
    
If a PFAN participant does not have the language skills to prepare a AAP using a systematically romanised form that conforms to PFAN practices where required, they should refrain from creating an authority record.
 
If a PFAN participant does not have the language skills to prepare a AAP using a systematically romanised form that conforms to PFAN practices where required, they should refrain from creating an authority record.