2,071
edits
Changes
PFAN - Other Documentation (view source)
Revision as of 16:17, 6 November 2023
, 16:17, 6 November 2023→Non-exhaustive List of Verifications to Make to an Existing Record
|043
|043
|This field cannot be used in records for geographic names (records with field 151). Delete this field in other cases such as when the record contains an occurrence of field 100, 110, 111 or 130.
|This field cannot be used in records for geographic names (records with field 151). Delete this field in other cases such as when the record contains an occurrence of field 100, 110, 111 or 130.
|- style="vertical-align: top;"
|<span style="color:red>046</span>
|<span style="color:red>In authority records for corporate names, please check that the dates in subfields $s and $t are indeed the earliest and latest dates in a period of activity, and not the dates the corporate body was established or terminated. If the information refers to the establishment date or the termination date, please recode these dates in subfields $q and $r. In the case of meetings, congresses, etc., please keep in mind that the dates associated with a single meeting, or a specific conference belonging to a series of conferences, are recorded in subfields $s and $t, while the dates of establishment and termination of a series of conferences are recorded in subfields $q and $r. For further information, please consult the Name authority manual, section 046. </span>
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|053
|053
667 Pour le 055, utiliser PS8623.</div>
667 Pour le 055, utiliser PS8623.</div>
Delete the 667 field containing "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" after finalizing the record.
Delete the 667 field containing "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" after finalizing the record.
<span style="color:red>In records derived from the LC/NAF file, remove any 667 fields indicating that URIs have been added to the records.
<span style="color:red>''Examples :''</span>
<div style="padding-left:15px; padding-top:5px; padding-right:30px; padding-bottom:5px; font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;"><span style="color:red>667 ## $a URIs added to this record for the PCC URI MARC Pilot. Please do not remove or edit the URIs.</span>
<div style="padding-left:60px; text-indent:-60px;"><span style="color:red>667 ## $a URIs added to 3XX and/or 5XX fields in this record for the PCC URI MARC Pilot. Please do not remove or edit the URIs.</div>
</div></span>
_____
BAnQ: Before sending records to OCLC, ensure that all of the 667 fields have been copied into field 899 in Portfolio to preserve their contents in the event that local content is deleted by another PFAN participant, except fields 667 beginning with one of the following expressions: "En subdivision :", "Ne pas utiliser en subdivision" and "UTILISATION COMME VEDETTE-MATIÈRE :". If the content of a 667 field copied into field 899 is no longer pertinent for BAnQ, consider also deleting the corresponding 899 field in Portfolio.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|670
|670
|Delete this field if subfield $2 lacnaf is present.
|Delete this field if subfield $2 lacnaf is present.
|}
|}
''Last update: 2023-09-20''<!--(2023-09-20)-->
''Last update: 2023-11-06''<!--(2023-10-26)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]