Changes

{{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}}<br>

{{Template: PFAN Tabs}}<br>

== 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.

Note: DCM Z1 tells catalogers to spell out or abbreviate the names of months (e.g., January or Jan.) rather than using a numeral to represent them (e.g., 1/5/14) when giving dates in the 670 field (e.g., when recording a person's birth or death date or the date an online resource was viewed) because U.S. practice for recording dates using only numerals differs from the practice in some other countries. This helps to facilitate international participation in NACO.

'''Note:''' DCM Z1 tells catalogers to spell out or abbreviate the names of months (e.g., January or Jan.) rather than using a numeral to represent them (e.g., 1/5/14) when giving dates in the 670 field (e.g., when recording a person's birth or death date or the date an online resource was viewed) because U.S. practice for recording dates using only numerals differs from the practice in some other countries. This helps to facilitate international participation in NACO.

== What are the prescribed elements in the 670 field? ==

== What are the prescribed elements in the 670 field? ==

The MARC 21 Authority Format defines the 670 (source data found) field as a repeatable variable field which is comprised of non-repeatable subfields $a and $b. Subfield $a (source citation) is always required; however, subfield $b (information found) is necessary only when information is being provided to support access points or entity attributes being recorded in the 0XX, 1XX, 3XX, 4XX and sometimes the 5XX fields. DCM Z1 prescribes four elements:

The ''MARC 21 Authority Format'' defines the 670 (source data found) field as a repeatable variable field which is comprised of non-repeatable subfields $a and $b. Subfield $a (source citation) is always required; however, subfield $b (information found) is necessary only when information is being provided to support access points or entity attributes being recorded in the 0XX, 1XX, 3XX, 4XX and sometimes the 5XX fields. DCM Z1 prescribes four elements:

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.

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.

Note: DCM Z1, reminds catalogers that: "the NAR does not serve as a biographical sketch of a person ..." and to "use judgment to determine how much data to record ..." The ideal 670 is cogent and concise yet complete.

'''Note:''' DCM Z1, reminds catalogers that: "the NAR does not serve as a biographical sketch of a person ..." and to "use judgment to determine how much data to record ..." The ideal 670 is cogent and concise yet complete.

== Is a subfield $b always required in a 670 field? ==

== Is a subfield $b always required in a 670 field? ==

As noted in Question 2 of this FAQ, the MARC 21 Authority Format requires a subfield $a; however, subfield $b is necessary only when information is being provided to support access points or entity attributes being recorded in the 0XX, 1XX, 3XX, 4XX and sometimes the 5XX fields.

As noted in Question 2 of this FAQ, the ''MARC 21 Authority Format'' requires a subfield $a; however, subfield $b is necessary only when information is being provided to support access points or entity attributes being recorded in the 0XX, 1XX, 3XX, 4XX and sometimes the 5XX fields.

For example, if usage for the entity being established is contained in the title of the item being cataloged (subfield $a), and the item contains no other usage or identifying information about the entity, the subfield $b may be omitted. When creating or updating work/expression NARs it is seldom necessary to add a subfield $b to the NAR unless recording research. Nonetheless, in both these cases the inclusion/repetition of information in a subfield $b is not prohibited.

For example, if usage for the entity being established is contained in the title of the item being cataloged (subfield $a), and the item contains no other usage or identifying information about the entity, the subfield $b may be omitted. When creating or updating work/expression NARs it is seldom necessary to add a subfield $b to the NAR unless recording research. Nonetheless, in both these cases the inclusion/repetition of information in a subfield $b is not prohibited.

Examples:

Examples:

670 $a The autobiography of Ethel Firebrace, 1937.

670 $a The autobiography of Ethel Firebrace, 1937.

Access point established as: Firebrace, Ethel

''    Access point established as: Firebrace, Ethel''

 

 

670 $a Proceedings of the 24th International Congress of Papyrology, Helsinki, 1-7 August, 2004, 2007.

''  Place of birth entered in 370 $a as: Newstead (N.Y. : Ville)''

  Access point established as: International Congress of Papyrology $n (24th : $d 2004 : $c Helsinki, Finland)

'' Date of birth entered in 046 $f as: 1811-09-27 $2 edtf''

  Date of birth entered in 046 $f as: 1811-09-27 $2 edtf

==Is adding the name of the agent responsible for creating the work cited in the 670 subfield $a totally forbidden?==

==Is adding the name of the agent responsible for creating the work cited in the 670 subfield $a totally forbidden?==