Changes

no edit summary
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 - FAQ sur la zone 670 (Source des données) dans les notices d’autorités de noms pour NACO]]
 
[[fr:PFAN - FAQ sur la zone 670 (Source des données) dans les notices d’autorités de noms pour NACO]]
 
{{Template: PFAN Tabs}}
 
{{Template: PFAN Tabs}}
 
<br>
 
<br>
 
+
<small>''PFAN version adapted from the [https://www.loc.gov/aba/pcc/naco/670faq.html original NACO version]''</small>
 
== Is there any required punctuation or style in the 670 field? ==
 
== Is there any required punctuation or style in the 670 field? ==
 
There is '''no required''' punctuation and style in the 670 field. There is some prescribed content (per the ''MARC 21 Authority Format'') and some suggested punctuation (see no. 2-4 of this FAQ). The 670 section in the Descriptive Cataloging Manual (DCM) Z1 supplement to the ''MARC 21 Authority Format'' states, '''"conventions in regard to punctuation and style ... are not prescriptive ... Punctuation and style need not be consistent from record to record as long as the information is clear and accurate."''' For historical purposes and because catalogers will continue to find NARs in the authority file which contain "old style" citations, the DCM Z1 shows varied examples.
 
There is '''no required''' punctuation and style in the 670 field. There is some prescribed content (per the ''MARC 21 Authority Format'') and some suggested punctuation (see no. 2-4 of this FAQ). The 670 section in the Descriptive Cataloging Manual (DCM) Z1 supplement to the ''MARC 21 Authority Format'' states, '''"conventions in regard to punctuation and style ... are not prescriptive ... Punctuation and style need not be consistent from record to record as long as the information is clear and accurate."''' For historical purposes and because catalogers will continue to find NARs in the authority file which contain "old style" citations, the DCM Z1 shows varied examples.
Line 16: Line 16:  
In '''subfield $a''' of the 670:
 
In '''subfield $a''' of the 670:
   −
The '''title proper''' of the resource being cited.
+
# The '''title proper''' of the resource being cited.
The '''date of publication''', etc.
+
# The '''date of publication, etc'''.
 +
 
 
In '''subfield $b''':
 
In '''subfield $b''':
   −
The specific location(s) of the information found.
+
# The '''specific location(s) of the information''' found.
The information found (enclosed in parentheses)
+
# The '''information found (enclosed in parentheses)'''.
 +
 
 
See the DCM Z1 for additional guidelines and examples for specific categories of materials, types of dates, etc.
 
See the DCM Z1 for additional guidelines and examples for specific categories of materials, types of dates, etc.
   Line 35: Line 37:  
Examples:
 
Examples:
   −
<pre>
+
<pre style="font-family:courier new;">
 
670 $a The autobiography of Ethel Firebrace, 1937.
 
670 $a The autobiography of Ethel Firebrace, 1937.
 
</pre>
 
</pre>
 
''    Access point established as: Firebrace, Ethel''
 
''    Access point established as: Firebrace, Ethel''
<pre>
+
<pre style="font-family:courier new;">
 
670 $a Actes du 26e Congrès international de papyrologie, Genève, 16-21 août 2010, 2012.
 
670 $a Actes du 26e Congrès international de papyrologie, Genève, 16-21 août 2010, 2012.
 
</pre>
 
</pre>
Line 45: Line 47:     
''but''
 
''but''
<pre>
+
<pre style="font-family:courier new;">
 
670 $a Autobiography of Mrs. Laura Dickey and choice miscellaneous selections, 1895: $b page 5 (née le 27 septembre 1811 à Newstead, Erie County, New York)
 
670 $a Autobiography of Mrs. Laura Dickey and choice miscellaneous selections, 1895: $b page 5 (née le 27 septembre 1811 à Newstead, Erie County, New York)
 
</pre>
 
</pre>
Line 61: Line 63:     
Example:
 
Example:
<pre>
+
<pre style="font-family:courier new;">
 
670 $a Dickinson, Emily. Selected poems, [1990]: $b achevé d’imprimer (Gregory C. Aaron)  
 
670 $a Dickinson, Emily. Selected poems, [1990]: $b achevé d’imprimer (Gregory C. Aaron)  
 
</pre>
 
</pre>
Line 70: Line 72:  
'''A monograph:'''
 
'''A monograph:'''
   −
<pre>
+
<pre style="font-family:courier new;">
 
670 $a La pasión de Octubre, 1996 : $b p. de t. (P.J. González Cuesta) rabat arrière (Pablo González Cuesta, né à Séville, en 1969)
 
670 $a La pasión de Octubre, 1996 : $b p. de t. (P.J. González Cuesta) rabat arrière (Pablo González Cuesta, né à Séville, en 1969)
 
</pre>
 
</pre>
 
'''A database reference source:'''
 
'''A database reference source:'''
<pre>
+
<pre style="font-family:courier new;">
 
670 $a OCLC, 23 janvier 2001 $b (point d’accès : González Cuesta, Pablo Juan; usage : P.J. González Cuesta)  
 
670 $a OCLC, 23 janvier 2001 $b (point d’accès : González Cuesta, Pablo Juan; usage : P.J. González Cuesta)  
 
</pre>
 
</pre>
Line 93: Line 95:  
In general, when newly establishing a personal name that does not conflict with another access point in the database within which one is cataloging, it is not necessary to cite another source beyond the item in hand except in the following situations:
 
In general, when newly establishing a personal name that does not conflict with another access point in the database within which one is cataloging, it is not necessary to cite another source beyond the item in hand except in the following situations:
   −
<div style="padding-left:50px; text-indent:-20px">
+
<!-- <div style="padding-left:50px; text-indent:-20px"> </div> -->
A. When the rules for establishing personal names require consultation with a reference source (e.g., RDA 9.2.2.2 and 9.2.2.5.2)
+
<ol type="A">
 
+
<li style="margin-bottom:10px;">When the rules for establishing personal names require consultation with a reference source (e.g., RDA 9.2.2.2 and 9.2.2.5.2)
B. When justifying an addition to the name access point (fuller form of name, dates, title, etc.) and that information was found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
+
</li>
 
+
<li style="margin-bottom:10px;">When justifying an addition to the name access point (fuller form of name, dates, title, etc.) and that information was found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
C. When justifying a variant access point and that information was found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
+
</li>
 
+
<li style="margin-bottom:10px;">When justifying a variant access point and that information was found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
D. When recording a variant usage which would not require a variant access point (e.g., unused additional forenames for a person, a minor difference in a corporate body name that occurs several words into the name, etc.) and that information is found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
+
</li>
 
+
<li style="margin-bottom:10px;">When recording a variant usage which would not require a variant access point (e.g., unused additional forenames for a person, a minor difference in a corporate body name that occurs several words into the name, etc.) and that information is found in a source other than the item in hand (i.e., during the normal course of searching in the database in which the work is being performed).
E. When recording elements other than access points (e.g., an associated place, occupation, etc.) and that information is found in a source other than the item in hand (i.e. during the normal course of searching in the database in which the work is being performed).
+
</li>
</div>
+
<li style="margin-bottom:10px;">When recording elements other than access points (e.g., an associated place, occupation, etc.) and that information is found in a source other than the item in hand (i.e. during the normal course of searching in the database in which the work is being performed).
 +
</li>
 +
</ol>
    
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
 
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
Line 127: Line 131:  
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
 
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
   −
==[Not included at present]==
+
==[Not included at present] If I search the LC database...==
 
<!-- == If I search the LC database should I provide an "LC database" citation in a 670 field? ==
 
<!-- == If I search the LC database should I provide an "LC database" citation in a 670 field? ==
   Line 143: Line 147:     
== May I also use URIs in subfields $a or $b in 670 fields? ==
 
== May I also use URIs in subfields $a or $b in 670 fields? ==
Generally, no. However, some corporate names and/or title strings may have the general appearance of URIs (usually without the Internet protocol designation, e.g., http://), and may be cited as names and titles in 670 $a as needed (cf. http://www.loc.gov/aba/pcc/naco/corpfaq.html#9 for more information). In order to be “actionable,” URIs found in $u should include the protocol, e.g., $u http://www.stephenking.com
+
Generally, no. However, some corporate names and/or title strings may have the general appearance of URIs (usually without the Internet protocol designation, e.g., http://), and may be cited as names and titles in 670 $a as needed (cf. //www.loc.gov/aba/pcc/naco/corpfaq.html#9 for more information). In order to be “actionable,” URIs found in $u should include the protocol, e.g., $u http://www.stephenking.com
    
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
 
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
Line 205: Line 209:  
Generally, existing 670 fields should not be modified, however, there are some cases where modification may be warranted:
 
Generally, existing 670 fields should not be modified, however, there are some cases where modification may be warranted:
   −
1. To correct catalogers’ typos  or clarify information that may be needlessly confusing.
+
# To correct catalogers’ typos  or clarify information that may be needlessly confusing.
2. To include additional entity attribute information (e.g., fuller form of name, date information, place of birth/death, etc.) encountered when consulting the same resource.
+
# To include additional entity attribute information (e.g., fuller form of name, date information, place of birth/death, etc.) encountered when consulting the same resource.
   −
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
+
'''Last update of the [https://www.loc.gov/aba/pcc/naco/670faq.html original NACO version]: 2017-09-08'''
   −
PFAN version last updated: XXXXX
+
'''Last update of the PFAN version: 2020-06-16'''
   −
<small>''PFAN version adpapted from [https://www.loc.gov/aba/pcc/naco/670faq.html original NACO version] last updated: 2017-09-08''</small>  
+
[[FAQ on the 670 (Source Data Found) Field in Name Authority Records (NARs) for NACO#toc|''Return to Table of Contents'' <big>⮝</big>]]
 
<!--[[PFAN - FAQ for Field 670 (Source Data Found) in NACO Name Authority Records#toc|''Return to Table of Contents'' <big>⮝</big>]]-->
 
<!--[[PFAN - FAQ for Field 670 (Source Data Found) in NACO Name Authority Records#toc|''Return to Table of Contents'' <big>⮝</big>]]-->
   −
<br>
   
[[Category:PFAN]]
 
[[Category:PFAN]]
1,277

edits