1,999
edits
Changes
→4XX - See From Tracings - General Information
point. This policy was established for collocation purposes (cf. [https://www.loc.gov/aba/publications/FreeSHM/H0430.pdf SHM H 430]). For example:
point. This policy was established for collocation purposes (cf. [https://www.loc.gov/aba/publications/FreeSHM/H0430.pdf SHM H 430]). For example:
<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;">
<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;">
États-Unis. Président (1789-1979 : Washington)
États-Unis. Président (1789-<span style="color:red>1797</span> : Washington)
</div>
</div>
may be used in descriptive cataloging as an access point, but in subject cataloging only the personal name:
may be used in descriptive cataloging as an access point, but in subject cataloging only the personal name:
Follow these guidelines for newly-created authority records. Correct existing records when making any other change to the records.
Follow these guidelines for newly-created authority records. Correct existing records when making any other change to the records.
[2021-03-02]<!--(2021-03-02)-->
[2023-05-08]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F15 Heading Use-Subject Added Entry|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F15 Heading Use-Subject Added Entry|''Supplement'' <big>⮞</big>]]
=== General ===
=== General ===
Do not use 008/32 code “b” (undifferentiated) in an RDA name authority record. Assign 008/32 value “a” for personal name NARs. Use code “n” for families, corporate bodies, and places. For works and expressions, assign value “a” if the access point begins with a personal name, otherwise assign value “n”.
In the past, personal name NARs could be coded as undifferentiated using 008/32 value “b” when the cataloger had no acceptable way of differentiating multiple persons with the same preferred name. Since then, PFAN have followed these guidelines for personal name NARs:
* Do not use code “b” in an RDA name authority record; all personal name authority records coded RDA should be differentiated.
* Do not create new undifferentiated records coded 008/32 “b”. All personal name authority records coded RDA should be differentiated.
* Do not add a new identity to an existing personal name authority record coded 008/32 “b.”
* Do not add a new identity to an existing personal name authority record coded 008/32 “b.”
* Instead, apply [http://original.rdatoolkit.org/rdachp9-fr_rda9-5465.html RDA 9.19.1] to create a unique authorized access point for the person, using suitable additional elements.
=== Maintenance of existing undifferentiated records: ===
'''Important :''' If the only record found for an entity is an undifferentiated record (with field 008/32 coded "b") from a university with the 667 note « 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 », do not use it. Create a new authority record for the entity.<br>
PFAN cataloguer: Report the undifferentiated record to LAC by emailing the OCLC control number to pfansuppression-deletionfnap@bac-lac.gc.ca with the subject line: Notice indifférenciée versée par une université.<br>
LAC cataloguer: Delete the undifferentiated authority record.
It may happen that an existing undifferentiated name authority record, especially one that has been imported from LC/NAF, contains pairs of 670 fields used to group information about each individual covered by the NAR. The first 670 in the pair is an “identifying” 670 field containing a term descriptive of the person’s relationship to the title cited in the second 670 of the pair. The data in the identifying 670 field is contained in subfield $a and enclosed in square brackets. The second 670 in the pair is a “citation” 670 that contains the normal data elements in a resource being cataloged citation.
It may happen that an existing undifferentiated name authority record, especially one that has been imported from LC/NAF, contains pairs of 670 fields used to group information about each individual covered by the NAR. The first 670 in the pair is an “identifying” 670 field containing a term descriptive of the person's relationship to the title cited in the second 670 of the pair. The data in the identifying 670 field is contained in subfield $a and enclosed in square brackets. The second 670 in the pair is a “citation” 670 that contains the normal data elements in a resource being cataloged citation.
''Example:''<br>
''Example:''<br>
</div>
</div>
When information is found to distinguish a person in an existing undifferentiated name record:
When information is found to distinguish a person in an existing undifferentiated from LAC or BAnQ name record:
* Always create a new name authority record for that person, with distinguishing information, and add an indication that the person was formerly on an undifferentiated record (see "[[PFAN_-_Name_Authority_Manual#667_notes_on_records_for_identities_previously_on_undifferentiated_records|667 notes on records for identities previously on undifferentiated records]]" below). If an authority record already exists for that person with the 667 note "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" and coded "a" in field 008/32, use that notice as the "new record".
* Always create a new name authority record for that person, with distinguishing information, and add an indication that the person was formerly on an undifferentiated record (see "[[PFAN_-_Name_Authority_Manual#667_notes_on_records_for_identities_previously_on_undifferentiated_records|667 notes on records for identities previously on undifferentiated records]]" below). If an authority record already exists for that person with the 667 note "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" and coded "a" in field 008/32, use that notice as the "new record".
* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
667 ## Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
667 ## Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number.)''</div>
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC control number.)''</div>
</div>
</div>
</li>
</li>
008/32 = b
008/32 = b
016 ## $a 0000X0000F
100 1# $a Bowman, Anne
100 1# $a Bowman, Anne
New record for the illustrator of Reptiles :
New record for the illustrator of Reptiles :
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
008red/32 = a
016 ## $a [New Canadiana number]
016 ## $a [New Canadiana number]
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
667 ## $a Anciennement incluse dans une notice d'autorité de nom indifférenciée : [Canadiana number of undifferentiated name record].
667 ## $a Anciennement incluse dans une notice d'autorité de nom indifférenciée : [Canadiana number of undifferentiated name record].
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number.)''</div>
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC control number.)''</div>
</div>
</div>
<br>
<br>
==== <span style="color:red">Records coded as undifferentiated that actually represent only one identity</span> ====
==== Records coded as undifferentiated that actually represent only one identity ====
Occasionally an existing record will be coded undifferentiated, but new research indicates that in fact the record represents only one identity.
''<span style="color:red">Example :</span>''<br>
''Example:''<br>
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
008/32 = b
008/32 = b
</div>
</div>
<span style="color:red>It may also happen that we suspect that the value "b" has been mistakenly coded in field 008/32. In such cases, proceed</span> as follows:
In this situation, do the following:
<ul><li>Add a 667 field to the undifferentiated NAR indicating that it has been reported for deletion:
<ul><li>Add a 667 field to the undifferentiated NAR indicating that it has been reported for deletion:
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number..)''</div></li>
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC control number..)''</div></li>
<li>Add in 016 field subfield $z the Canadiana number of the undifferentiated name authority record to be deleted, if any.</li>
<li>Add in 016 field subfield $z the Canadiana number of the undifferentiated name authority record to be deleted, if any.</li>
</div></span>
</div></span>
[2022-02-09]<!--(2022-02-09)-->
[2023-10-26]<!--(2023-10-26)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F32 Undifferentiated personal name|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F32 Undifferentiated personal name|''Supplement'' <big>⮞</big>]]
'''Duplicates'''
'''Duplicates'''
Do not “reuse” a Canadiana number. Once an authority record has been created for a given entity, and once a Canadiana number has been attributed, do not change the data in this authority record to describe a DIFFERENT entity. For instance, do not change the authority record for “Dupont, Jean” to transform it into an authority record describing “Tremblay, Marie” (except if the person’s name has changed).
Do not “reuse” a Canadiana number. Once an authority record has been created for a given entity, and once a Canadiana number has been attributed, do not change the data in this authority record to describe a DIFFERENT entity. For instance, do not change the authority record for “Dupont, Jean” to transform it into an authority record describing “Tremblay, Marie” (except if the person's name has changed).
<ol>'''PFAN'''
<ol>'''PFAN'''
<span style="color:red>'''Partially modified batch-loaded authority records'''</span>
<span style="color:red>'''Partially modified batch-loaded authority records'''</span>
<span style="color:red>Batch-loaded authority records which are partially modified, according to the [[PFAN_-_Other_Documentation#Procedure_for_partial_modification_of_records_describing_works_and_expressions_.5BNEW.5D|Procedure for partial modification of records describing works and expressions]], will include Canadiana number 1111X1111F. This temporary number is added in order to allow the cataloguer to save the record, until such time as the entire record is evaluated to make sure it follows all PFAN standards. This number will have to be replaced by a unique number once the record is evaluated, when the 667 note “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” is deleted. </span>
<span style="color:red>Batch-loaded authority records which are partially modified, according to the [[PFAN_-_Other_Documentation#Procedure_for_partial_modification_of_records_describing_works_and_expressions_.5BNEW.5D|Procedure for partial modification of records describing works and expressions]], will include Canadiana number 1111X1111F. This temporary number is added in order to allow the cataloguer to save the record, until such time as the entire record is evaluated to make sure it follows all PFAN standards. This number will have to be replaced by a unique number once the record is evaluated, when the 667 note “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” is deleted. </span>
[2022-01-26]<!--(2022-01-26)-->
[2022-01-26]<!--(2022-01-26)-->
'''Subfield $d – Modifying agency'''<br>
'''Subfield $d – Modifying agency'''<br>
Subfield $d [MARC 21 code] is added automatically by WMS when modifying NARs or SARs unless your institution’s is already the last MARC subfield $d in the 040 field.
Subfield $d [MARC 21 code] is added automatically by WMS when modifying NARs or SARs unless your institution's is already the last MARC subfield $d in the 040 field.
'''Subfield $e – Description conventions'''<br>
'''Subfield $e – Description conventions'''<br>
[2021-03-09]<!--(2021-03-08)-->
[2021-03-09]<!--(2021-03-08)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#042_Authentication_Code|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#042_Authentication_Code|''Supplement'' <big>⮞</big>]]
= 043 Geographic Area Code <span style="color:red>[New]</span>=
Field 043 can only be used in authority records for geographical names (151).
'''Subfield b – Local GAC code and Subfield $2 – Source of local code'''
For sites located in Quebec, PFAN participants can use subfield $b to record a local code from the list below, representing the administrative region of Quebec where the site is located. This code is formed by the geographic region code "n-cn---" and a two-letter sub-entity local code (e.g., qa) that identifies the administrative region and replaces the last two characters of the "n-cn---" code (e.g., "n-cn---"). (e.g. "n-cn-qa"). Subfield $b is recorded after subfield $a and is followed by subfield $2 cagraq.
''Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
043 ## $a n-cn-qu $b n-cn-qj $2 cagraq
151 ## $a Le Golfe-du-Saint-Laurent (Québec)
</div>
'''Codes d’aires géographiques pour les régions administratives du Québec'''
{| class="wikitable sortable mw-collapsible" style="background:none; width:40%"
|+
! style="background-color:darkgray; border:solid 1px black;width:10%" |
! style="background-color:darkgray; border:solid 1px black; width:20%" |
! style="background-color:darkgray; border:solid 1px black; width:10%" |
|- style="vertical-align: top;"
|n-cn-qa
|Bas-Saint-Laurent
|Région 01
|- style="vertical-align: top;"
|n-cn-qb
|Saguenay–Lac-Saint-Jean
|Région 02
|- style="vertical-align: top;"
|n-cn-qc
|Capitale-Nationale
|Région 03
|- style="vertical-align: top;"
|n-cn-qd
|Mauricie
|Région 04
|- style="vertical-align: top;"
|n-cn-qe
|Estrie
|Région 05
|- style="vertical-align: top;"
|n-cn-qf
|Montréal
|Région 06
|- style="vertical-align: top;"
|n-cn-qg
|Outaouais
|Région 07
|- style="vertical-align: top;"
|n-cn-qh
|Abitibi-Témiscamingue
|Région 08
|- style="vertical-align: top;"
|n-cn-qj
|Côte-Nord
|Région 09
|- style="vertical-align: top;"
|n-cn-qk
|Nord-du-Québec
|Région 10
|- style="vertical-align: top;"
|n-cn-ql
|Gaspésie–Îles-de-la-Madeleine
|Région 11
|- style="vertical-align: top;"
|n-cn-qm
|Chaudière-Appalaches
|Région 12
|- style="vertical-align: top;"
|n-cn-qn
|Laval
|Région 13
|- style="vertical-align: top;"
|n-cn-qo
|Lanaudière
|Région 14
|- style="vertical-align: top;"
|n-cn-qp
|Laurentides
|Région 15
|- style="vertical-align: top;"
|n-cn-qq
|Montérégie
|Région 16
|- style="vertical-align: top;"
|n-cn-qr
|Centre-du-Québec
|Région 17
|- style="vertical-align: top;"
|}
[2023-11-20]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#043_Geographic_Area_Code|''Supplement'' <big>⮞</big>]]
= 046 Special coded dates =
= 046 Special coded dates =
<span id="046_2nd_par">When</span> revising existing authority records, record dates in field 046 even if the heading itself does not have dates in 100 subfield $d, when the information is readily available.
<span id="046_2nd_par">When</span> revising existing authority records, record dates in field 046 even if the heading itself does not have dates in 100 subfield $d, when the information is readily available.
When recording dates in field 046, use the Extended Date Time Format (EDTF) schema in all cases except for centuries; supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd. See date table in [http://original.rdatoolkit.org/lacbanqpschp9_lacbanqps9-304.html LAC-BanQ PS 9.3.1.3].
When recording dates in field 046, use the Extended Date Time Format (EDTF) schema in all cases except for centuries; supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd. See date table in [http://original.rdatoolkit.org/lacbanqpschp9_lacbanqps9-304.html LAC-BanQ PS 9.3.1.3]. <span style="color:red> For the full EDTF specification, see [https://www.loc.gov/standards/datetime/ https://www.loc.gov/standards/datetime/].</span>
''Examples:''
''Examples:''
670 ## $a Wikipédia, 21 juillet 2010 $b (Eleanor Roosevelt; Anna Eleanor Roosevelt; née le 11 octobre 1884 à Manhattan, à New York; morte le 7 novembre 1962)
670 ## $a Wikipédia, 21 juillet 2010 $b (Eleanor Roosevelt; Anna Eleanor Roosevelt; née le 11 octobre 1884 à Manhattan, à New York; morte le 7 novembre 1962)
<div style="margin-top:25px;">
<div style="margin-top:25px;">
670 ## $a Cox, Karen Castellucci. Isabel Allende, 2003 : $b p. 4-5 (en 1981 Allende a commencé à écrire une version romancée des histoires qu'elle avait entendues dans son enfance, qui a été publiée en Espagne en 1982)
670 ## $a Cox, Karen Castellucci. Isabel Allende, 2003 : $b p. 4-5 (en 1981 Allende a commencé à écrire une version romancée des histoires qu'elle avait entendues dans son enfance, qui a été publiée en Espagne en 1982)
</div>
</div>
</div>
<div style="margin-top:25px;"><span style="color:red>
046 ## $s 194X $2 edtf
100 1# $a Hicks, Johnny $c (Saxophonist)
670 ## $a Bryant, W. Blues around the clock [SR] 1945: $b label (Johnny Hicks, tenor sax)
670 ## $a Discogs website, May 27, 2021 $b (Johnny Hicks; tenor sax player who performed with Tab Smith in the 1940s)
</div></span>
670 ## $a Cohen, A.I. Int'l encycl. of women composers, 2nd ed. $b (Turner, Elizabeth, compositrice anglaise du 18e siècle)
</div>
</div>
<span style="color:red>When recording B.C. dates in the 046 field, precede the digits by a hyphen (minus sign). Because there is no year “zero” in the common era calendar, subtract one year from the actual B.C. date, e.g., the year 50 B.C. is recorded -0049.</span>
'''Subfield $2 – Source of date scheme'''
<span style="color:red>''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $s -0199~ $2 edtf
100 0# $a Hellanicus $c (Grammairien), $d environ 200 av. J.-C.
670 ## $a Brill's new Pauly, consulté le 2 août 2011 $b (Hellanicus; grammairien d'Alexandrie; environ 200 av. J.-C.)
</div></span>
When recording a century in the 046 field, use the first two digits of the hundred year span (e.g., use “16” to represent the 17th century, 1600–1699).
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
046 ## $s 17
100 1# $a Turner, Elizabeth, $d activité 18e siècle
670 ## $a Cohen, A.I. Int'l encycl. of women composers, 2nd ed. $b (Turner, Elizabeth, compositrice anglaise du 18e siècle)
</div>
<li>For fields 046, 368, 370-378, and 381:
Note that the 1st century A.D. is represented by value “00” and B.C. centuries have a hyphen <span style="color:red>(</span>minus <span style="color:red>sign)</span> before the digits (e.g., “-04” for the 5th century B.C.). An approximate century (e.g., active approximately 12th century) cannot be recorded in the 046 field.
<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>
<span style="color:red>'''Repeatability:'''</span>
<li type="a">use of $u is optional, and should always be preceded by $v</li>
<span style="color:red>Field 046 is repeatable, but the 046 subfields used to record the dates are not repeatable. Generally, one 046 field with dates conforming to the EDTF schema should be sufficient. However, century dates follow the ISO 8601 standard, not EDTF. When recording century dates in addition to more precise dates, it is therefore necessary to repeat the 046 field.</span>
</ol>
<span style="color:red>'''Conflicting dates'''</span>
</li>
'''Subfield $v – Source of information'''
<span style="color:red>In some situations, resources consulted may present conflicting dates (e.g., conflicting birth or death dates for a person, or start or end dates for a corporate body). In these situations, the 046 field should reflect the cataloger's evaluation of the conflicting date information. It is not necessary to record all the conflicting dates using field 046, nor is it necessary to give a 046 field for each resource consulted. Evaluation of the conflicting dates should generally result in a single 046 field, containing the date(s) the cataloger judges to be most accurate in representing the entity. At the cataloger's discretion, the date(s) recorded in that 046 field may incorporate the conflicting date information and need not correspond exactly to the date(s) selected for the authorized access point.</span>
<span style="color:red>Similarly, any dates added to the authorized access point should reflect the cataloger's evaluation of the conflicting date information, recorded in conformance with the instructions in RDA and the PFAN Policy Statements. If one date predominates in the resources consulted, that date may be considered the most appropriate to use in the authorized access point. If a single date does not predominate, the cataloger may decide to use the “approximately yyyy”, “yyyy?”, or “yyyy or yyyy” format in the authorized access point. In some cases, dates corresponding to the period of activity of the person (RDA 9.19.1.5) may be considered the best choice.</span>
<span style="color:red>''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $f -0156 $g -0085-01-13 $2 edtf
100 1# $a Marius, Caius, $d 157 av. J.-C.-86 av. J.-C.
670 ## $a Syllana varia : aux sources de la première guerre civile romaine, 2008 : $b ressource non disponible (Marius)
670 ## $a Grand dictionnaire encyclopédique Larousse, 1984 $b (Marius (Caius); général et homme politique romain (Cereatae, près d'Arpinum, 157-Rome 86 av. J.-C.))
670 ## $a Dictionnaire encyclopédique Quillet, 1983 $b (Marius (Caius) (156-86 av. J.-C.); né à Arpinium, général romain d'origine plébéienne)
670 ## $a Capitalismo de laçeos, 2011 : $b page de titre (Sérgio G. Lazzarini)
670 ## $a Petit Robert des noms propres, 2006 $b (Marius, en lat. Caius Marius; général et homme politique romain (Cereatae, près d'Arpinum, -157 - Rome -86))
670 ## $a Dictionnaire encyclopédique d'histoire, 1978 $b (Marius, Caius (né à Cereatae, près d'Arpinum, 157, mort à Rome 13.I.86 av. J.-C.); général et homme politique romain)<br>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#046_Special_Coded_Dates|''Supplement'' <big>⮞</big>]]
<div style="font-family:sans-serif; margin-left:85px;">
''(Cataloger has chosen 157 B.C. as the approximate date of birth in both the authorized access point and field 046 because it occurs most frequently in the sources consulted)''</div>
046 ## $f 1907-05-12 $g 2003-06-29 $2 edtf
100 1# $a Hepburn, Katharine, $d 1907-2003
670 ## $a Moi : histoires de ma vie, 1994 : $b page de titre (Katharine Hepburn) page 27 (née le 12 mai 1907)
670 ## $a Contemporary theatre, film & television, c1996 : $b (Katharine Houghton Hepburn, née le 9 novembre 1909 à Hartford, Conn.)
670 ## $a Biography resource center, 2 juillet 2003 $b (Katharine Hepburn (actrice américaine, 1907-2003) ; Contemporary. authors : Katharine (Houghton) Hepburn; née le 12 mai 1907, Hartford, Conn.; morte le 29 juin 2003, Old Saybrook, Conn.; Complete Marquis who's who : Katharine Hepburn; née le 12 mai 1907, Hartford, Conn.)
670 ## $a IMDb, 5 septembre 2023 $b (Katharine Hepburn; née le 12 mai 1907, Hartford, Connecticut; morte le 29 juin 2003, Old Saybrook, Connecticut)
= 080 Universal Decimal Classification Number =
670 ## $a Wikipédia, 5 septembre 2023 $b (Katharine Hepburn; née le 12 mai 1907 à Hartford (Connecticut) et morte le 29 juin 2003 à Old Saybrook (Connecticut); actrice américaine)<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(Cataloger has chosen 1907 as the date of birth in both the authorized access point and field 046 because it occurs most frequently in the sources consulted)''</div>
046 ## $f [1907-05-12,1909-11-09] $g 2003-06-29 $2 edtf
= 083 Dewey Decimal Classification Number =
100 1# $a Hepburn, Katharine, $d 1907-2003<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(Same example as above, reflecting a different decision the cataloger might have made for recording 046 subfield $f)'' </div>
</div>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#083_Dewey_Decimal_Classification_Number|''Supplement'' <big>⮞</big>]]
<span style="color:red>Because the 046 field will be based on information from multiple sources, justification cannot be accurately expressed in subfield $v/$u at the end of the 046 field. The conflicting dates should be recorded in 670 fields. If an existing record has subfield $v/$u as 046 field justification, and the 046 field is being updated as described above, the subfield $v/$u should be removed, and the justification converted to a 670 field, if the conflicting dates are not already justified in an existing 670 field.</span>
= 086 Government Document Call Number =
<span style="color:red>'''Uncertain dates resulting from date calculations'''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#086_Government_Document_Call_Number|''Supplement'' <big>⮞</big>]]
<span style="color:red>In some situations, a calculation may be required to determine which dates to record in the 046 field and the authorized access point. Such calculations may result in uncertain dates.</span>
= 087 Government Document Classification Number =
<span style="color:red>If the consulted resources provide only the person's date of death and their age (in years) at the time of death, as often happens with obituaries, their year of birth will correspond to one of two consecutive years. To calculate those years, first subtract the age from the year of death, then use the resulting year plus its preceding year as the two alternatives for the year of birth.</span>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#087_Government_Document_Classification_Number|''Supplement'' <big>⮞</big>]]
<span style="color:red>''Examples :''
= 1XX Headings - General Information =
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $f [1918,1919] $g 1994-04 $2 edtf
100 1# $a Dalpé, Paul-Émile, $d 1918 ou 1919-1994
670 ## $a Analyse du marché du travail des infirmières au Québec, 1964 : $b page 9 (Paul-Émile Dalpé, président, Fédération nationale des services inc. (C.S.N.))
670 ## $a La Presse, 31 décembre 1994 :$b page B 7 (Paul-Émile Dalpé, président fondateur de la Centrale des syndicats démocratiques, mort en avril 1994 à l'âge de 75 ans)<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(Cataloger subtracted 75, the age at death, from 1994, the year of death; the resulting year, 1919, and the year preceding it, 1918, represent the two possible alternatives for the year of birth)''</div>
</div>
<!--'''SARs'''
<span style="color:red>If non-Gregorian dates are found in consulted resources, uncertain dates may result from calendar conversion differences. Gregorian calendar dates are used in the 046 field and authorized access point. A single date in a non-Gregorian calendar may correspond to one of two Gregorian dates. </span>
<span style="color:red>''Examples :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $f [1967,1968] $2 edtf
100 1# $a Zaeef, Abdul Salam, $d 1967 ou 1968-
#If the resource has more than one form of series title, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7766.html/view RDA 2.12.2.2] and [http://original.rdatoolkit.org/rdachp2-fr_rda2-7759.html/view 2.12.2.5].
670 ## $a Prisonnier à Guantanamo, 2008 : $b page de titre (Mollah Abdul Salam Zaeef)
#If the resource has the series title in more than one language or script on the same source, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7759.html/view RDA 2.12.2.4].
670 ## $a LC/NAF, 25 août 2023 $b (point d'accès : Z̤aʻīf, ʻAbd al-Salām, 1967 or 1968- ; né en 1346 [1967 ou 68])<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(The Hijri calendar date 1346 H converts to either 1967 or 1968 in the Gregorian calendar.)''</div>
</div>
''Establishing an SAR access point:''
'''Subfield $2 – Source of date scheme'''
Always add subfield $2 edtf except after a century.
<li>Exclude from the authorized access point the following information included in the series statement in the bibliographic record for the component part:
'''<span style="color:red>Subfields $q – Establishment date, $r – Termination date,</span> $s – Start period, and $t – End period'''
<li type="a">other title information;</li>
<span style="color:red>Record dates associated with a one-time conference, etc., or a single instance of a
series of conferences, etc. ([https://original.rdatoolkit.org/rdachp11-en_rda11-4572.html RDA 11.4.2] and [https://original.rdatoolkit.org/rdachp11-en_rda11-5252.html RDA 11.13.1.8.1]), use subfields $s and $t.</span>
<li type="a">statement of responsibility;</li>
''<span style="color:red>Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $s 2017-07-27 $t 2017-08-06 $2 edtf
111 2# $a Festival des arts de Saint-Sauveur $n (26e : $d 2017 : $c Saint-Sauveur, Québec)
670 ## $a Festival des arts de Saint-Sauveur, du 27 juillet au 6 août 2017, 2017
</div>
<li>Add a parenthetical qualifier(s) if appropriate according to the guidelines in LAC-BAnQ PS 6.27.1.9.</li>
<span style="color:red>Use the establishment date ([https://original.rdatoolkit.org/rdachp11-en_rda11-4572.html RDA 11.4.3]) and the termination date ([https://original.rdatoolkit.org/rdachp11-en_rda11-4628.html RDA 11.4.4]) of a series of conferences, etc. ([https://original.rdatoolkit.org/rdachp11-en_rda11-5691.html RDA 11.13.1.8.2]) in subfields $q and $r, if that information is known.</span>
''<span style="color:red>Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;"><span style="color:red>
046 ## $q 2019 $2 edtf
110 2# $a Acfas (Association). $b Congrès
670 ## $a L'université du XXIe siècle, 2020 : $b page de titre (87e Congrès de l'Acfas, tenu à l'Université du Québec en Outaouais) page 3 (2019)
'''''Authorized access points for families'''
670 ## $a Congrès de l'Acfas. Programme général, 70e (2002), substitut : $b page de titre (76e Congrès de l'Acfas, du 5 au 9 mai 2008, Centre des congrès de Québec) page ii (Association francophone pour le savoir-Acfas)</span>
</div>
For instructions on using $s and $t for start and end periods in fields 368, and 370-376, see the instructions provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield instructions'''
'''Subfield $u – Uniform Resource Identifier and Subfield and Subfield $v – Source of information'''
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>
</div>
<li type="a">use $v if the information/source is not cited in a 670</li>
<li type="a">use of $u is optional, and should always be preceded by $v</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.
'''Subfield $v – Source of information'''
'''Subfield instructions'''
Follow the same basic citation principles when recording data in subfield $v (Source of information) of fields 046, 368, 370-378, and 381 that currently apply to field 670 subfield $a (Source citation).
Supply specific citation information (page number, sub-page of website) in subfield $v if, in the cataloger's judgment, this greater specificity is needed to find the information within the source cited.
If the information in fields 046, 368, 370-378, and 381 is in the same form as found in the source, there is no need to cite usage information. If the information recorded in those fields is in a different form from that in the source, use 670 $b (Information found).
'''For tangibles sources:'''
If the information was derived from a tangible source (e.g., a print book, removable digital media) subfield $v should contain sufficient information for a cataloger to find the item cited in a catalog
or bibliographic database. This can usually be limited to title proper and imprint or date. If that combination is not unique, the title citation may be preceded by the creator's name
'''For online resources:'''
Provide information sufficient to find the resource via a search engine. Include either title and publication date (if it is a formally-published resource, such as an e-book) or a suitable description of the
document and date accessed (for a less formal resource). Optionally include subfield $u.
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 0# $a M. Alicia $q (Mary Alicia), $c Sister, S.C.N.
100 1# $a Lazzarini, Sérgio G.
372 ## $a Relations industrielles $2 rvm $v Lazzarini, Sergio G. CV-English, consulté le 22 février 2012 $u http ://www.sergiolazzarini.insper.edu.br/indexelazza.html
670 ## $a Capitalismo de laçeos, 2011 : $b page de titre (Sérgio G. Lazzarini)
</div>
[2023-10-05]<!--(2023-10-03)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#046_Special_Coded_Dates|''Supplement'' <big>⮞</big>]]
= 050 Library of Congress Call Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#050_Library_of_Congress_Call_Number|''Supplement'' <big>⮞</big>]]
= 053 LC classification number <span style="color:red>[New]</span>=
This field is used in personal name authority records to record LC classification numbers for individual literary authors, including authors of children's literature. It may also be used '''exceptionally'' in personal and corporate name authority records to record biography numbers in the ML410-429 range of the LC classification when the choice of index or cutter is not obvious. Field 053 must always include a $5 subfield.
'''Subfield $a – Content type term'''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
053 #4 $a PZ7.T378 $c Littérature de jeunesse anglaise $5 [Institution MARC Code]
100 1# $a Thomson, Sarah L. <br>
053 #4 $a ML410.S716 $c Biographie $5 [Institution MARC Code]
100 1# $a Chostakovitch, Dmitri Dmitrievitch, $d 1906-1975
</div>
Class PS8000 numbers should not be recorded in field 053. For the use of PS8000 numbers in name authority records, see section 065 of this Manual. An authority record for a Canadian literary author may contain both a 053 and a 065 field.
''Examples:''
[2023-10-05]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#053_LC_Classification_Number|''Supplement'' <big>⮞</big>]]
= 055 Library and Archives Canada Call Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#055_Library_and_Archives_Canada_Call_Number|''Supplement'' <big>⮞</big>]]
<br><br>
= 065 Other Classification Number <span style="color:red>[New]</span>=
Field 065 is used to record PS8000 class numbers. Field 065 must always include a subfield $2 and a subfield $5.
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
065 ## $a PS8576.U57 $2 fcps $5 [MARC code of institution]
<br><br>
</div>
'''Subfield $2 – Number source'''
In subfield $2, record " fcps " to indicate that the number comes from the PS8000 class.
[2023-10-05]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#065_Other_Classification_Number|''Supplement'' <big>⮞</big>]]
= 080 Universal Decimal Classification Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#080_Universal_Decimal_Classification_Number|''Supplement'' <big>⮞</big>]]
= 082 Dewey Decimal Call Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#082_Dewey_Decimal_Call_Number|''Supplement'' <big>⮞</big>]]
= 083 Dewey Decimal Classification Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#083_Dewey_Decimal_Classification_Number|''Supplement'' <big>⮞</big>]]
</div>
= 086 Government Document Call Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#086_Government_Document_Call_Number|''Supplement'' <big>⮞</big>]]
= 087 Government Document Classification Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#087_Government_Document_Classification_Number|''Supplement'' <big>⮞</big>]]
<br><br>
= 1XX Headings - General Information =
'''General'''
PFAN catalogers should consult the [https://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html PCC Post RDA Test Guidelines] for instructions on using RDA and/or AACR2 in new and existing authority records.
When modifying an authority record for any reason, delete a final mark of punctuation in the 1XX field unless it is a part of the data (e.g., a period in an abbreviation) or is called for by the cataloging
instructions (e.g., a parenthetical qualifier).
Note: in order to minimize the impact of database maintenance with associated bibliographic records and/or related authority records, catalogers are urged to refrain from making unnecessary changes to 1XXs.
<!--'''SARs'''
</div>
PFAN series practice: Transcription of the series statement is mandatory if applicable. Searching for series authority records, tracing the series, and the creation and maintenance of series authority records are optional.
For the title proper of a multipart monograph, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-2781.html/view RDA 2.1.2.3].
''Choosing a monographic series title proper:''
''(La première 368 renferme un terme provenant d'un vocabulaire contrôlé mais pas la seconde)'' </div>
#If the resource has more than one form of series title, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7766.html/view RDA 2.12.2.2] and [http://original.rdatoolkit.org/rdachp2-fr_rda2-7759.html/view 2.12.2.5].
#
#If the resource has the series title in more than one language or script on the same source, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7759.html/view RDA 2.12.2.4].
#
#If the resource has series title pages in more than one language and or script, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7759.html/view RDA 2.2.3.1].
#
#Consider spacing and changes in typography when determining where the series title begins and ends. Also consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-7778.html/view RDA 2.12.2.3].
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
''Establishing an SAR access point:''
<ol><li>Determine choice of authorized access point based on [http://original.rdatoolkit.org/rdachp6-fr_rda6-6412.html/view RDA 6.27] and its associated LAC-BAnQ PS.</li>
<li>Exclude from the authorized access point the following information included in the series statement in the bibliographic record for the component part:
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#368_Other_Attributes_of_Person_or_Corporate_Body|''Supplement'' <big>⮞</big>]]
<ol>
<li type="a">initial article in subfields $a, $t, $n, and $p;</li>
<li type="a">other title information;</li>
= 370 Associated place =
<li type="a">statement of responsibility;</li>
<li type="a">parallel title(s);</li>
<li type="a">ISSN;</li>
<li type="a">numeric/chronological designations.</li>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
</ol>
</li>
<div style="font-family:sans-serif; margin-left:85px;">
<div style="font-family:sans-serif">Authorized access point recorded in 370:</div>
<li>Add a parenthetical qualifier(s) if appropriate according to the guidelines in LAC-BAnQ PS 6.27.1.9.</li>
</ol>
For instructions on converting an existing NAR to an SAR, see Should an SAR be made? in the Introduction of [https://www.loc.gov/catdir/cpso/dcmz1.pdf DCM Z1].-->
<div style="font-family:sans-serif">
[2021-11-03]<!--(2021-10-27)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
= 100 Heading - Personal Name =
''(Abbreviation for the larger place per [http://original.rdatoolkit.org/rdaappb-fr_rdab-388.html RDA B.11])''</div>
</div><br>
'''''Authorized access points for families'''
'''''General'''
Use first indicator value “3” in field 100 when creating an NAR for a family. See in this Manual, [[PFAN_-_Name_Authority_Manual#667_Nonpublic_general_note|667]] section, [[PFAN_-_Name_Authority_Manual#NARs_and_subject_usage|NARs and subject usage]], for subject usage instructions in NARs for families.
'''Subfield instructions'''
There is no prescribed MARC order for the subfields beyond subfield $a in the X00 fields. When providing multiple additions to the name generally follow these guidelines:
# Additions to the name are contained in a single set of parentheses separated by colons.
#
# The term for the type of family is added after the name and is contained in subfield $a.
#
# Subfield $d (date) follows the term for the type of family.
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
#
# Subfield $c is used for place associated with family and follows the date.
#
# Subfield $g is used for prominent member of family. Give authorized access point for the person as found in the 1XX of the NAR without any internal subfield coding.
#
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 3# $a Jones (Famille : $d 1801-1950 : $c New York, N.Y. : $g Jones, Samuel, 1830-1899)
</div>
'''''Authorized access points for persons'''''
'''General'''
''(For a person born in the city of Calcutta before its name changed to Kolkata; cataloger has chosen to record the form of name that applied at the time the person was born)''</div><br>
Use first indicator value “0” or “1” in field 100 when creating an NAR for a person.
'''Subfield instructions'''
There is no prescribed MARC order for the subfields beyond subfield $a in the X00 fields. [http://original.rdatoolkit.org/rdachp9-fr_rda9-2234.html/view RDA 9.2.2.9.5] provides guidance for the placement of words indicating relationship (e.g., Jr.) and MARC defines subfield $q as “Forme développée du nom de personne.” When providing multiple additions to the name generally follow these guidelines:
When determining when to create a name authority record for a geographic name, consult the “Name Authority Records (NARs)” section of [https://www.loc.gov/catdir/cpso/dcmz1.pdf DCM Z1], Introduction.
1) Subfield $d (date) should always be the last element in a 100 string unless the term (Esprit) is being added to the name. Add $c (Esprit) as the last element in a 100 string.
<ol>'''Example:'''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 0# $a Élisabeth $b Ire, $c reine d'Angleterre, $d 1533-1603 $c (Esprit)
</div></ol>
2) Generally add subfield $c before subfield $q when also adding words, numerals, etc. indicating relationship. (See [http://original.rdatoolkit.org/rdachp9-fr_rda9-2234.html/view RDA 9.2.2.9.5] for treatment of Portuguese names)
<ol>''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a McCauley, Robert H., $c Jr. $q (Robert Henry), $d 1913-1979
</div>
BUT
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 0# $a M. Alicia $q (Mary Alicia), $c Sister, S.C.N.
</div></ol>
3) For exceptional situations, such as when subfield $a contains only a surname or only a forename or the name includes a prefix, etc. consult [http://original.rdatoolkit.org/lcpschp1_lcps1-224.html LC-PCC PS 1.7.1].
[2021-02-19]<!--(2020-12-08)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#100_Heading-Personal_Name|''Supplement'' <big>⮞</big>]]
<div style="font-family:sans-serif; margin-left:85px;">
''(Martinique is an overseas department of France)''</div></div><br>
= 336 Content Type =
''Examples:''
'''General'''
''(For a person associated with Great Britain who has strong ties to Wales; cataloger has chosen to record both places)''</div><br>
Field 336 may only be used in NARs and SARs for expressions. 336 is always accompanied by a subfield $2.
''Example :''
'''Subfield $2 – Source of term'''
In subfield $2 give “rdacontent/fre.”
'''Subfield $s – Start period and Subfield $t – End period'''
'''Subfield $a – Content type term'''
Use terms from [http://original.rdatoolkit.org/rdachp6-fr_rda6-3421.html/view RDA 6.9.1.3]. The list of terms is also available in the [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].
'''Subfield $b – Content type code'''
If giving subfield $b instead of/or in addition to subfield $a, use the code from the MARC format [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].
[2021-02-15]<!--(2021-02-15)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#336_Content_Type|''Supplement'' <big>⮞</big>]]
[2022-01-24]<!--(2022-01-22)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#370_Associated_Place|''Supplement'' <big>⮞</big>]]
= 371 Address =
= 368 Other attributes of person or corporate body =
'''General'''
'''General'''
Prefer controlled vocabulary for terms in subfields $a, $b, and $c, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a, $b and $c. When terms in subfields $a and $b do not come from a controlled vocabulary, use a singular form.
'''Repeatability'''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
110 2# $a Freer Gallery of Art
'''Subfield $m – Electronic mail address'''
368 ## $a Musées d'art $2 rvm
<br><br>
151 ## $a France
368 ## $b États $2 ram
<br><br>
151 ## $a Garwolin (Pologne : Powiat)
368 ## $b Powiat
<br><br>
100 0# $a Jeanne, $c d'Arc, sainte, $d 1412-1431
368 ## $c Saints $2 rvmgd
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#371_Address|''Supplement'' <big>⮞</big>]]
<br><br>
100 0# $a Palamède $c (Personnage du cycle arthurien)
368 ## $c Personnage du cycle arthurien
<br><br>
110 2# $a Church of Christ (Rigdonites)
368 ## $c Rigdonites
<br><br>
110 2# $a Indiana (Cuirassé : BB-50)
368 ## $a Cuirassés $2 rvm
368 ## $c BB-50
</div>
</div>
Do not record professions or occupations in subfield $c (Other designation). Profession or occupation may be recorded in field [[PFAN_-_Name_Authority_Manual#374_Occupation|374]].
Record titles of royalty, nobility or religious rank ([http://original.rdatoolkit.org/rdachp9-fr_rda9-4646.html RDA 9.4.1.4–9.4.1.8]) in subfield $d in the form used in the authorized or variant access points.
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 0# $a Alexandre $b VI, $c pape, $d 1431-1503
368 ## $d pape $s 1492 $t 1503
<br><br>
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall
100 0# $a Jane Seymour, $c reine, épouse d'Henri VIII, roi d'Angleterre, $d 1509?-1537
best practice: repeat the field when needed for clarity.
368 ## $d reine, épouse d'Henri VIII, roi d'Angleterre
<br><br>
100 0# $a Jeanne Marie, $c sœur, $d 1926-2013
368 ## $d sœur
<br><br>
100 1# $a Walsh, Joseph-Alexis, $c vicomte, $d 1782-1860
368 ## $d vicomte
</div>
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
''Example:''
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
368 ## $c Saints $2 rvmgd
368 ## $d métropolite de Rostov
<div style="font-family:sans-serif; margin-left:85px;">
<div style="font-family:sans-serif; margin-left:85px;">
(''372 fields with a term from RVM and a non-controlled vocabulary term'')</div>
''(La première 368 renferme un terme provenant d'un vocabulaire contrôlé mais pas la seconde)'' </div>
</div>
</div>
'''Subfield $s – Start period and Subfield $t – End period'''
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
Follow the instructions given in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
Follow the instructions given in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field
[2021-03-09]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#368_Other_Attributes_of_Person_or_Corporate_Body|''Supplement'' <big>⮞</big>]]
= 370 Associated place =
'''General'''
'''General'''
For jurisdictions or other place names with authority records in Canadiana or, failing that, the form found in the RVM, recording the source in subfield $2. The form of place name in the 370 field may differ from the form of place name added to a preferred name of place or an access point per RDA and LAC-BAnQ PS instructions.
''Examples:''
''Examples:''
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif;">Corporate name in Canadiana:</div>
<div style="font-family:sans-serif">Geographic name in Canadiana :</div>
151 ## $a Washington (État)
<div style="font-family:sans-serif; margin-left:85px;">
''(Authorized access point for the place includes type of jurisdiction)''</div><br>
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
<div style="font-family:sans-serif">Authorized access point recorded in 370:</div>
370 ## $e Washington (État) $2 lacnaf
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
<div style="font-family:sans-serif;">Corporate name in Canadiana:</div>
Form of name as an addition in an access point:</div>
110 2# $a Childhood Lead Poisoning Prevention Program (Wash.)
<div style="font-family:sans-serif; margin-left:85px;">
''(Abbreviation for the place per [http://original.rdatoolkit.org/rdaappb-fr_rdab-388.html RDA B.11])''</div><br>
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
<div style="font-family:sans-serif">
Form of name as part of preferred name of a local place:</div>
</div>
151 ## $a Seattle (Wash.)
<div style="font-family:sans-serif; margin-left:85px;">
'''Repeatability:'''
''(Abbreviation for the larger place per [http://original.rdatoolkit.org/rdaappb-fr_rdab-388.html RDA B.11])''</div>
</div><br>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
Geographic name in Canadiana :</div>
151 ## $a Québec (Province)
<div style="font-family:sans-serif; margin-left:85px;">''(Authorized access point for the place includes an other designation)''</div>
<br>
<div style="font-family:sans-serif">
Authorized access point recorded in 370: </div>
370 ## $e Québec (Province) $2 lacnaf
<div style="font-family:sans-serif">
Form of name as an addition in an access point:</div>
<div style="font-family:sans-serif;">NAR with 373s with subfield $2 and dates:</div>
110 2# $a Parti libéral du Canada (Québec)
<div style="font-family:sans-serif">
Form of name as part of preferred name of a local place:</div>
151 ## $a Rimouski (Québec)
</div><br>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
Geographic name in Canadiana : </div>
151 ## $a Congo (République démocratique)
<div style="font-family:sans-serif; margin-left:85px;">''(Authorized access point for the place includes an other designation)''</div>
<br>
<div style="font-family:sans-serif">
Authorized access point recorded in 370:</div>
370 ## $c Congo (République démocratique) $2 lacnaf
<div style="font-family:sans-serif">
</div>
Form of name as an addition in an access point:</div>
110 2# $a Centre d'information et d'animation missionnaire (Congo)
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif; margin-left:85px;">''(Preferred name of place)''</div>
<div style="font-family:sans-serif;">NAR with 373s with different vocabulary sources:</div>
<br>
<div style="font-family:sans-serif">
Form of name as part of preferred name of a local place:</div>
151 ## $a Lubumbashi (Congo)
<div style="font-family:sans-serif; margin-left:85px;">''(Preferred name for the larger place)''</div>
<br>
<div style="font-family:sans-serif">
Authorized access point recorded in 370:</div>
370 ## $e Lubumbashi (Congo) $2 lacnaf
<div style="font-family:sans-serif">
</div>
Form of name as an addition in an access point:</div>
110 2# $a Institut Imara (Lubumbashi, Congo)
<div style="font-family:sans-serif; margin-left:85px;">''(Preferred name of local place modified per [http://original.rdatoolkit.org/rdachp16-fr_rda16-351.html RDA 16.2.2.4])''</div>
</div> <br>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
Geographic name in Canadiana :</div>
151 ## $a Ottawa (Ont.)
<div style="font-family:sans-serif; margin-left:85px;">''(Abbreviation for the larger place per [http://original.rdatoolkit.org/rdaappb-fr_rdab-388.html RDA B.11])''</div>
<br>
<div style="font-family:sans-serif">
Authorized access point recorded in 370:</div>
370 ## $g Ottawa (Ont.) $2 lacnaf
<span id="373$s$t"></span>
<div style="font-family:sans-serif">
Form of name as an addition in an access point:</div>
130 #0 $a Histoire et généalogie (Ottawa, Ont.)
<div style="font-family:sans-serif; margin-left:85px;">''(Preferred name of local place modified per [http://original.rdatoolkit.org/rdachp16-fr_rda16-351.html RDA 16.2.2.4])''</div>
</div><br>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
Other place name in Canadiana :</div>
110 2# $a Auschwitz (Camp de concentration)
<div style="font-family:sans-serif">
Authorized access point recorded in 370:</div>
370 ## $a Auschwitz (Camp de concentration) $2 lacnaf
</div><br>
If there is no authorized access point for the place in Canadiana or RVM, it is not necessary to create an NAR in order to code the 370 field. Record the place in the 370 field following RDA and the LAC-BAnQ PSs, including consulting appropriate sources and adding additional elements (e.g., type of jurisdiction) to break conflicts. Do not add a subfield $2 if no NAR is created.
<span style="color:red>If the name of the associated place has changed, the name of the place that applied in the time of the entity being established in the 1XX may optionally be recorded in place of, or in addition to, the current form of name. It is not necessary to follow subject cataloging policies to use the latest form of name only.</span>
<span style="color:red>''Examples:</span>''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]]
<span style="color:red><div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
370 ## $a Salisbury (Zimbabwe)$c Zimbabwe $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person born in the city of Calcutta before its name changed to Kolkata; cataloger has chosen to record the form of name that applied at the time the person was born)''</div><br>
= 374 Occupation =
370 ## $a Italie $e Milan (Italie) $2 lacnaf
'''General'''
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person residing in the city of Milan during the Renaissance, prior to the formation of the modern country of Italy; cataloger has chosen to record the current form of name for the country)''</div></div></span><br>
For non-jurisdictions, prefer names from an authorized vocabulary such as RVM and identify the source in subfield $2. If the name is not found in an authorized vocabulary, record it in field 370 without
vocabulary, use a singular form.
giving a subfield $2.
Pour déterminer quand créer une notice d'autorité pour un nom géographique, consulter la section « Name Authority Records (NARs) » dans l'introduction du manuel [https://www.loc.gov/catdir/cpso/dcmz1.pdf DCM Z1].
When determining when to create a name authority record for a geographic name, consult the “Name Authority Records (NARs)” section of [https://www.loc.gov/catdir/cpso/dcmz1.pdf DCM Z1], Introduction.
'''Repeatability:'''
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary
source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
'''Subfield $2 – Source of term'''
'''<span style="color:red>Subfield $c – Associated country</span>'''
<span style="color:red>Generally, do not use subfield $c to record places that are not sovereign entities. Such places may be recorded in subfield $f or other subfields as appropriate.</span>
''<span style="color:red>Example:</span>''
<span style="color:red><div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
370 ## $c France $f Martinique $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(Martinique is an overseas department of France)''</div></div><br>
However, if a sovereign entity has (or previously had) one or more constituent countries, any of the constituent countries associated with the 1XX may optionally be recorded in subfield $c in addition to, or instead of, the larger sovereign entity.
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
370 ## $c Grande-Bretagne $c Pays de Galles $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person associated with Great Britain who has strong ties to Wales; cataloger has chosen to record both places)''</div><br>
370 ## $c URSS $c Kirghizistan $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person associated with the Soviet Union, particularly the Kirghiz Soviet Socialist Republic; cataloger has chosen to record both places)''</div><br>
370 ## $c Aruba $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person associated with Aruba, a constituent country of the Netherlands; cataloger has chosen not to record the Netherlands)''</div><br>
370 ## $c Inde $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(For a person associated with India prior to its independence from Great Britain; cataloger has chosen not to record Great Britain)''</span></div></span></div><br>
Entity names of First Nations in Canada and Indian tribes recognized by the United States government as legal entities may be included in subfield $c.
''Example :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
370 ## $c Première nation de Natashkuan $2 lacnaf
</div></span>
'''Subfield $s – Start period and Subfield $t – End period'''
'''PFAN'''
Follow the instructions given in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions given in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
<!--'''SARs'''
'''Repeatability:'''
''PFAN series practice:'' Record the place of origin of the work in field 370, unless it is merely a place of publication or other place associated with a manifestation (use field 643, when appropriate, for the latter). Although the “place of origin” of a serial work may be the same as the place of publication of the component part for which the SAR (or serial bibliographic record) was created, use judgment in distinguishing between place of origin of the work and a place of publication not actually related to the work itself.
-->
[2022-01-24]<!--(2022-01-22)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#370_Associated_Place|''Supplement'' <big>⮞</big>]]
= 371 Address =
''Example:''
'''General'''
Best practice:
* Supply based on cataloger's judgment, if the information is readily available and not already being recorded in field 370 subfield $e (Place of residence/headquarters).
*
* In cases where subfield $a is not recorded, include at a minimum subfield $m (Electronic mail address) or subfield $b (City).
*
* Do not record physical addresses for living people.
*
* Catalogers are not required to maintain address information when updating a record that contains an address.
*
'''Repeatability'''
Record multiple addresses, with or without ranges of dates, in separate occurrences of field 371.
'''Subfield $2 – Source of term'''
'''Subfield $m – Electronic mail address'''
Subfield $m should contain only an e-mail address. Do not add an internet address for the 1XX in this field.
'''Subfield $s – Start period and Subfield $t – End period'''
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#371_Address|''Supplement'' <big>⮞</big>]]
= 372 Field of activity =
'''General'''
'''General'''
Prefer controlled vocabulary, such as RVMGD or RVM, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled
Prefer controlled vocabulary, such as RVM, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a
If using an RVM heading string for field of activity, replace the subfield coding for the subdivision(s) with two hyphens and close up the spaces between the main heading and subdivision(s).
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
372 ## $a Japon--Histoire $2 rvm
</div>
If using an entity from Canadiana for field of activity, remove any subfield coding not authorized for use in the 372 field.
''Example:''
Authorized access point in Canadiana:
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a Bible. $p Nouveau Testament
</div>
Field of activity in 372:
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
372## $a Bible. Nouveau Testament $2 lacnaf
</div>
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall
best practice: repeat the field when needed for clarity.
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
372 ## $a Poésie $2 rvm
372 ## $a Brasserie artisanale
<div style="font-family:sans-serif; margin-left:85px;">
(''372 fields with a term from RVM and a non-controlled vocabulary term'')</div>
</div>
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#376_Family_Information|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#372_Field_of_Activity|''Supplement'' <big>⮞</big>]]
= 373 Associated group =
'''General'''
'''General'''
Prefer language codes over language terms, using codes from the Code List for Languages in MARC21. Use subfield $l (Language term) only to provide information not available in the [https://loc.gov/marc/languages/language_code.html MARC Code List for Languages]. Encode multiple languages for a person or corporate body only if more than one language is used for publication, communication, etc.
Prefer a controlled vocabulary, such as the Canadiana or LC/NACO Authority File, recording the source in subfield $2. Subfield coding for subordinate bodies is not used in the 373 field.
<span style="color:red>If the name of an associated group has changed, record the group name(s) that applied at the time of the entity being established in the 1XX.</span>
''Examples:''
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif;">Corporate name in Canadiana:</div>
110 2# $a Canadiens de Montréal (Équipe de hockey)
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
<div style="font-family:sans-serif; margin-left:0px;text-indent:0px">
373 ## $a Canadiens de Montréal (Équipe de hockey) $2 lacnaf
</div>
</div>
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif;">Corporate name in Canadiana:</div>
110 1# $a Québec (Province). $b Conseil supérieur de l'éducation. $b Direction de la recherche
= 378 Fuller form of personal name =
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
373 ## $a Québec (Province). Conseil supérieur de l'éducation. Direction de la recherche $2 lacnaf
</div>
'''General'''
'''Repeatability:'''
In choosing between repeating a field and repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples:''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif;">NAR with 373s with subfield $2 and dates:</div>
373 ## $a Toronto Raptors (Équipe de basketball) $2 lacnaf $s 2006 $t 2009
373 ## $a Vancouver Grizzlies (Équipe de basketball) $2 lacnaf $s 2009 $t 2011
373 ## $a Toronto Raptors (Équipe de basketball) $2 lacnaf $s 2012 $t 2014
</div>
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<br><br>
<div style="font-family:sans-serif;">NAR with 373s with different vocabulary sources:</div>
373 ## $a Gendarmerie royale du Canada. Liaison Branch $2 lacnaf
373 ## $a Buffalo State College $2 naf
</div>
</div>
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the Information'''
<span id="373$s$t"></span>
'''Subfield $s – Start period and Subfield $t – End period'''
Best practice: Although the MARC format does not specify a form of date in these subfields, the following practice is recommended for consistency. Input dates using the Gregorian calendar in the form yyyy. If more specific dates are necessary, consider recording them in another field (e.g., 670, 678). It is
not necessary to reformulate dates in existing NARs to conform to this practice.
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2023-06-21]<!--(2023-06-21)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]]
= 374 Occupation =
'''General'''
'''General'''
Prefer a controlled vocabulary, such as RVM or RVMGF, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled vocabulary, use a singular form.
Prefer a controlled vocabulary, such as the RVMGD or RVM, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled
vocabulary, use a singular form.
See LAC-BAnQ PS 9.16.1.3 for instructions on recording profession or occupation as an element. See LAC-BAnQ PS 9.19.1.6 for instructions using a profession or occupation term in an access point.
'''Repeatability:'''
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, repeat the field. Overall best practice: repeat the field when needed for clarity.
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples:''
'''Subfield $2 – Source of term'''
Codes from either the [http://www.loc.gov/standards/sourcelist/occupation.html/view Occupation Term Source Codes] or the [http://www.loc.gov/standards/sourcelist/subject.html/view Subject Source Codes] lists may be recorded in subfield $2 for the 374 field.
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
</div>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#374_Occupation|''Supplement'' <big>⮞</big>]]
= 375 Gender =
'''PFAN'''
[2021-11-03]<!--(2021-11-01)-->
<span style="color:red>Do not use this field in new authority records. Whenever an existing record must be changed for any reason, delete any occurrence of field 375.</span>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#380_Form_of_Work|''Supplement'' <big>⮞</big>]]
[2023-10-20]<!--(2023-10-20)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement'' <big>⮞</big>]]
= 381 Other distinguishing characteristics of work or expression =
= 376 Family information =
'''General'''
'''General'''
Prefer controlled vocabulary, such as RVMGD or RVM, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled
vocabulary, use a singular form.
''Examples:''
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
'''Subfield $b – Name of prominent member'''
''(Franklin number recorded as other distinguishing characteristic of work)''</div> <br>
When giving the name of the prominent member of the family in 376 subfield $b, give the form for the person as found in subfield $g of the 100 field of the NAR for the family. Do not include any internal subfield coding in subfield $b.
'''Subfield $s – Start''' period and Subfield $t – End period
''(Version recorded as other distinguishing characteristic of expression)''</div> <br>
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#376_Family_Information|''Supplement'' <big>⮞</big>]]
= 377 Associated language =
'''General'''
''(Corporate body recorded as other distinguishing characteristic of expression)''</div><br>
Prefer language codes over language terms, using codes from the Code List for Languages in MARC21. Use subfield $l (Language term) only to provide information not available in the [https://loc.gov/marc/languages/language_code.html MARC Code List for Languages]. Encode multiple languages for a person or corporate body only if more than one language is used for publication, communication, etc.
'''Subfield $2 – Source of the code'''
Subfield $2 is not required when the MARC Code List for Languages is used as the language source code (second indicator value “#”). PFAN institutions may supply an additional 377 field from another language code list by using second indicator value “7,” with subfield $2 containing a code for a language source list taken from the list in [http://www.loc.gov/standards/sourcelist/language.html/view Language Code and Term Source Codes]
''Example:''
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
377 ## $a myn
377 #7 $a acr $2 iso639-3
<div style="font-family:sans-serif; margin-left:0px;text-indent:0px">
''(ISO 639-3 code for Achi (acr); assigned a collective code (myn) for Mayan languages in the MARC Code List for Languages)''</div>
<div style="font-family:sans-serif; margin-left:85px;">
''(Places used as other distinguishing characteristic of a legal work; recorded in 370 and 381 fields)''</div>
</div>
</div>
[2021-02-22]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#377_Associated_Language|''Supplement'' <big>⮞</big>]]
= 378 Fuller form of personal name =
'''Repeatability:'''
'''General'''
Best practice: Encode the fuller form of name in the 378 field when this information is readily available, even if the same information is already present in the 100 field.
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Lennon, John, $d 1940-1980
378 ## $q John Winston
<br><br>
100 1# $a Eliot, T. S. $q (Thomas Stearns), $d 1888-1965
378 ## $q Thomas Stearns
<br><br>
100 1# $a Guiles, Kay D.
378 ## $q Kay Dean
</div>
'''Repeatability:'''
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the Information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-02-19)-->
[2021-02-22]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#382_Medium_of_Performance|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#378_Fuller_Form_of_Personal_Name|''Supplement'' <big>⮞</big>]]
= 383 Numeric designation of musical work =
= 380 Form of work =
'''General'''
'''General'''
Prefer a controlled vocabulary, such as RVM or RVMGF, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled vocabulary, use a singular form.
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, repeat the field. Overall best practice: repeat the field when needed for clarity.
'''General'''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Picasso, Pablo, $d 1881-1973. $t Gertrude Stein
380 ## $a Portraits $a Peintures $2 rvmgf
100 1# $a Shakespeare, William, $d 1564-1616. $t Hamlet
380 ## $a Tragédies $2 rvmgf
380 ## $a Tragédie $2 rvm
</div>
''Examples :''
<!--'''SARs'''
For instructions on recording form of work as an element in a work-level series authority record, see LAC-BAnQ PS 6.3.1.3.
-->
[2021-11-03]<!--(2021-11-01)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#380_Form_of_Work|''Supplement'' <big>⮞</big>]]
= 381 Other distinguishing characteristics of work or expression =
'''General'''
''(Uncontrolled term)''</div>
This field is used to record the RDA elements other distinguishing characteristic of work ([http://original.rdatoolkit.org/rdachp6-fr_rda6-3204.html RDA 6.6]) and other distinguishing characteristic of expression ([http://original.rdatoolkit.org/rdachp6-fr_rda6-3584.html RDA 6.12]). Other characteristics of expressions that are unique to musical works (see [http://original.rdatoolkit.org/rdachp6-fr_rda6-4857.html RDA 6.18.1.4-6.18.1.6]) may also be recorded in the 381 field.
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Dickinson, Emily, $d 1830-1886. $t Because I could not stop for Death
381 ## $a Fr. 712
<div style="font-family:sans-serif; margin-left:60px;">
<div style="font-family:sans-serif; margin-left:85px;">
''(Terms from different controlled vocabularies)''</div><br>
''(Franklin number recorded as other distinguishing characteristic of work)''</div> <br>
130 #0 $a Bible. $p Psaumes. $l Anglais. $s New American. $f 1991
381 ## $a New American
<div style="font-family:sans-serif; margin-left:60px;">
<div style="font-family:sans-serif; margin-left:85px;">
''(Uncontrolled term and term from a controlled vocabulary)''</div><br>
''(Version recorded as other distinguishing characteristic of expression)''</div> <br>
100 1# $a Bach, Johann Sebastian, $d 1685-1750. $t Chorals. $s Partitions de chant. $l Anglais
<div style="font-family:sans-serif;">''or''</div>
381 ## $a Partitions de chant $2 rvmgf
<div style="font-family:sans-serif; margin-left:85px;">
(''Other distinguishing characteristic of expression of musical work'')</div>
</div>
</div>
'''Subfield $m – Demographic group term and Subfield $n – Demographic group code'''
Some terms recorded for other distinguishing characteristic of work or expression may be appropriate to record in field 381 and another MARC field for which there is no corresponding RDA element.
Do not use these subfields, but do not remove them from existing records if they are correctly coded.
For example, a corporate body (such as a publisher) used as an other distinguishing characteristic of work or expression could be recorded in either the 373 field (associated group), the 381 field or both.
Note: Subfield coding for subordinate bodies is not used in the 381 field.
[2022-10-14]<!--(2022-10-14)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#385_Audience_Characteristics|''Supplement'' <big>⮞</big>]]
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
= 386 Creator/contributor characteristics =
130 #0 $a Bible. $l Français. $s Bayard. $f 2001
'''General'''
381 ## $a Bayard éditions $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.
''(Corporate body recorded as other distinguishing characteristic of expression)''</div><br>
[2021-02-21]<!--(2021-02-19)-->
130 #0 $a Journal of adult education (University of Zambia. Centre for Continuing Education)
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]
373 ## $a University of Zambia. Centre for Continuing Education $2 naf
= 388 Time Period of Creation =
381 ## $a University of Zambia. Centre for Continuing Education $2 naf
<div style="font-family:sans-serif; margin-left:85px;">
'''General'''
''(Corporate body recorded as associated group and other distinguishing characteristic of work)''</div>
</div>
PFAN catalogers may use this field to record the time period of creation or origin of a work or expression. The name of the time period may specify or imply a place for which the time period is relevant. It may also specify the name of an event.
RDA has no specific element for places associated with expressions, but field 370 subfield $f (Other associated place) and subfield $g (Place of origin of work or expression) may be used in authority records for expressions. Some places associated with works or expressions would be considered other distinguishing characteristic of work or expression in RDA and could be recorded in the 370 field, the 381 field, or both.
Prefer a controlled vocabulary, such as RVM or RVMFAST, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a.
''Examples:''
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Harlem Renaissance $2 rvm
130 #0 $a Ley de Enjuiciamiento Criminal para las Islas de Cuba y Puerto Rico (Cuba; Porto Rico)
388 1# $a Dynastie des Han (Chine) $2 rvmfast
370 ## $f Cuba $f Porto Rico $2 lacnaf
388 1# $a <span style="color:red>Rébellion des Patriotes (Canada : 1837-1838) $2 rvmfast</span>
381 ## $a Cuba $a Porto Rico $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
</div>
''(Places used as other distinguishing characteristic of a legal work; recorded in 370 and 381 fields)''</div>
</div>
If using an RVM subject heading string, replace the subfield coding for the subdivision(s) with two hyphens and close up the spaces between the main heading and subdivision(s).
Record the RDA element place of origin of work ([http://original.rdatoolkit.org/rdachp6-fr_rda6-3163.html RDA 6.6]) in a 370 field (see Manual, [[PFAN_-_Name_Authority_Manual#370_Associated_place|370]] section).
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
When other distinguishing characteristic of work or other distinguishing characteristic of expression has been used in an authorized access point and is also being recorded as an element in a 3XX
388 1# $a Crises économiques--1929 $2 rvm
field, use the 381 field to record the other distinguishing characteristic. Optionally, also record the same information in any other appropriate 3XX field.
</div>
'''Repeatability:'''
For compilations, the field may be used to record the time period of creation or origin of the works/expressions contained within the compilation, considered collectively (using first indicator value “1”). It may also be used to record the time period of creation or origin of the compilation itself (using first indicator value “2”).
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the
''Examples:''
vocabulary source differs, or if another associated element differs, repeat the field. Overall best practice: repeat the field when needed for clarity.
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Renaissance $2 rvm
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
388 2# $a Dix-neuvième siècle $2 rvm
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#381_Other_Distinguishing_Characteristics_of_Work_or_Expression|''Supplement'' <big>⮞</big>]]
= 382 Medium of performance =
'''General'''
Record the medium of performance using thesaurus terms from "Moyens d'exécution en musique du RVM (RVMMEM)". Record the medium of performance by applying the instructions at [http://original.rdatoolkit.org/rdachp6-fr_rda6-4362.html RDA 6.15.1.3–6.15.1.6], the associated LAC-BAnQ PSs. ''Note:'' The 382 field may also be used in authority records for expressions.
'''Repeatability:'''
If the vocabulary source differs, repeat the field. If considered important for identification and access, provide an additional 382 that does not apply these guidelines.
[2021-03-10]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#382_Medium_of_Performance|''Supplement'' <big>⮞</big>]]
= 383 Numeric designation of musical work =
'''General'''
Best practice: Encode when available. Create separate 383 fields for different numbering schemes associated with a single work.
[2021-02-22]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#383_Numeric_Designation_of_Musical_Work|''Supplement'' <big>⮞</big>]]
= 384 Key =
'''General'''
Best practice: Encode when available for works. In case of doubt, do not encode. Do not encode for expressions.
[2021-02-22]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#384_Key|''Supplement'' <big>⮞</big>]]
= 385 Audience characteristics =
'''General'''
PFAN catalogers may use this field to record the intended audience of a work or expression.
Prefer a controlled vocabulary, such as RVMGD or RVM, recording the source code in subfield $2. For consistency, capitalize the first term in each subfield $a. Record uncontrolled terms in the plural form. Follow the guidelines for coding and assignment of terms in the ''Library of Congress Demographic Group Terms Manual'', available at [https://www.loc.gov/aba/publications/FreeLCDGT/freelcdgt.html https://www.loc.gov/aba/publications/FreeLCDGT/freelcdgt.html]. In particular, consult instruction sheet L 480, Assignment of Terms: Audience Characteristics, available at [https://www.loc.gov/aba/publications/FreeLCDGT/L480.pdf https://www.loc.gov/aba/publications/FreeLCDGT/L480.pdf].
''Examples :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
385 ## $a Préadolescents $2 rvmgd
385 ## $a Familles de militaires $2 rvmt
385 ## $a Élève-maître $2 unescot
385 ## $a Acheteurs potentiels de logement
<div style="font-family:sans-serif; margin-left:60px;">
''(Uncontrolled term)''</div>
</div>
'''Repeatability:'''
In choosing between repeating a field and repeating subfield $a: If the vocabulary source differs or if some terms come from a controlled vocabulary and others are uncontrolled, repeat the field. Otherwise, if the only addition to an existing field is an additional term from the same vocabulary, either repeat subfield $a or repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
385 ## $a Anglophones $2 rvmgd
385 ## $a Commerçants $2 rvm
<div style="font-family:sans-serif; margin-left:60px;">
''(Terms from different controlled vocabularies)''</div><br>
385 ## $a Créolophones à base française
385 ## $a Personnel de l'industrie de la construction $2 rvmgd
<div style="font-family:sans-serif; margin-left:60px;">
''(Uncontrolled term and term from a controlled vocabulary)''</div><br>
385 ## $a Adolescents $a Enfants de divorcés $2 rvmgd
<div style="font-family:sans-serif;">''or''</div>
385 ## $a Adolescents $2 rvmgd
385 ## $a Enfants de divorcés $2 rvmgd
</div>
'''Subfield $m – Demographic group term and Subfield $n – Demographic group code'''
Do not use these subfields, but do not remove them from existing records if they are correctly coded.
[2022-10-14]<!--(2022-10-14)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#385_Audience_Characteristics|''Supplement'' <big>⮞</big>]]
= 386 Creator/contributor characteristics <span style="color:red>[New]</span>=
'''General'''
PFAN catalogers may use this field to record demographic characteristics of one or more creators or contributors associated with a work or expression, in particular for characteristics common to a group of creators or contributors associated with a work or expression. The field will most commonly be used in authority records for collection aggregates embodying two or more expressions of two or more independent works by different agents, and for individual works named by title alone (e.g., works of unknown authorship; monographic series).
Prefer a controlled vocabulary, such as RVMGD or RVM, recording the source code in subfield $2. For consistency, capitalize the first term in each subfield $a. Record uncontrolled terms in the plural form. Follow the guidelines for coding and assignment of terms in the draft Library of Congress Demographic Group Terms Manual, available at [https://www.loc.gov/aba/publications/FreeLCDGT/freelcdgt.html https://www.loc.gov/aba/publications/FreeLCDGT/freelcdgt.html]. In particular, consult instruction sheet L 485, Assignment of Terms: Creator and Contributor Characteristics, available at [https://www.loc.gov/aba/publications/FreeLCDGT/L485.pdf https://www.loc.gov/aba/publications/FreeLCDGT/L485.pdf].
''Examples :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a Pièces pour piano composées par des enfants
386 ## $a Enfants $2 rvmgd
<br><br>
130 #0 $a Beowulf
386 ## $a Anglo-Saxons $2 rvm
<br><br>
130 #0 $a De l'infidélité
386 ## $a Taiwanais $2 rvmgd
670 ## $a De l'infidélité, 2008 : $b page de titre (anthologie de la poésie contemporaine de Taiwan)
<br><br>
130 #0 $a Spoke (Birstall, Kirklees, Angleterre)
386 ## $a personne queer $2 gsdg/fre
670 ## $a Spoke : new queer voices, 2014 : $b page de titre ("poetry, prose, drama, maps & comics")
<br><br>
130 #0 $a Parcours ombragés
386 ## $a Bas-Laurentiens
670 ## $a Parcours ombragés, 2020 : $b couverture (nouvelles rédigées par des aînés du Bas-Saint-Laurent)<br>
(Uncontrolled demographic term)
</div>
While this field will be used primarily for aggregated works and for individual works named by title alone, there are situations when it will be appropriate for an individual work by one or more named creators. For example, for a musical work composed during childhood or adolescence, it would not be appropriate to record “Enfants” or “Adolescents” as a characteristic in the composer’s authority record. Instead, demographic characteristics applicable to only some of a creator’s works should be recorded in the authority records for those works
''Example :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Greenberg, Jay, $d 1991- $t Symphonies, $n no 5
386 ## $a Adolescents $a Garçons $2 rvmgd<br>
(Work composed 2003-2005, completed when the composer was 14 years old)
</div>
'''Repeatability:'''
In choosing between repeating a field and repeating subfield $a:
If the vocabulary source differs or if some terms come from a controlled vocabulary and others are uncontrolled, repeat the field. Otherwise, if the only addition to an existing field is an additional term from the same vocabulary, either repeat subfield $a or repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a Latin American women writers
386 ## $a Latino-Américains $2 rvm
386 ## $a Femmes $2 rvmgd<br>
(Terms from different controlled vocabularies)
<br><br>
130 #0 $a Cowboy poetry from Utah
386 ## $a Cowboys $a Utahains $2 rvmgd
ou
386 ## $a Cowboys $2 rvmgd
386 ## $a Utahains $2rvmgd
<br><br>
130 #0 $a Faux pas
386 ## $a Gatinois
386 ## $a Élèves du secondaire $a Adolescents $a Québécois $2 rvmgd
ou
386 ## $a Gatinois
386 ## $a Élèves du secondaire $2 rvmgd
386 ## $a Adolescents $2 rvmgd
386 ## $a Québécois $2 rvmgd
670 ## $a Faux pas, 2014 $b page 4 de la couverture (Textes écrits par les élèves de 5e secondaire du Collège Saint-Alexandre à Gatineau)<br>
(Uncontrolled term and terms from one controlled vocabulary)
</div>
'''Subfield $i – Relationship information'''
Optionally, use subfield $i to record a term designating the nature of the relationship between the demographic groups recorded in the field and the work or expression. Prefer a term from a controlled vocabulary, such as the MARC relator terms, RDA relationship designators, or RBMS relationship designators. Capitalize the first letter of the relationship term and record it in the singular. Follow the relationship term with a colon.
''Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a Best of Indian English poetry
386 ## $i Auteur : $a Indiens de l'Inde $2 rvmgd
<br><br>
130 #0 $a Private worlds (Catalogue d'exposition : 1998)
386 ## $i Artiste : $a Européens $2 rvmgd
670 ## $a Private worlds, 1998 : $b page de titre ("classic outsider art from Europe : Katonah Museum of Art, December 13, 1998- February 28, 1999")
</div>
Do not record multiple subfield $i’s in a single 386 field. If multiple relationship terms apply to a single group of creators or contributors (e.g., a work with authors and artists from the same demographic group or an expression with editors and translators from the same demographic group), repeat the field, using different relationship terms.
''Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a City lights (Greater Brockton Society for Poetry and the Arts (Mass.))
386 ## $i Auteur : $a Massachusettais $2 rvmgd
386 ## $i Artiste : $a Massachusettais $2 rvmgd
670 ## $a City lights, 2009 : $b page de titre (anthologie de poésie et d'art de la Greater Brockton Society for Poetry and the Arts; éditrice intellectuelle, Sheila Mullen Twyman)<br>
(A compilation of works by authors and artists from Massachusetts)
</div>
If different relationship terms apply to some of the creators and contributors (e.g., authors are in one demographic group and artists are in another), repeat the field, using different relationship terms. If the same relationship term applies to more than one demographic group, either repeat subfield $a in one field, or repeat the field. For clarity, when in doubt, repeat the 386 field as necessary.
''Example :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a 50 German songs (Voix aiguë)
386 ## $i Compositeur : $a Allemands $a Autrichiens $2 rvmgd
386 ## $i Auteur : $a Allemands $a Autrichiens $2 rvmgd
ou
386 ## $i Compositeur : $a Allemands $2 rvmgd
386 ## $i Compositeur : $a Autrichiens $2 rvmgd
386 ## $i Auteur : $a Allemands $2 rvmgd
386 ## $i Auteur : $a Autrichiens $2 rvmgd<br>
(Score containing works by Schubert, Schumann, Franz, Brahms, Wolf, Mahler, and Strauss, with lyrics also printed as text in German and English translation)
</div>
'''Subfield $m – Demographic group term and Subfield $n – Demographic group code'''
Do not use these subfields, but do not remove them from existing records if they are correctly coded.
[2023-09-11]<!--(2023-11-09)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]
= 388 Time Period of Creation =
'''General'''
PFAN catalogers may use this field to record the time period of creation or origin of a work or expression. The name of the time period may specify or imply a place for which the time period is relevant. It may also specify the name of an event.
Prefer a controlled vocabulary, such as RVM or RVMFAST, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a.
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Harlem Renaissance $2 rvm
388 1# $a Dynastie des Han (Chine) $2 rvmfast
388 1# $a <span style="color:red>Rébellion des Patriotes (Canada : 1837-1838) $2 rvmfast</span>
</div>
If using an RVM subject heading string, replace the subfield coding for the subdivision(s) with two hyphens and close up the spaces between the main heading and subdivision(s).
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Crises économiques--1929 $2 rvm
</div>
For compilations, the field may be used to record the time period of creation or origin of the works/expressions contained within the compilation, considered collectively (using first indicator value “1”). It may also be used to record the time period of creation or origin of the compilation itself (using first indicator value “2”).
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Renaissance $2 rvm
388 2# $a Dix-neuvième siècle $2 rvm
<div style="font-family:sans-serif; margin-left:85px;">
<div style="font-family:sans-serif; margin-left:85px;">
''(Nom changé après le mariage)''</div>
''(Nom changé après le mariage)''</div>
</div>
</div>
<span style="color:red>When an authorized access point for a person (100) is updated to close the date, it is recommended to save the former form with the open date in a 4XX field with $w nnea.</span>
<span style="color:red>''Example :''</span>
<div style="font-family:courier new; margin-left:0px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<span style="color:red>100 1# $a Laurin, Rachel, $d 1961-2023<br>
400 1# $w nnea $a Laurin, Rachel, $d 1961-</span>
</div></span>
When an authorized access point (1XX) based on CIP cataloging is changed because its form on the published resource is different from that on the CIP galley, a 4XX from the previous authorized access point form with subfield $w nne may be added unless the former 1XX form was egregiously incorrect (e.g., the author's date of birth was given as 1775 instead of 1975 in the CIP galley).
When an authorized access point (1XX) based on CIP cataloging is changed because its form on the published resource is different from that on the CIP galley, a 4XX from the previous authorized access point form with subfield $w nne may be added unless the former 1XX form was egregiously incorrect (e.g., the author's date of birth was given as 1775 instead of 1975 in the CIP galley).
</div>
</div>
</div>
</div>
<span style="color:red>When changing an authorized access point because dates were recorded inaccurately or a cataloger entered a typo in the authorized access point, do not add the inaccurate form as a cross reference.</span>
<!--'''SARs'''
<!--'''SARs'''
If the volumes of a multipart monograph have different forms of the common title, use a 4XX reference rather than a 5XX reference for the form of the title not chosen as the title proper of the multipart monograph.
If the volumes of a multipart monograph have different forms of the common title, use a 4XX reference rather than a 5XX reference for the form of the title not chosen as the title proper of the multipart monograph.
-->
-->
[2021-11-03] <!--(2021-11-01)-->
[2024-03-27] <!--(2024-03-27)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#4XX_Fields_Tracings_and_References_-_General_Information|''Supplement'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D|''Manual 4XX and 5XX'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#Simple_4XX_.22see.22_cross-references_.5BNew.5D |''Manual 4XX'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#4XX_Fields_Tracings_and_References_-_General_Information|''Supplement'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D|''Manual 4XX and 5XX'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#Simple_4XX_.22see.22_cross-references_.5BNew.5D |''Manual 4XX'' <big>⮞</big>]]
[2021-03-10]<!--(2021-03-04)-->
[2021-03-10]<!--(2021-03-04)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#500_See_Also_From_Tracing-Personal_Name|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#500_See_Also_From_Tracing-Personal_Name|''Supplement'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D|''Manual 4XX and 5XX'' <big>⮞</big>]]
= 510 See Also From Tracing - Corporate Name =
= 510 See Also From Tracing - Corporate Name =
Give subsequent 670 fields in any order, adding new fields after existing ones. Do not routinely delete or change existing 670 fields when adding new 670 fields.
Give subsequent 670 fields in any order, adding new fields after existing ones. Do not routinely delete or change existing 670 fields when adding new 670 fields.
When adding subsequent 670 fields, prefer objective, authoritative sources (e.g., an encyclopedia) and those sources that provide firsthand information (e.g., an author’s blog). Use sources that provide additional information rather than repeating information that is already present in other 670 fields.
When adding subsequent 670 fields, prefer objective, authoritative sources (e.g., an encyclopedia) and those sources that provide firsthand information (e.g., an author's blog). Use sources that provide additional information rather than repeating information that is already present in other 670 fields.
<ol>'''Best practices for 670 fields:'''
<ol>'''Best practices for 670 fields:'''
A 670 field should include the following data in subfield $a:
A 670 field should include the following data in subfield $a:
# The title proper of the resource being cited, complete enough for later identification in an online catalog. Abbreviations and ellipses may be used. Precede a generic or indistinctive title with the creator’s name that would begin the authorized access point for the work. If the authorized access point for the work is the same as the title proper plus a qualifier, it may be provided instead of the title proper to avoid ambiguity. When information in subfield $a of a 670 field is provided to justify an authorized or variant access point, follow the additional instructions at ''Recording names and titles''.
# The title proper of the resource being cited, complete enough for later identification in an online catalog. Abbreviations and ellipses may be used. Precede a generic or indistinctive title with the creator's name that would begin the authorized access point for the work. If the authorized access point for the work is the same as the title proper plus a qualifier, it may be provided instead of the title proper to avoid ambiguity. When information in subfield $a of a 670 field is provided to justify an authorized or variant access point, follow the additional instructions at ''Recording names and titles''.
# The date of publication.
# The date of publication.
<ol>
<ol>
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a Site Web de l'organisme, consulté le 16 août 2019 : $b page d'accueil (Carrefour jeunesse-emploi Drummond; CJE Drummond) À propos (ouvre ses portes en novembre 1998; organisme sans but lucratif) Nous joindre (749, boul. Mercure Drummondville (Québec) J2B 3K6; cjed@cgocable.ca)
<div style="text-indent:-85px;">
670 ## $a Site Web de l'organisme, consulté le 16 août 2019 : $b page d'accueil (Carrefour jeunesse-emploi Drummond; CJE Drummond) À propos (ouvre ses portes en novembre 1998; organisme sans but lucratif) Nous joindre (749, boul. Mercure Drummondville (Québec) J2B 3K6; cjed@cgocable.ca)</div>
<div style="text-indent:-85px; padding-top:1.3em;">
670 ## $a Site Web du Réseau Mentorat, consulté le 23 décembre 2021 : $b Accueil (Réseau Mentorat (Fondation de l'entrepreneurship)) Accueil; À propos; Nous connaître; Notre histoire (en 2020, le Réseau M devient le Réseau Mentorat)</div>
</div>
</div>
</ol>
</ol>
Catalogers may optionally provide a uniform resource identifier (URI) in subfield $u of the 670 citation to link to the cited resource if it contains significant information related to the established entity
Catalogers may optionally provide a uniform resource identifier (URI) in subfield $u of the 670 citation to link to the cited resource if it contains significant information related to the established entity
that cannot be cited succinctly in the authority record. Note that use of a URI in the 670 $u does not take the place of the requirement to cite relevant data in subfields $a and $b of the 670 field needed to support the authorized access point (including additions) or variants (this information will continue to be available if the site changes or disappears). However, information found in online sources may be added to the 046 or 3XX fields with the appropriate citations in subfields $v and $u and not repeated in a 670 when that information is not used in the 1XX or a 4XX. If a URI is included in a 670, it must be given in subfield $u.
that cannot be cited succinctly in the authority record. Note that use of a URI in the 670 $u does not take the place of the requirement to cite relevant data in subfields $a and $b of the 670 field needed to support the authorized access point (including additions) or variants (this information will continue to be available if the site changes or disappears). However, information found in online sources may be added to the 046 or 3XX fields with the appropriate citations in subfields $v and $u and not repeated in a 670 when that information is not used in the 1XX or a 4XX. If a URI is included in a 670, it must be given in subfield $u. <span style="color:red>The subfield $u should contain only the URI and no additional data (e.g., do not enclose the URI within parentheses and do not include words in the subfield $u).</span>
''Example:''
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a British Oceanographic Data Centre, consulté le 23 novembre 2009 : $b About us (British Oceanographic Data Centre, National Environment Research Council; <span style="color:red>le BODC est un organisme national chargé de la gestion et de la diffusion des données relatives au milieu marin)</span> $u http ://www.bodc.ac.uk/
670 ## $a British Oceanographic Data Centre, consulté le 23 novembre 2009 : $b About us (British Oceanographic Data Centre, National Environment Research Council; le BODC est un organisme national chargé de la gestion et de la diffusion des données relatives au milieu marin) $u http ://www.bodc.ac.uk/
</div>
</div>
</div>
</div>
For corporate name authorities, include in the data cited all the hierarchy required to justify needed variant access points, Use judgment in deciding what information (e.g., subordinate body’s name) is extraneous to the record being created and should not be recorded.
For corporate name authorities, include in the data cited all the hierarchy required to justify needed variant access points, Use judgment in deciding what information (e.g., subordinate body's name) is extraneous to the record being created and should not be recorded.
For all of the above categories, if the only presentation of the name or title on the chief source of information is in the bibliographic title given in subfield $a of the 670 citation, repetition of the name in
For all of the above categories, if the only presentation of the name or title on the chief source of information is in the bibliographic title given in subfield $a of the 670 citation, repetition of the name in
<span id="Usage"></span><small>2. [[#^2|^]] "Usage" for bibliographic records refers to the transcribed forms of name usually found in statements of responsibility of bibliographic records. It may also appear in other parts of the bibliographic record such as a title proper or a quoted note. Because of changes in cataloging instructions, catalogers should be careful when taking information from the publication statement, distribution statement, etc. and the series statement.</small>
<span id="Usage"></span><small>2. [[#^2|^]] "Usage" for bibliographic records refers to the transcribed forms of name usually found in statements of responsibility of bibliographic records. It may also appear in other parts of the bibliographic record such as a title proper or a quoted note. Because of changes in cataloging instructions, catalogers should be careful when taking information from the publication statement, distribution statement, etc. and the series statement.</small>
<br>
<br>
<span id="Forme_non_transcrite"></span><small>3. [[#^3|^]] « Forme non transcrite » (or « formes non transcrites ») for bibliographic records refers to a form of the name that may not represent a transcribed form. For example, in AACR2 records, a publisher’s name that appeared on the resource as “ABC Publishing Company” might have been recorded in the publication statement as “ABC Pub. Co.” Normally, there is no need to cite such a form in a 670 field..</small>
<span id="Forme_non_transcrite"></span><small>3. [[#^3|^]] « Forme non transcrite » (or « formes non transcrites ») for bibliographic records refers to a form of the name that may not represent a transcribed form. For example, in AACR2 records, a publisher's name that appeared on the resource as “ABC Publishing Company” might have been recorded in the publication statement as “ABC Pub. Co.” Normally, there is no need to cite such a form in a 670 field..</small>
<br><br>
<br><br>
For information on existing 670 citations found in undifferentiated NARs, see in this Manual, [[PFAN_-_Name_Authority_Manual#008.2F32_Undifferentiated_personal_name|008/32 Undifferentiated Personal Name]].
For information on existing 670 citations found in undifferentiated NARs, see in this Manual, [[PFAN_-_Name_Authority_Manual#008.2F32_Undifferentiated_personal_name|008/32 Undifferentiated Personal Name]].
[2022-11-22]<!--(2022-11-22)-->
[2023-09-11]<!--(2023-09-11)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#670_Source_Data_Found|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#670_Source_Data_Found|''Supplement'' <big>⮞</big>]]
<ol>
<ol>
'''A) General information'''<br>
'''A) General information'''<br>
This is an authority records revision project, led by UQAM. These records have been created or modified in Canadiana by UQAM’s cataloguing “traitement documentaire” team. These records were then revised by two librarians and a library technician, also at UQAM. This project ended March 31, 2021.<br>
This is an authority records revision project, led by UQAM. These records have been created or modified in Canadiana by UQAM's cataloguing “traitement documentaire” team. These records were then revised by two librarians and a library technician, also at UQAM. This project ended March 31, 2021.<br>
When added to Canadiana, these new records contained the following elements: <br>
When added to Canadiana, these new records contained the following elements: <br>
* In the Leader/17, the value was "o" (Incomplete authority record).
* In the Leader/17, the value was "o" (Incomplete authority record).