Difference between revisions of "PFAN - Rules for contribution"
Jump to navigation
Jump to search
Line 23: | Line 23: | ||
# <li value="3">The file does 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> | # <li value="3">The file does 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> | ||
− | # 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. | + | # 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. |
# 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. | # 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. | ||
Line 32: | Line 32: | ||
<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>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>control data and the content designation for proper identification and manipulation of the data.</li> </ol> | <li>control data and the content designation for proper identification and manipulation of the data.</li> </ol> | ||
− | |||
<p style="margin-left: 3em;">An authority record may contain :</p> | <p style="margin-left: 3em;">An authority record may contain :</p> |
Revision as of 14:52, 14 January 2021
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 |
General Rules for Contributions
- The file contains descriptions of persons, families, corporate bodies, geographical entities, works and expressions.
- 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:
- 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.
- 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.
- 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.
- 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.
- 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.
- The file does 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).
- 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.
- 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.
- A name authority record must contain the following elements:
- the authorized access point (MARC field 1XX);
- 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);
- 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.
- control data and the content designation for proper identification and manipulation of the data.
An authority record may contain :
- additional information, recorded in fiexed fields (008) and in note fields of the authority record (MARC fields 667, 675 ou 678);
- optional MARC fields such as fields 046 et 3XX;
- equivalent access points in the MARC 7XX linking fields.
Sources:
- Module 1 -- NACO Foundations (Last update: Apr. 6, 2017)
- Descriptive cataloging manual Z1: Name and series Authority records. Prepared by the Policy and Standards Division, Library of Congress. October 2018.
- NACO Participants' Manual. 3rd Edition. Edited by Patricia Van Ryn and William L. Starck. July 31, 2005
- NACO Program Parameters
Last Update: 2019-05-23
Mandatory MARC Fields
MARC Field | Note |
---|---|
Leader | Supplied by WMS |
003 | Supplied by WMS |
008 | Code completely |
016 | |
040 | Supplied by WMS |
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 |
1XX | |
368 $c | Supply another designation associated with a person (9.6) when it is not included in the authorized access point for:
|
4XX | Supply if necessary. |
500 | Supply for different identities. |
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 corporate access points) |
663 | Supply for individuals who have three different identities or more |
667 | Supply for certain situations explained in Name Authority Manual, 667 and in other guidelines |
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 |
675 | Supply to cite the catalogued resource when the resource does not supply any information |