Changes

PFAN - Name Authority Manual (view source)

Revision as of 15:52, 27 March 2024

3,858 bytes added , 27 March

→‎4XX - See From Tracings - General Information

Line 116: Line 116:

=== General ===

−

~~<span style="color:red>~~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”.~~</span>~~

+

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

−

~~<span style="color:red>~~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:~~</span>~~

+

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:

−

* ~~<span style="color:red>~~Do not create new undifferentiated records coded 008/32 “b”.~~</span>~~ All personal name authority records ~~<span style="color:red>~~coded RDA~~</span>~~ 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.”

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

Line 125: Line 125:

=== Maintenance of existing undifferentiated records: ===

−

~~<span style="color:red>~~'''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>

+

'''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.~~</span>~~

+

LAC cataloguer: Delete the undifferentiated authority record.

Line 164: Line 164:

</div>

−

When information is found to distinguish a person in an existing undifferentiated ~~<span style="color:red>~~from LAC or BAnQ~~</span>~~ 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".

* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.

Line 186: Line 186:

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 ~~<span style="color:red>~~control~~</span>~~ 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>

</li>

Line 336: Line 336:

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 ~~<span style="color:red>~~control~~</span>~~ 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>

<br>

Line 354: Line 354:

</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:

Line 365: Line 364:

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 ~~<span style="color:red>~~control~~</span>~~ 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>

Line 438: Line 437:

</div></span>

−

[2023-07-19]

+

[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>]]

Line 669: Line 668:

[2021-03-09]

<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 :''

+

+

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 =

Line 717: Line 812:

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

−

<span style="color:red>''~~Examples~~:''

+

<span style="color:red>''Example:''

046 ## $s -0199~ $2 edtf

Line 749: Line 844:

<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>''~~Examples~~ :''

+

<span style="color:red>''Example:''

Line 766: Line 861:

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>

−

(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)

+

+

''(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>

Line 783: Line 879:

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>

−

(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)

+

+

''(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>

Line 790: Line 887:

100 1# $a Hepburn, Katharine, $d 1907-2003<br>

−

(Same example as above, reflecting a different decision the cataloger might have made for recording 046 subfield $f)

+

+

''(Same example as above, reflecting a different decision the cataloger might have made for recording 046 subfield $f)'' </div>

</div>

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

−

<span style="color:red>'''~~DUncertain~~ dates resulting from date calculations'''

+

<span style="color:red>'''Uncertain dates resulting from date calculations'''

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

Line 812: Line 910:

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>

−

(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)

+

+

''(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>

Line 828: Line 927:

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>

−

(The Hijri calendar date 1346 H converts to either 1967 or 1968 in the Gregorian calendar.)

+

+

''(The Hijri calendar date 1346 H converts to either 1967 or 1968 in the Gregorian calendar.)''</div>

</div>

Line 835: Line 935:

Always add subfield $2 edtf except after a century.

−

'''~~Subfield~~ $s – Start period, and $t – End period'''

+

'''<span style="color:red>Subfields $q – Establishment date, $r – Termination date,</span> $s – Start period, and $t – End period'''

−

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

+

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

−

'''~~Subfield~~ $~~u – Uniform Resource Identifier and Subfield and Subfield~~ $~~v – Source of information'''~~

+

''<span style="color:red>Example :''

+

+

046 ## $s 2017-07-27 $t 2017-08-06 $2 edtf

−

~~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:~~

+

111 2# $a Festival des arts de Saint-Sauveur $n (26e : $d 2017 : $c Saint-Sauveur, Québec)

−

~~<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:~~

+

670 ## $a Festival des arts de Saint-Sauveur, du 27 juillet au 6 août 2017, 2017

−

~~<ol>~~

+

</div>

−

~~<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>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 :''

+

+

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)

+

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 $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>

+

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

Line 885: Line 1,011:

</div>

−

[2023-09-11]

+

[2023-10-05]

<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]  |  [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#046_Special_Coded_Dates|''Supplement'' <big>⮞</big>]]

Line 892: Line 1,018:

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

+

= 053 LC classification number <span style="color:red>[New]</span>=

−

~~<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]  |  [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#053_LC_Classification_Number|''Supplement'' <big>⮞</big>]]~~

−

~~<!--~~

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.

−

''Examples''

+

''Examples:''

Line 914: Line 1,038:

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.

−

[2023-09-28]

+

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

Line 921: Line 1,045:

<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>]]

−

= 065 Other Classification Number =

+

= 065 Other Classification Number <span style="color:red>[New]</span>=

−

~~<br>[[#toc|''Return~~ to ~~Table of Contents'' <big>⮝</big>]]  |  [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#065_Other_Classification_Number|''Supplement'' <big>⮞</big>]]~~

+

Field 065 is used to record PS8000 class numbers. Field 065 must always include a subfield $2 and a subfield $5.

−

= 080 Universal Decimal Classification Number =

+

''Example:''

+

+

065 ## $a PS8576.U57 $2 fcps $5 [MARC code of institution]

+

</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>]]

