1,277
edits
Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Changes
Jump to navigation
Jump to search
Line 317:
Line 317: + + − 1.670s must be used to support information used as part of a heading in 1XX and 4XX fields.+ + + − 2.For fields 046, 368, 370-378, and 381:+ − + − + − b.use $v if the information/source is not cited in a 670+ − + − c.use of $u is optional, and should always be preceded by $v+ −
PFAN - Name Authority Manual (view source)
Revision as of 08:14, 23 February 2021
, 08:14, 23 February 2021→046 Special coded dates
The following represents PFAN practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670:
The following represents PFAN practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670:
<ol>
<li>670s must be used to support information used as part of a heading in 1XX and 4XX fields.</li>
<li>For fields 046, 368, 370-378, and 381:
<ol>
<li type="a">use of $v is optional if the same information/source is already cited in the 670</li>
<li type="a">use $v if the information/source is not cited in a 670</li>
a.use of $v is optional if the same information/source is already cited in the 670
<li type="a">use of $u is optional, and should always be preceded by $v</li>
</li>
</ol>
</li>
</ol>
Use a 670 field if needed to justify information recorded in other fields for which subfields $u and/or $v are not defined or defined differently.
Use a 670 field if needed to justify information recorded in other fields for which subfields $u and/or $v are not defined or defined differently.
