1,990
edits
Changes
Jump to navigation
Jump to search
Line 180:
Line 180: − ==General Information==+ − + Line 241:
Line 241: + Line 276:
Line 277: − + − + Line 288:
Line 289: − + − − The content of all 665 fields in LAC and BAnQ records has been placed in field 678. It is possible that the original field 665 contained instructions about the access point to use as an author or as a subject heading (see the example under field 665 above). Delete these instructions in field 678 if they have been retained. Consider adding a 667 note on the use of the access point as a subject heading, if applicable. − − '''<big>Justification for field 678</big>''' − − Generally, a 678 field must be justified by a 670 field. If it is not justified and its contents are appropriate for a biographical or historical note, retain the field and add a 670 note citing the internal file of the institution who supplied the 678 field as follows: − <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">670 ## Fichier interne de [abréviation de la bibliothèque participante], [date de consultation de Canadiana] …</div> − Example: − − Existing 678 field: − <div style="padding-left:75px; padding-top:5px; padding-right:30px; padding-bottom:5px; text-indent:-60px; font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;">678 1# Établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail.</div> − Added 670 field: − <div style="padding-left:75px; padding-top:5px; padding-right:30px; padding-bottom:5px; text-indent:-60px; font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;">670 ## Fichier interne de BAC, 29-10-2020 $b (établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail)</div> − If the record was modified after having been migrated, it is necessary to consult the record history file to determine who originally added the 678 field. − − If field 678 is not justified and its contents are not appropriate for a biographical or historial note, do not retain field 678 except if an appropriate note can be written with the information on hand. Note that field 678 is optional. If the contents of the field must be retained because they are not found anywhere else in the record, transfer them to a 670 note citing the the internal file of the institution who supplied the 678 field. − − Example:<br> − The existing 678 field which will be deleted because the contents are not appropriate for a biographical note. − <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">678 1# Né le 6 juin 1973.</div> − Added 670 field: − <div style="font-family:courier new; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">670 ## Fichier interne de l'ULaval, 29-10-2020 $b (né le 6 juin 1973)</div> − +
→Non-exhaustive List of Verifications to Make to an Existing Record
=Non-exhaustive List of Verifications to Make to an Existing Record=
=Non-exhaustive List of Verifications to Make to an Existing Record=
'''General Information'''
* Verify that the characters used are only those in the MARC 8 character set.
* Verify that the characters used are only those in the MARC 8 character set.
* Generally, the information must be provided in French. If a record is derived from an original English record, fields 670 and 675 can remain in English but it must be ensured that the information recorded in other fields is in French. It is understood that all information in English will not necessarily have an equivalent in French. This would be the case, for example, for terms belonging to a controlled vocabulary for which there is no French version. In this case, the information must be deleted.
* Generally, the information must be provided in French. <span style="color:red">When information quoted in field 670 comes from a source in a language other than French, the Guide asks cataloguers to “generally translate the information into French, in an informal manner, summarizing as appropriate”. If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English,</span> fields 670 and 675 can remain in English but it must be ensured that the information recorded in other fields is in French. It is understood that all information in English will not necessarily have an equivalent in French. This would be the case, for example, for terms belonging to a controlled vocabulary for which there is no French version. In this case, the information must be deleted.
{| class="wikitable sortable mw-collapsible" style="background:none;"
{| class="wikitable sortable mw-collapsible" style="background:none;"
|+
|+
* delete all occurrences of subfield $w containing only a single code (for ex. $w d)
* delete all occurrences of subfield $w containing only a single code (for ex. $w d)
* delete all occurrences of subfield $w containing only two codes if the codes are not "nh" (for ex. $w na).
* delete all occurrences of subfield $w containing only two codes if the codes are not "nh" (for ex. $w na).
<span style="color:red">For more information about subfield $w, see the Manual - MARC 21 Supplement, section 4XX.</span>
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|5XX
|5XX
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|670
|670
|If the record was derived from a record originally created in English, it is not necessary to translate the field into French, as the case may be.
|<span style="color:red">If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English</span>, it is not necessary to translate the field into French, as the case may be.
It is generally not necessary to modify an existing 670 field except in cases provided in the FAQ for field 670 (Source data found) in the name authority record for NACO.
It is generally not necessary to modify an existing 670 field except in cases provided in the FAQ for field 670 (Source data found) in the name authority record for NACO.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|675
|675
|If the record was derived from a record originally created in English, it is not necessary to translate the field into French, as the case may be.
|<span style="color:red">If the existing record was originally created by LAC in English, or if it is a migrated record derived from a record that was originally in English</span>, it is not necessary to translate the field into French, as the case may be.
Occurrences of subfield $a following the first occurrence must be preceeded by a semi-colon, space. Add this punctuation if it is missing.
Occurrences of subfield $a following the first occurrence must be preceeded by a semi-colon, space. Add this punctuation if it is missing.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|678
|678
|Ensure that the contents of the field truly consist of biographical or historical information and are appropriate for public display. The text must be worded in the form of concise and complete phrases.
|Ensure that the contents of the field truly consist of biographical or historical, <span style="color:red">that it is appropriate for public viewing, and that it is supported by sources given in a 670 field. For further information, see the Name Authority Manual, section 678 </span>.
|- style="vertical-align: top;"
|- style="vertical-align: top;"
|7XX
|7XX
|Delete this field if subfield $2 lacnaf is present.
|Delete this field if subfield $2 lacnaf is present.
|}
|}
''Last update: 2021-03-16''<!--(2021-03-15)-->
''Last update: 2021-03-30''<!--(2021-03-15)-->
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