Line 1,524: Line 1,661:

= 375 Gender =

+

'''PFAN'''

−

~~'''General'''~~

+

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

−

~~When recording a term indicating gender, prefer the terns ''masculin'' and ''féminin''. For these terms, do~~ not ~~capitalize or indicate the source of the term~~ in ~~the $2 subfield~~. ~~If neither of these terms is appropriate or sufficiently precise,~~ record ~~an appropriate term or phrase preferably using a controlled vocabulary~~, ~~such as the RVMGD or the [https://www.btb.termiumplus.gc~~.~~ca/publications~~/diversite-diversity-eng.html ''Gender and sexual diversity glossary''], recording the source in subfield 2. For consistency, capitalize the first term in each subfield $a for terms other than ''masculin'' and ''féminin''. When terms are not taken from a controlled vocabulary, use the singular form. Use terms rather than ISO 5218 codes.

−

~~'''Repeatability:'''~~

+

[2023-10-20]

−

+

<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]  |  [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement'' <big>⮞</big>]]

−

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 corresponding 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:''~~

−

−

~~100 1# $a Lenoir, Axelle, $d 1979-~~

−

~~375 ## $a Transgenres $2 rvmgd~~

−

~~375 ## $a féminin $s 2018~~

−

~~375 ## $a masculin $s 1979 $t 2018~~

−

~~</div>~~

−

~~'''Subfield $2 – Source of term'''~~

−

~~Codes from the~~ [~~http://www.loc.gov/standards/sourcelist/gender.html Gender Source Codes] list may be recorded in subfield $2 for the 375 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.~~

−

~~______~~

−

~~'''LAC :'''~~

−

~~Do not record gender. ''Exception:'' When information has changed over the course of a person's life. Follow PFAN instructions.~~

−

~~Do not delete gender information recorded by other organizations.~~

−

~~[2021~~-03-12]

−

<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]  |  [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement~~'' <big>⮞</big>]]  |  [[PFAN_-_Participant%27s_Manual#375_.E2.80.93_Gender_.28R.29|''Participant's Manual~~'' <big>⮞</big>]]

= 376 Family information =

Line 1,840: Line 1,945:

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

+

= 386 Creator/contributor characteristics <span style="color:red>[New]</span>=

'''General'''

−

~~<span style="color:red>~~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).~~</span>~~

+

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

−

~~<span style="color:red>~~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].~~</span>~~

+

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

−

~~<span style="color:red>~~''Examples :''~~</span>~~

+

''Examples :''

−

+

130 #0 $a Pièces pour piano composées par des enfants

Line 1,884: Line 1,989:

</div>

−

~~<span style="color:red>~~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

+

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

−

~~<span style="color:red>~~''Example :''

+

''Example :''

−

+

100 1# $a Greenberg, Jay, $d 1991- $t Symphonies, $n no 5

Line 1,896: Line 2,001:

</div>

−

~~<span style="color:red>~~'''Repeatability:'''

+

'''Repeatability:'''

−

~~<span style="color:red>~~In choosing between repeating a field and repeating subfield $a:

+

In choosing between repeating a field and repeating subfield $a:

−

~~<span style="color:red>~~ 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.

+

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.

−

~~<span style="color:red>~~''Examples :''

+

''Examples :''

−

+

130 #0 $a Latin American women writers

Line 1,945: Line 2,050:

</div>

−

~~<span style="color:red>~~'''Subfield $i – Relationship information'''

+

'''Subfield $i – Relationship information'''

−

~~<span style="color:red>~~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.

+

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.

−

~~<span style="color:red>~~''Example :''

+

''Example :''

−

+

130 #0 $a Best of Indian English poetry

Line 1,964: Line 2,069:

</div>

−

~~<span style="color:red>~~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.

+

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.

−

~~<span style="color:red>~~''Example :''

+

''Example :''

−

+

130 #0 $a City lights (Greater Brockton Society for Poetry and the Arts (Mass.))

Line 1,979: Line 2,084:

</div>

−

~~<span style="color:red>~~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.

+

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.

−

~~<span style="color:red>~~''Example :''

+

''Example :''

−

+

130 #0 $a 50 German songs (Voix aiguë)

Line 2,002: Line 2,107:

</div>

−

~~<span style="color:red>~~'''Subfield $m – Demographic group term and Subfield $n – Demographic group code'''

+

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

−

~~<span style="color:red>Do not use these subfields, but do not remove them from existing records if they are correctly coded.~~

−

~~</span>~~

[2023-09-11]

Line 2,156: Line 2,261:

''(Nom changé après le mariage)''</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>

+

+

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

Line 2,179: Line 2,292:

</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'''

Line 2,188: Line 2,303:

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]

+

[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>]]

Nathalie.mainville

1,999

edits