Difference between revisions of "PFAN - Rules for contribution"

From wiki
Jump to navigation Jump to search
 
(72 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<!-- {{In use| 24 h (Currently being edited by A. Dunnett, LAC)}} -->
+
<!-- {{In use| 24 h (Currently being edited by A. Dunnett, LAC)}} -->
 
[[fr:PFAN - Règles de contribution]]
 
[[fr:PFAN - Règles de contribution]]
 
{{Template:PFAN Tabs}}
 
{{Template:PFAN Tabs}}
 +
{{Template:PFAN Contribution EN}}
  
 +
==General Rules for Contributions==
 +
<ol>
 +
<li>The file contains two types of records:<br>
 +
<ol style="list-style-type: lower-roman; margin-left: 5em">
 +
<li>French Canadiana name authority records, which contain descriptions of persons, families, corporate bodies, geographic entities, works, and expressions, have OCLC record numbers (field 001) begin with the letters "ncf". These records are created and modified by PFAN participants.
 +
</li><li>Canadian Subject Headings (CSH) records, which are used to express and provide access to the subject content of documents about Canada and Canadian subjects. They can be identified by the OCLC control number (field 001) which begins with the letters "cash", and by the code in fields 008/11 (k - Canadiana Subject Headings) and 040 $b (eng). They are not the responsibility of PFAN and can only be changed by LAC staff.</li></ol>
 +
 +
<li>Participating libraries contribute to the file by establishing authorities generated in the course of their cataloguing activities. However, 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:
  
__TOC__
+
<ol style="list-style-type: lower-roman; margin-left: 5em">
 +
<li>All bodies that are part of an established hierarchy; e.g., when establishing a body that is entered subordinately to its parent body, if a name authority record for the parent body is not present in the authority file, it must be established and contributed as well.</li>
  
==General Rules for Contributions==
+
<li>All bodies referred through in cross-references; e.g., if an authorized access point is entered independently and a variant access point is given through a higher body, the higher body needs to be represented in the authority file as well; this may mean that the library will need to create an additional name authority record in addition to the one the library needs to use in its catalogue.</li>
# Le fichier contient des descriptions de personnes, familles, collectivités, entités géographiques, œuvres et expressions.
+
 
# Les bibliothèques participantes contribuent au fichier en établissant les autorités générées dans le cadre de leurs activités de catalogage. Les bibliothèques participantes n’ont toutefois pas l’obligation d'établir une notice d'autorité pour chaque point d'accès inclus dans une notice bibliographique ni toutes les notices d’autorité reliées à un point d’accès particulier excepté dans les cas prévus :<br>
+
<li>All personal and corporate names used in see also references (5XXs); e.g., when establishing a name for an author who uses a pseudonym, or an access point representing an earlier or later name of a corporate body, the library will need to connect the access points by means of see-also references. In order to avoid blind references, the participant will need to make sure that the corresponding authorized access point is established.</li>
 +
 
 +
<li>All access points under which preferred titles are established; e.g., if an author-title record with the conventional collective title Works is entered under an author who is not established in the authority file, a name authority record for the author must be contributed as well.</li>
  
<ol style="list-style-type: lower-roman; margin-left: 5em">
+
<li>Although participating libraries are not required to contribute name-titles authority records, if one is contributed, all eligible elements must be represented in the authority file.</li>
<li>Toutes les collectivités qui font partie d'une hiérarchie établie; par exemple, si on établit un point d'accès pour une collectivité qui figure en sous-vedette d'une collectivité supérieure, il faut aussi établir l'autorité pour la collectivité supérieure si celle-ci n'est pas déjà présente dans le fichier d'autorité.</li>
 
<li>Toutes les collectivités mentionnées dans les renvois; par exemple, si une collectivité est mise en vedette à son propre nom et qu'elle figure dans un renvoi en sous-vedette d'une collectivité supérieure, celle-ci doit également être représentée dans le fichier d'autorité; cela peut signifier que la bibliothèque devra créer une autorité de nom supplémentaire, en plus de celle dont elle a besoin dans son catalogue.</li>
 
<li>Tous les noms de personnes et de collectivités utilisés dans les renvois Voir aussi (5XX); par exemple, lorsqu'elle établit un nom pour un auteur qui utilise un pseudonyme ou pour une collectivité antérieure ou postérieure représentant un changement de nom, la bibliothèque doit relier les points d'accès au moyen de renvois Voir aussi. Dans le but d'éviter des renvois impasses, les participants doivent s'assurer que le point d'accès correspondant a été établi.</li>
 
<li>Tous les points d'accès sous lesquels les titres uniformes sont enregistrés; par exemple, si on crée une autorité pour le titre collectif conventionnel Œuvre pour un auteur qui n'est pas établi dans le fichier d'autorité, une notice d'autorité pour cet auteur doit aussi être créée.
 
<li>Bien que les bibliothèques participantes n'aient pas d'obligation de créer des notices d'autorité de titre uniforme, si une telle autorité est créée, tous les éléments pertinents doivent être présents dans le fichier d'autorité.</li>
 
 
</ol>
 
</ol>
  
# <li value="3">Le fichier ne contient pas de doublons. Les bibliothèques participantes doivent s’assurer qu’une notice d’autorité n’existe pas déjà avant d’en créer une nouvelle. Par conséquent, les bibliothèques participantes doivent mettre à jour une notice autorité existante plutôt que d’en créer une nouvelle lorsqu’elles veulent ajouter des renseignements supplémentaires sur l’entité représentée par la notice (par exemple, une date de naissance).</li>
+
<li> <li value="3">The file <span style="color:red">must</span> not contain duplicates. Participating libraries must ensure that an authority record does not already exist before creating a new one. Consequently, participating libraries must update an existing authority record rather than create a new one when they wish to include additional information about the entity represented by the record (for example, a birth date).</li>
# Lorsqu’une autorité dont le codage n’indique pas qu’elle est conforme à RDA (008/10 (Règles de catalogage descriptif) avec valeur autre que z et pas de 040 $e « rda ») est révisée, les points d’accès qu’elle comporte doivent être révisés si nécessaire pour être conformes à RDA et le codage des zones 008 et 040 modifié en conséquence.
+
<li>When an authority contains coding which indicates that it is not RDA compliant (008/10 (Descriptive cataloging rules) containing a value other than z and no 040 $e "rda") is revised, the access points it contains must be revised, if necessary, to comply with RDA and the coding in fields 008 and 040 modified accordingly.
# Les autorités doivent être formulées en MARC 21 selon RDA et en suivant les options indiquées dans les LC-PCC PS, les énoncés de politique de BAC-BAnQ et les politiques mises en place par le Comité des normes.
+
<li>The authorities must be formulated in MARC21 according to RDA and follow the options indicated in the LC-PCC PS, the LAC-BAnQ policy statements and other policies established by the Standards Committee.
# Une notice d'autorité de nom doit contenir les éléments de base suivants :
+
 
 +
<li><li value="6">A name authority record must contain the following elements:
 
<ol style="list-style-type: lower-roman; margin-left: 5em">
 
<ol style="list-style-type: lower-roman; margin-left: 5em">
<li>le point d'accès autorisé (zone MARC 1XX);</li>
+
<li>the authorized access point (MARC field 1XX);</li>
<li>les sources servant à justifier le point d’accès autorisé, y compris les ajouts faisant partie du point d'accès autorisé, les variantes de point d'accès et certains éléments d’identification (zone MARC 670);</li>
+
<li>the sources used to justify the authorized access point, including additions that are part of the authorized access point, variant forms of the access point and certain identification elements (MARC field 670);</li>
<li>le cas échéant, tout point d’accès associé servant à exprimer des relations (zones MARC 5XX) ou à enregistrer des variantes de forme (zones MARC 4XX);</li>
+
<li>the cross-references leading to the authorized access point from variant access points (MARC field 4XX) or from related access points (MARC field 5XX) if appropriate.
<li>des données de contrôle et la désignation du contenu afin d’identifier correctement et de manipuler les données.</li> </ol>
+
<li>control data and the content designation for proper identification and manipulation of the data.</li> </ol>
  
<p style="margin-left: 3em;">Une notice d’autorité peut également comprendre :</p>
+
<p style="margin-left: 3em;">An authority record may contain :</p>
 
<ol style="list-style-type: lower-roman; margin-left: 5em">
 
<ol style="list-style-type: lower-roman; margin-left: 5em">
<li>des informations supplémentaires, enregistrées dans des zones fixes (008) et dans des zones de note de la notice d'autorité (zones MARC 667, 675 ou 678);
+
<li>additional information, recorded in fixed fields (008) and in note fields of the authority record (MARC fields 667, 675 ou 678);
<li>des zone MARC facultatives telles que les zones 046 et 3XX;</li>
+
<li>optional MARC fields such as fields 046 et 3XX;</li>
<li>des points d’accès équivalents dans les zones de liaison MARC 7XX.</li>
+
<li>equivalent access points in the MARC 7XX linking fields.</li>
 
</ol>
 
</ol>
  
 
Sources:
 
Sources:
 
* [https://www.loc.gov/catworkshop/courses/naco-RDA/Module%201-NACO%20Foundations.pptx Module 1 -- NACO Foundations] (Last update: Apr. 6, 2017)
 
* [https://www.loc.gov/catworkshop/courses/naco-RDA/Module%201-NACO%20Foundations.pptx Module 1 -- NACO Foundations] (Last update: Apr. 6, 2017)
* [https://www.loc.gov/catdir/cpso/dcmz1.pdf Descriptive cataloging manual Z1: Name and series Authority records.] Prepared by the Policy and Standards Division, Library of Congress. October 2018.
+
* [https://www.loc.gov/catdir/cpso/dcmz1.pdf Descriptive cataloging manual Z1: Name and series Authority records.] Prepared by the Policy and Standards Division, Library of Congress. October 2018.
 
* [https://www.loc.gov/aba/pcc/naco/documents/npm3rd.pdf NACO Participants' Manual. 3rd Edition.] Edited by Patricia Van Ryn and William L. Starck. July 31, 2005
 
* [https://www.loc.gov/aba/pcc/naco/documents/npm3rd.pdf NACO Participants' Manual. 3rd Edition.] Edited by Patricia Van Ryn and William L. Starck. July 31, 2005
 
* [https://www.loc.gov/aba/pcc/naco/parameters.html NACO Program Parameters]
 
* [https://www.loc.gov/aba/pcc/naco/parameters.html NACO Program Parameters]
''Dernière mise à jour : 23 mai 2019''
+
''Last Update: 2022-09-15''<!--(2023-05-12)-->
 
 
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
 
 
 
==Mandatory MARC Fields==
 
 
 
{| class="wikitable mw-collapsible" style="border-collapse: collapse;" border="1" ;
 
! style="background-color:darkgray; border:solid 1px black; " |MARC Field
 
! style="background-color:darkgray; border:solid 1px black; " | Note
 
|- style="vertical-align: top;"
 
|Leader
 
|Supplied by WMS
 
|- style="vertical-align: top;"
 
|003
 
|Supplied by WMS
 
|- style="vertical-align: top;"
 
|008
 
|Code completely
 
|- style="vertical-align: top;"
 
|016
 
|
 
|- style="vertical-align: top;"
 
|040
 
|Supplied by WMS
 
|- style="vertical-align: top;"
 
|046 $f $g
 
|Supply the birth date (9.3.2) and death date (9.3.3.) if they are known but not included in the authorized access point
 
|- style="vertical-align: top;"
 
|1XX
 
|
 
|- style="vertical-align: top;"
 
|368 $c
 
|Supply another designation associated with a person (9.6) when it is not included in the authorized access point for:
 
* a person named in a sacred text or in an apocryphal book
 
* a fictitious or legendary person
 
* a real non-human entity.
 
|-
 
|4XX
 
|Supply if necessary.
 
|- style="vertical-align: top;"
 
|500
 
|Supply for different identities.
 
|- style="vertical-align: top;"
 
|510
 
|Supply for sequential relationships between corporate bodies other than conferences, only to immediately preceeding or succeeding entities (establish relationships between conferences only in records for authorized collective access points)  
 
|- style="vertical-align: top;"
 
|663
 
|Supply for individuals that have three different identities or more
 
|- style="vertical-align: top;"
 
|667
 
|Supply for certain situations explained in [[PFAN_-_Name_Authority_Manual#667_Nonpublic_general_note|''Name Authority Manual, 667'']] and in other guidelines
 
|- style="vertical-align: top;"
 
|670
 
|Supply to cite the catalogued resource and to justify the authorized access point, including additions that are part of the authorized access point, variant access points and certain identification elements
 
|- style="vertical-align: top;"
 
|675
 
|Supply to cite the catalogued resource when the resource does not supply any information
 
|}
 
 
 
[[#toc|''Retour au sommaire'' <big>⮝</big>]]
 
 
 
==Éléments RDA fondamentaux PFAN==
 
  
[[#toc|''Retour au sommaire'' <big>⮝</big>]]  
+
[[#top|''Return to Top of Page'' <big>⮝</big>]]
  
 
[[Category:PFAN]]
 
[[Category:PFAN]]

Latest revision as of 11:30, 12 May 2023

About PFAN News and Updates Rules for Contributions Name Authority Manual Participant's Manual PFAN Policy Statements PFAN Training Frequently Asked Questions (FAQ) Other Documentation LAC
Rules for Contribution    |    Core RDA Elements for PFAN    |    Mandatory MARC Fields for PFAN

General Rules for Contributions

  1. The file contains two types of records:
    1. French Canadiana name authority records, which contain descriptions of persons, families, corporate bodies, geographic entities, works, and expressions, have OCLC record numbers (field 001) begin with the letters "ncf". These records are created and modified by PFAN participants.
    2. Canadian Subject Headings (CSH) records, which are used to express and provide access to the subject content of documents about Canada and Canadian subjects. They can be identified by the OCLC control number (field 001) which begins with the letters "cash", and by the code in fields 008/11 (k - Canadiana Subject Headings) and 040 $b (eng). They are not the responsibility of PFAN and can only be changed by LAC staff.
  2. Participating libraries contribute to the file by establishing authorities generated in the course of their cataloguing activities. However, 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:
    1. All bodies that are part of an established hierarchy; e.g., when establishing a body that is entered subordinately to its parent body, if a name authority record for the parent body is not present in the authority file, it must be established and contributed as well.
    2. All bodies referred through in cross-references; e.g., if an authorized access point is entered independently and a variant access point is given through a higher body, the higher body needs to be represented in the authority file as well; this may mean that the library will need to create an additional name authority record in addition to the one the library needs to use in its catalogue.
    3. All personal and corporate names used in see also references (5XXs); e.g., when establishing a name for an author who uses a pseudonym, or an access point representing an earlier or later name of a corporate body, the library will need to connect the access points by means of see-also references. In order to avoid blind references, the participant will need to make sure that the corresponding authorized access point is established.
    4. All access points under which preferred titles are established; e.g., if an author-title record with the conventional collective title Works is entered under an author who is not established in the authority file, a name authority record for the author must be contributed as well.
    5. Although participating libraries are not required to contribute name-titles authority records, if one is contributed, all eligible elements must be represented in the authority file.
  3. The file must not contain duplicates. Participating libraries must ensure that an authority record does not already exist before creating a new one. Consequently, participating libraries must update an existing authority record rather than create a new one when they wish to include additional information about the entity represented by the record (for example, a birth date).
  4. When an authority contains coding which indicates that it is not RDA compliant (008/10 (Descriptive cataloging rules) containing a value other than z and no 040 $e "rda") is revised, the access points it contains must be revised, if necessary, to comply with RDA and the coding in fields 008 and 040 modified accordingly.
  5. The authorities must be formulated in MARC21 according to RDA and follow the options indicated in the LC-PCC PS, the LAC-BAnQ policy statements and other policies established by the Standards Committee.
  6. A name authority record must contain the following elements:
    1. the authorized access point (MARC field 1XX);
    2. the sources used to justify the authorized access point, including additions that are part of the authorized access point, variant forms of the access point and certain identification elements (MARC field 670);
    3. the cross-references leading to the authorized access point from variant access points (MARC field 4XX) or from related access points (MARC field 5XX) if appropriate.
    4. control data and the content designation for proper identification and manipulation of the data.

    An authority record may contain :

    1. additional information, recorded in fixed fields (008) and in note fields of the authority record (MARC fields 667, 675 ou 678);
    2. optional MARC fields such as fields 046 et 3XX;
    3. equivalent access points in the MARC 7XX linking fields.

    Sources:

    Last Update: 2022-09-15

    Return to Top of Page