2,057
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 9:
Line 9: − + − + + − + + − − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008 Fixed-Length Data Elements|''Supplement'' <big>⮞</big>]] Line 29:
Line 29: − '''Exception 1:''' <br>+ − − '''Exception 2:''' <br>+ − − + + − + Line 49:
Line 48: − '''Examples of corporate names not appropriate for use as subject headings:'''+ − + + + + + + − + − + − + Line 73:
Line 77: − '''Background:''' For Heads of state, heads of governments, etc., International intergovernmental+ − + − + − + − + − + Line 90:
Line 94: − '''Example:'''+ − + + + − + Line 104:
Line 110: − + Line 110:
Line 116: − When creating an NAR for a family name, assign value “n” in 008/32.+ − Comme la LC et le PCC, le PFAN adhère aux lignes directrices suivantes pour les personnes dont les noms privilégiés sont identiques :+ − As LC and the PCC, PFAN has agreed to the following guidelines for persons whose preferred names are identical:+ − + − 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: ===+ + + − Il peut arriver qu'une notice d'autorité de nom indifférenciée existante, en particulier une notice qui a été importée du LC/NAF, comprenne des paires de zones 670 utilisées pour regrouper l'information sur chaque personne visée par la notice d'autorité de nom. La première zone 670 de chaque paire est une zone 670 d'identification qui comprend un terme décrivant la relation de la personne avec le titre cité dans la deuxième zone 670 de la paire. Les données de la zone 670 d'identification sont enregistrées dans la sous-zone $a et sont mises entre crochets. La deuxième zone 670 de la paire est une zone 670 de citation qui comprend les éléments de données normaux dans la citation d'une ressource cataloguée. − An existing undifferentiated NAR 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+ − − + + − + + + − + + + − + + + − + − Il peut aussi arriver qu'une notice d'autorité de nom indifférenciée existante comprenne une note 667 indiquant que la notice est indifférenciée et identifiant la ou les ressources associées aux autres personnes portant le même nom. Dans ce cas, la notice ne comprend généralement pas de zones 670 pour les personnes autres que la première qui a été identifiée.+ − + + + + − + − + − + − + − * Le cas échéant, transférer la citation 670 se rapportant à cette personne depuis la notice d'autorité indifférenciée vers la nouvelle notice d'autorité de nom et modifier l'information si c'est nécessaire.+ − + − + − − − Afin de faciliter le traitement automatisé des notices d'autorité (par exemple, appariement, liaison), lorsqu'il ne reste qu'une seule identité dans une notice d'autorité de nom de personne indifférenciée (c'est-à-dire lorsque les autres identités sont désambiguïsées et enlevées), procéder comme suit :+ + − Créer une nouvelle notice d'autorité de nom pour l'unique identité restante. Si une notice d'autorité comportant la note 667 « 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 ») existe déjà pour cette identité, utiliser cette notice comme « nouvelle notice ». Le point d'accès autorisé lui-même peut être différent ou il peut être identique au point d'accès autorisé dans la notice d'autorité de nom indifférenciée. Dans la nouvelle notice :+ − Le cas échéant, transférer la citation 670 se rapportant à l'unique identité restante depuis la notice d'autorité indifférenciée vers la nouvelle notice d'autorité de nom et modifier l'information si c'est nécessaire.</li>+ − Ajouter la note 667 :+ − + − + − + + + + − <li style="list-style-image: none; list-style-type:circle;">Ajouter dans la zone 016, sous-zones $z le numéro Canadiana de la notice d'autorité de nom indifférenciée qui sera supprimée, s'il y en a un.</li> − </ul> − Réévaluer la nouvelle notice d'autorité de nom si celle-ci contient la note 667 « 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 ».</li>+ − + − + − + + − + − Message générique suggéré :+ − + − + − + − + − + − + − + − + − + − + − Notice d'autorité indifférenciée avant la désambiguïsation :+ − + − + + + + + − + − Nouvelle notice pour l'auteur d'Histoire du département de la Manche :+ − + − + + + − + + + − + − + − Notice d'autorité indifférenciée après la désambiguïsation. L'identité qui reste est pour l'auteur d'Hydraulique urbaine :+ − + + − + + + − + − + − Nouvelle notice pour l'auteur d'Hydraulique urbaine :+ − + + − + + + − + + + − + − + + − Notice d'autorité indifférenciée avant la désambiguïsation :+ − + + + + + + + − + − Nouvelle notice pour l'autrice d'Esperanza :+ − + − + + + − + + + − + − Notice d'autorité indifférenciée après la désambiguïsation. L'identité qui reste est pour l'illustratrice de Reptiles :+ − + + + + − + + + − + − Nouvelle notice pour l'illustratrice de Reptiles :+ − + − 008/32 = a+ − + + + − + + + − + − + − Toujours ajouter une note 667 à une nouvelle notice d'autorité de nom pour identifier le numéro Canadiana de la notice d'autorité dans laquelle l'information sur cette personne a déjà été enregistrée :+ − + − + − + + + − [2021-02-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>]]+ − + + + − '''NARS'''+ − + − + + − Code an NAR as provisional (008/33 value “c”) if the authorized access point cannot be formulated satisfactorily because of inadequate information. If the necessary information later becomes available, re-evaluate the NAR and upgrade it to fully established (008/33 value “a”). In no case should a provisional-level authority record be created with an access point that conflicts with an existing NAR according to NACO normalization rules.<br>+ − + + + − Because there is uncertainty about whether Hong Kong and Macau will continue to have two official languages, code all NARs for government bodies in these two places, at the level of the special administrative region and below, as provisional (008/33 value “c”), regardless of the language in which the authorized access point has been established. If a form in the second of the two official languages becomes available, add that form as a variant access point rather than revising the existing authorized access point. Consult [http://original.rdatoolkit.org/rdachp11-fr_rda11-1365.html RDA 11.2.2.5.2] and the [http://original.rdatoolkit.org/lacbanqpschp11_lacbanqps11-105.html related policy statement] for instructions on choosing the language of the referred name. Please note that this policy for provisional status does not apply to non-government bodies.<br>+ + + + + − + + − Les participants au PFAN peuvent créer des notices provisoires dans les deux situations exceptionnelles suivantes :<br>+ − PFAN participants may also create provisional records in the following two exceptional situations:+ − + − + − #+ − # If the contributing library is unable, due to limited resources or other constraints, to complete related authority work or to determine the appropriate reference structure that is required for fully established authority records.<br>+ − + + + + + + − + + + + − + + − <ol>+ − <br>As needed, catalogers may upgrade NARs coded preliminary when working with earlier/later corporate body records, even if the access points in the records being upgraded are not used in the local bibliographic database. Occasionally catalogers may need to create a new NAR without having an item in hand, e.g., for an earlier or later name heading using information from reference sources, or a heading based on information found in field 245 subfield “c” of bibliographic records when resolving NAR conflicts. Do not code these occasional NARs as “preliminary.” − </ol> − '''SARs'''+ − + − are optional. − Generally, series data elements should be viewed on the publication and series authority records should be coded “a” (full). In post-cataloging authority work it is permissible to create SARs without the piece in hand; these records are coded “d” (preliminary). When a publication in the series has been examined and the preliminary authority record reviewed and updated as necessary, upgrade the SAR to full level.+ − [2021-02-28]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#008.2F33_Level_of_establishment|''Supplement'' <big>⮞</big>]]+ − + + − '''PFAN series practice:'''<br>+ − 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. − Whatever value is originally input into this field remains; do not change this value when updating a record unless the original value was incorrect.+ − [2021-02-15]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#008.2F39_Cataloging_source|''Supplement'' <big>⮞</big>]] − = 016 National Bibliographic Agency Control Number =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#016_National_Bibliographic_Agency_Control_Number|''Supplement'' <big>⮞</big>]]+ − = 022 International Standard Serial Number =+ − ''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.+ − '''General'''<br>+ − Record the ISSN whenever it is available from the item in hand, from analytic bibliographic records, or from the collected set bibliographic record for the series; otherwise, recording the ISSN is optional.+ − When it is known there are separate ISSN assigned to different formats of a series represented by a single SAR, prefer to record in 022 subfield $a the ISSN that is the linking ISSN (ISSN-L) for the different formats. Identify ISSN for specific formats in separate 667 fields, following this pattern:+ − − <pre style="font-family:courier new;"> − 667 $a Version imprimée : ISSN YYYY-ZZZZ − 667 $a Version en ligne : ISSN YYYY-ZZZZ − </pre> − When the title of a publication has changed, confirm that an ISSN appearing on the publication belongs to the new title and not to the earlier title.+ − An incorrect ISSN can be given in a 667 field (e.g., “ISSN 1122-3344 is not a valid ISSN for this publication”).+ − [2021-02-15] + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#022_International_Standard_Serial_Number|''Supplement'' <big>⮞</big>]] − = 024 Other standard identifier =+ − '''General'''<br> − Follow the guidelines in [https://www.loc.gov/aba/pcc/naco/documents/NACO-024-Best-Practices.pdf NACO Best Practices] for the 024 Field. As a general rule, limit the number of 024 fields in a NACO authority record to five. Do not routinely delete or change existing 024 fields when adding new ones. − '''Maintenance'''<br>+ − Catalogers are not required to maintain identifiers coded in the 024 field of PFAN authority records. When an 024 field is present in an authority record that is being reported for deletion (for example, in the case of a duplicate), catalogers should transfer the field to the record that is to be retained. When two authority records are being collapsed into one, and each record has a different 024 field, catalogers should include both 024 fields in the updated record. − + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#024_Other_Standard_Identifier|''Supplement'' <big>⮞</big>]] − = 034 Coded cartographic mathematical data =+ + − + + − Coordinates for outside limits (bounding boxes or polygons) should generally be used with larger geographic entities such as countries, states, and counties to identify the coordinates of the entity. The+ − coordinates may be recorded in either degrees/minutes/seconds, decimal degrees, decimal minutes, and/or decimal seconds. Styles should not be mixed in a single 034 field, but the field may be repeated to − represent the different styles (see below for conversion utilities); the order of 034 fields when both styles are given does not matter. To facilitate the reuse of coordinates in geographic applications, the point (not the comma) should be used as the decimal point. − :'''Degrees/minutes/seconds''': record in the form hdddmmss (hemisphere-degrees-minutes-seconds).+ − + − ::034 ## $d W1800000 $e E1800000 $f N0840000 $g S0700000+ − </div> − :'''Decimal degrees''': record in the form hddd.dddddd (hemisphere-degrees.decimal degrees) − <div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;"> − ::034 ## $d E079.533265 $e E086.216635 $f S012.583377 $g S020.419532 − </div> − :'''Decimal degrees with plus ou minus''': record in the form +-ddd.dddddddd (hemisphere[+/-]-degrees.decimal degrees) (“+” or N and E, “-” for S and W ; the plus sign is optional) − <div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;"> − ::034 ## $d +079.533265 $e +086.216635 $f -012.583377 $g -020.419532<br> − :::<div style="font-family:sans-serif;">(Example with +/-)</div> − ::034 ## $d 079.533265 $e 086.216635 $f -012.583377 $g -020.419532<br>+ − :::<div style="font-family:sans-serif;">(Example without the optional plus sign)</div>+ − − :'''Decimal minutes''': record in the form hdddmm.mmmm (hemisphere-degrees-minutes.decimal minutes)+ − − ::034 ## $d E07932.5332 $e E08607.4478 $f S01235.5421 $g S02028.9704 − </div> − :'''Decimal seconds''': record in the form hdddmmss.sss (hemisphere-degrees-minutes-seconds.decimal seconds) − <div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;"> − ::034 ## $d E0793235.575 $e E0860727.350 $f S0123536.895 $g S0202858.125 − + + + + + − '''Recording coordinates for cities, towns, and townships'''<br>+ − Coordinates for cities, towns, and townships should generally be recorded as center points rather than outside limits. For the 034 field, the longitude and latitude that form the central axis are recorded+ − twice to define the center point (i.e., the contents of $d and $e are identical, the contents of $f and $g are identical).+ + + + + + − + − :: 034 ## $d W0950500 $e W0950500 $f N0303000 $g N0303000<br>+ − :::<div style="font-family:sans-serif;">(Example showing degrees/minutes/seconds)</div> − + − :::<div style="font-family:sans-serif;">(Example showing decimal degrees)</div>+ − ::034 ## $d -119.697222 $e -119.697222 $f +034.420833 $g +034.420833<br>+ − :::<div style="font-family:sans-serif;">(Example showing decimal degrees with plus/minus)</div>+ + + + − + − PFAN institutions are encouraged to provide both degrees/minutes/seconds and decimal degrees when available. Numerous conversion tools are available on the Web to derive one from the other; here are two examples:+ + − ::'''Degrees/minutes/seconds to Decimal degrees:'''<br>+ − ::http://vancouver-webpages.com/META/DMS.html − ::'''Decimal degrees to Degrees/minutes/seconds:'''<br>+ − ::http://vancouver-webpages.com/META/DD.html + + − + − Subfield $2 has been defined for recording the source of the coordinate information– codes for commonly used sources are available from: [http://www.loc.gov/standards/sourcelist/cartographic-data.html/view Cartographic Data Source Codes].+ − A 670 citation to the source would not be required if the only information from the source is recorded in field 034; a 670 citation should be made if necessary to record information beyond coordinates, such as variant names, hierarchy, time period of applicability, etc.+ − [2021-02-22]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#034_Coded_Carographic_Mathematical_Data|''Supplement'' <big>⮞</big>]] − = 035 System Control Number =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#035_System_Control_Number|''Supplement'' <big>⮞</big>]]+ − = 040 Cataloging source =+ − 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.+ − + − Subfield $b fre added automatically by WMS.+ + − '''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 $e – Description conventions'''<br> − All new authority records created and submitted by PFAN cataloguers must have the code "z" in Field 008/10 and include the $e rda subfield in Field 040. − When adding the subfield $e manually, add it after subfield $b and before $c. It is not necessary to move the subfield $e to this position if it is already present elsewhere in the 040 or if it is being added by a macro or a template. Subfield $e rda is automatically added by the system in NARs and SARs when fixed field 008/10 (Rules) is set to “z” (Other).+ + − [2021-02-15]+ − + − = 042 Authentication Code =+ − '''PFAN'''<br>This field is found in all authority records used by LAC. Do not modify or delete this field when code CaOONL appears in field 040.+ − When cataloguers (other than LAC cataloguers) derive an authority record from an LAC record which includes field 042, they must remember to delete this field. + − _____ − + − [2021-02-18]+ − − = 046 Special coded dates =+ − + − Best practice: When encoding date information, give the fullest information about the date that is readily available (the date in field 046 may be more precise than a date used in the 100 subfield $d). When 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 LAC-BanQ PS 9.3.1.3. + + + − '''Examples :'''+ − + − 046 ## $f 1884-10-11 $g 1962-11-07 $2 edtf+ − 100 1# $a Roosevelt, Eleanor, $d 1884-1962+ − 670 ## $a When you grow up to vote, 1932 : $b p. de t. (Eleanor Roosevelt (Mrs. Franklin D. Roosevelt)) − 670 ## $a Wikipédia, consultée le 21 juillet 2010 $b (Eleanor Roosevelt; Anna Eleanor Roosevelt; née le 11 octobre 1884 à Manhattan, à New York; morte le 7 novembre 1962) − 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.) − 046 ## $f 1946-06 $2 edtf+ − 100 1# $a Vickers, Roy Henry, $d 1946- − 670 ## $a Solstice, c1988 : $b p. de t. (Roy Henry Vickers) jaquette (artiste amérindien; né en juin 1946 à Greenville, Colombie-Britannique) − 046 ## $k 1981 $2 edtf+ − 100 1# $a Allende, Isabel. $t Casa de los espíritus − 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) − </pre> − 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). + + − + − + − 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) − </pre> − Note that the 1st century A.D. is represented by value “00” and B.C. centuries have a hyphenminus 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. + − + + − Always add subfield $2 edtf except after a century. + − + − For instructions on using $s and $t for start and end periods in fields 368, and 370-376, see the instructions provided in the 373 field. + + + − + − 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: + − + − <li>670s must be used to support information used as part of a heading in 1XX and 4XX fields.</li>+ − + − + − <li type="a">use of $v is optional if the same information/source is already cited in the 670</li>+ − + + + − <li type="a">use of $u is optional, and should always be preceded by $v</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. − + − 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+ + − + + + − 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 :'''+ − <pre style="font-family:courier new;">+ − 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) − − [2021-02-19] − <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 =+ + − <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>]]+ − = 065 Other Classification Number =+ + − <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>]]+ − = 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>]]+ − = 1XX Headings - General Information =+ − + − 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.+ − + − + − For the title proper of a multipart monograph, consult RDA 2.1.2.3.+ + + + + − ''Choosing a monographic series title proper:'' − #If the resource has more than one form of series title, consult RDA 2.12.2.2 and 2.12.2.5.+ − #+ − #If the resource has the series title in more than one language or script on the same source, consult RDA 2.12.2.4.+ − #+ − #If the resource has series title pages in more than one language and or script, consult RDA 2.2.3.1.+ − #+ − #Consider spacing and changes in typography when determining where the series title begins and ends. Also consult RDA 2.12.2.3.+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + + − <ol><li>Determine choice of authorized access point based on RDA 6.27 and its associated LAC-BAnQ PS.</li>+ − + − <ol> − <li type="a">initial article in subfields $a, $t, $n, and $p;</li> − + − + + + + + + + − <li type="a">parallel title(s);</li>+ − + + − <li type="a">numeric/chronological designations.</li>+ − </ol> − </li> − <li>Add a parenthetical qualifier(s) if appropriate according to the guidelines in LAC-BAnQ PS 6.27.1.9.</li>+ − + − For instructions on converting an existing NAR to an SAR, see Should an SAR be made? in the Introduction of Z1. [to be modify]+ + − [2021-02-19]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]] − + + + + − '''''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, 667 section, 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. − # − # 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:''' − − 100 3# $a Jones (Famille : $d 1801-1950 : $c New York, N.Y. : $g Jones, Samuel, 1830-1899) − + − + + − '''General'''+ − 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:+ + − 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.+ − + − <pre style="font-family:courier new;"> − 100 0# $a Élisabeth $b Ire, $c reine d'Angleterre, $d 1533-1603 $c (Esprit) − </pre></ol> − 2) Generally add subfield $c before subfield $q when also adding words, numerals, etc. indicating relationship. (See RDA 9.2.2.9.5 for treatment of Portuguese names)+ − + − <pre style="font-family:courier new;"> − 100 1# $a McCauley, Robert H., $c Jr. $q (Robert Henry), $d 1913-1979 − − BUT + − − 100 0# $a M. Alicia $q (Mary Alicia), $c Sister, S.C.N. − </pre></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 LAC-BAnQ PS 1.7.1.+ − [2021-02-19] + − − + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#151_Heading-Geographic_Name|''Supplement'' <big>⮞</big>]]+ − = 336 Content Type =+ − '''General''' − Field 336 may only be used in NARs and SARs for expressions. 336 is always accompanied by a subfield $2.+ + + − '''Subfield $2 – Source of term'''+ − In subfield $2 give “rdacontent/fre.” + − + + + − 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]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#336_Content_Type|''Supplement'' <big>⮞</big>]] − = 368 Other attributes of person or corporate body =+ − '''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.+ − + − <pre style="font-family:courier new;">+ − 110 2# $a Freer Gallery of Art − 368 ## $a Musées d'art $2 rvm − 151 ## $a France+ − 368 ## $b États $2 ram+ + − 151 ## $a Garwolin (Pologne : Powiat) − 368 ## $b Powiat − 100 0# $a Jeanne, $c d'Arc, sainte, $d 1412-1431 − 368 ## $c Saints $2 rvmgd − 100 0# $a Palamède $c (Personnage du cycle arthurien)+ − 368 ## $c Personnage du cycle arthurien − 110 2# $a Church of Christ (Rigdonites) + − 368 ## $c Rigdonites + + + − 110 2# $a Indiana (Cuirassé : BB-50)+ − 368 ## $a Cuirassés $2 rvm − 368 ## $c BB-50 − − Do not record professions or occupations in subfield $c (Other designation). Profession or occupation may be recorded in field 374. + − Record titles of royalty, nobility or religious rank (RDA 9.4.1.4–9.4.1.8) in subfield $d in the form used in the authorized or variant access points.+ − '''Examples:'''+ − − 100 0# $a Alexandre $b VI, $c pape, $d 1431-1503 − 368 ## $d pape $s 1492 $t 1503 − 100 0# $a Jane Seymour, $c reine, épouse d'Henri VIII, roi d'Angleterre, $d 1509?-1537+ − 368 ## $d reine, épouse d'Henri VIII, roi d'Angleterre − − 100 0# $a Jeanne Marie, $c sœur, $d 1926-2013 − 368 ## $d sœur − 100 1# $a Walsh, Joseph-Alexis, $c vicomte, $d 1782-1860+ − 368 ## $d vicomte − − '''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:'''+ − <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+ − (''La première 368 renferme un terme provenant d'un vocabulaire contrôlé mais pas la seconde'')</div>+ − '''Subfield $s – Start period and Subfield $t – End period'''+ − Follow the LC/PCC practice for subfield $s and subfield $t provided in the 373 field+ − '''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''+ − Follow the LC/PCC practice for subfield $u and subfield $v provided in the 046 field+ − [2021-02-23]+ − <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 =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#370_Associated_Place|''Supplement'' <big>⮞</big>]]+ + + + − = 371 Address =+ − '''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 $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''' − Follow the instructions in this Manual for subfield $s and subfield $t provided in the 373 field.+ − + + + − Follow the instructions in this Manual for subfield $u and subfield $v provided in the 046 field.+ − [2021-02-19]+ − <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'''+ − 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 :'''+ − + − 372 ## $a Japon--Histoire $2 rvm+ − − 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:+ − + − 130 #0 $a Bible. $p Nouveau Testament+ − + − Field of activity in 372: − − 372## $a Bible. Nouveau Testament $2 lacnaf − </pre> − + − 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 :'''+ − <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 guidelines in the Manual for subfield $s and subfield $t provided in the 373 field. + + − + − Follow the guidelines in the Manual for subfield $u and subfield $v provided in the 046 field. + + − [2021-02-22]+ − <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''' − 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.+ + − + + − Corporate name in Canadiana:+ − <pre style="font-family:courier new;"> − 110 2# $a Canadiens de Montréal (Équipe de hockey) − </pre> − Authorized access point in 373: − <pre style="font-family:courier new;"> − 373 ## $a Canadiens de Montréal (Équipe de hockey) $2 lacnaf − </pre> − Corporate name in Canadiana: − <pre style="font-family:courier new;"> − 110 1# $a Québec (Province). $b Conseil supérieur de l'éducation. $b Direction de la recherche − </pre> − Authorized access point in 373: − <pre style="font-family:courier new;"> − 373 ## $a Québec (Province). Conseil supérieur de l'éducation. Direction de la recherche $2 lacnaf − </pre> − 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. − + − NAR with 373s with subfield $2 and dates:+ − + − 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+ − − NAR with 373s with different vocabulary sources: − <pre style="font-family:courier new;"> − 373 ## $a Gendarmerie royale du Canada. Liaison Branch $2 lacnaf − 373 ## $a Buffalo State College $2 naf − </pre> − '''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 guidelines in the Manual for subfield $u and subfield $v provided in the 046 field.+ + − [2021-02-19]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]] − = 374 Occupation =+ − − 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.+ − + + − 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.+ + − + − 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.+ − + + − Follow the guidelines in the Guide for subfield $s and subfield $t provided in the 373 field.+ − + − Follow the guidelines in the Guide for subfield $u and subfield $v provided in the 046 field.+ − [2021-02-19]+ − − + − '''PFAN''' − + − Lors de l'enregistrement d'un terme indiquant le sexe, privilégier les termes masculin et féminin. Pour ces termes, ne pas mettre de majuscule ni indiquer la source du terme dans la sous-zone $2. + − When recording a term indicating gender, prefer male and female terms. − Si ni l'un ni l'autre de ces termes n'est approprié ou suffisamment précis, enregistrer un terme ou une expression appropriés en utilisant de préférence un vocabulaire contrôlé, tel que le RVMGD ou le Lexique sur la diversité sexuelle et de genre, en enregistrant la source dans la sous-zone 2. − Par souci de cohérence, mettre une majuscule au premier terme de chaque sous-zone $a pour les termes autres que masculin et féminin. Lorsque les termes ne proviennent pas d'un vocabulaire contrôlé, utiliser la forme au singulier. Privilégier l'emploi de termes plutôt que des codes ISO 5218.+ − When recording a term indicating gender, prefer male and female terms. For these terms, do not controlled vocabulary, such as LCDGT or MeSH, recording the source in subfield $2. + − For consistency, capitalize the first term in each subfield $a for terms other than male and female.+ − When terms do not come from a controlled vocabulary, use a singular form. Prefer use of terms over the ISO 5218 codes. − '''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:'''+ − <pre style="font-family:courier new;"> − 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 − </pre> − '''Subfield $2 – Source of term'''+ + − Codes from the Gender Source Codes list may be recorded in subfield $2 for the 375 field.+ − + − Follow the guidelines in the Manual for subfield $s and subfield $t provided in the 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-02-22] − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement'' <big>⮞</big>]] − = 376 Family information =+ − '''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.+ + − '''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'''+ − 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+ + + − Follow the instructions in this Manual for subfield $s and subfield $t provided in the 373 field.+ + − '''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''+ − Follow the instructions in this Manual for subfield $u and subfield $v provided in the 046 field.+ + − [2021-02-22]+ − <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'''+ − 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 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'''+ − + − + − + − + − 377 ## $a myn+ − 377 #7 $a acr $2 iso639-3+ − <div style="font-family:sans-serif; margin-left:85px;">+ − (''ISO 639-3 code for Achi (acr); assigned a collective code (myn) for Mayan languages in the MARC Code List for Languages'')</div>+ + + + + + − [2021-02-22]<br> − <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 = − 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.+ − + − <pre style="font-family:courier new;"> − 100 1# $a Lennon, John, $d 1940-1980 − 378 ## $q John Winston − 100 1# $a Eliot, T. S. $q (Thomas Stearns), $d 1888-1965+ − 378 ## $q Thomas Stearns − 100 1# $a Guiles, Kay D.+ − 378 ## $q Kay Dean − </pre> − + + + + − Follow the guidelines in the Manual for subfield $u and subfield $v provided in the 046 field.+ − [2021-02-22]+ − + + + − + + + + − '''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.+ − '''Examples:'''+ − <pre style="font-family:courier new;"> − 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 − </pre> − + − 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-02-22]+ − <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 =+ − + + − This field is used to record the RDA elements other distinguishing characteristic of work (RDA 6.6) and other distinguishing characteristic of expression (RDA 6.12). Other characteristics of expressions that are unique to musical works (see 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;">+ − 100 1# $a Dickinson, Emily, $d 1830-1886. $t Because I could not stop for Death − 381 ## $a Fr. 712+ − + − (''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:85px;"> − (''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+ + − 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> − 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. + + − 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. − '''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;">+ − 130 #0 $a Bible. $l Français. $s Bayard. $f 2001 − 381 ## $a Bayard éditions $2 lacnaf+ − <div style="font-family:sans-serif; margin-left:85px;"> − (''Corporate body recorded as other distinguishing characteristic of expression'')</div><br> − − 130 #0 $a Journal of adult education (University of Zambia. Centre for Continuing Education) − 373 ## $a University of Zambia. Centre for Continuing Education $2 naf+ + − 381 ## $a University of Zambia. Centre for Continuing Education $2 naf+ − <div style="font-family:sans-serif; margin-left:85px;"> − − </div> − RDA n'a pas d'élément particulier pour les lieux associés aux expressions, mais la zone 370 sous-zone $f (Autre lieu associé) et la sous-zone $g (Lieu d'origine de l'œuvre ou de l'expression) peuvent être utilisées dans les notices d'autorité pour les expressions. Dans certains cas, des lieux associés aux œuvres ou aux expressions sont considérés comme une autre caractéristique distinctive d'une œuvre ou d'une expression selon RDA et peuvent être enregistrés dans la zone 370, dans la zone 381 ou dans les deux zones. + + − 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. − '''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;"> − 130 #0 $a Ley de Enjuiciamiento Criminal para las Islas de Cuba y Puerto Rico (Cuba; Porto Rico) − 370 ## $f Cuba $f Porto Rico $2 lacnaf+ − − 381 ## $a Cuba $a Porto Rico $2 lacnaf − <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> − Record the RDA element place of origin of work (RDA 6.6) in a 370 field (see Manual, 370 section).+ − 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+ − field, use the 381 field to record the other distinguishing characteristic. Optionally, also record the same information in any other appropriate 3XX field. − + + + − 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, repeat the field. Overall best practice: repeat the field when needed for clarity.+ − '''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''+ − Follow the guidelines in the Manual for subfield $u and subfield $v provided in the 046 field. + + − [2021-02-22]+ − <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 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. − + − [2021-02-22]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#382_Medium_of_Performance|''Supplement'' <big>⮞</big>]]+ + − + + + + − + − Best practice: Encode when available. Create separate 383 fields for different numbering schemes associated with a single work. + − [2021-02-22]+ − <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 =+ − + + − Best practice: Encode when available for works. In case of doubt, do not encode. Do not encode for expressions.+ − − [2021-02-22] − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#384_Key|''Supplement'' <big>⮞</big>]] − − − PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.+ − [2021-02-22]+ − + + + + + + + + − + + + + + − + + + + + + + + + + + + + + + − PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.+ + + − [2021-02-21]+ − + + + + + + + + + + + + − + + + + + + + + + + + + + − + + + + + + + + + + + + + + − When modifying an authority record for another reason, delete any final mark of punctuation in a 4XX field unless it is a part of the data (e.g., a period in an abbreviation) or is called for by the cataloging rules (e.g., a parenthetical qualifier).+ + + + + + + + + − When otherwise modifying NARs or SARs that contain obsolete codes such as subfield $w position zero (0) code “d,” PFAN catalogers should upgrade the NAR to RDA.+ + + + + − Not all 4XX references require justification; see “Justifying variant access points” in the 670 section of this document.+ − Do not make a 4XX that normalizes to the same form as another 4XX on the same authority record or a 1XX on any name authority record. See the section “NACO normalization” in the [https://www.loc.gov/catdir/cpso/dcmz1.pdf/view DCM Z1] Introduction.+ + + + + − Best practice guidelines for RDA:+ + + − <ul>+ − <li>Record variants found in the manifestation being cataloged:+ − <dl>+ − <dd>○ Use cataloger's judgment;</dd>+ − <dd>○ No limitation on the number or form of references;</dd>+ − <dd>○ Instead of or in addition to adding variants, consider providing access by adding 37X fields.+ + + + + − + − <pre style="font-family:courier new;"> − 100 1# $a Bucknum, David W. − 378 ## $q David Walter+ − − </div> − </dd> − </dl> − − + + + + + − <li>Generally provide a variant form 4XX access point for a former 1XX authorized access point, unless the former authorized access point was egregiously incorrect. See the section “Subfield $w – Control subfield” for more information.+ − + + + + + + + + + + + + + + − <li>Generally, do not remove variants unless egregiously incorrect (e.g., a non-Latin script variant that does not represent the same person).+ − <li>If a form found on the manifestation being cataloged includes a variant form of a component of a 4XX variant access point, that form may be used in its entirety as an additional 4XX variant access point, provided that it is not divided into its component parts through the use of subfields.+ − <div>+ − + − + − <p>100 1# $a Faulkner, William, $d 1897-1962. $t Nouvelles. $k Extraits<br> − 400 1# $a Faulkner, William, $d 1897-1962. $t Uncollected stories of William Faulkner<br> − 430 #0 $a Uncollected stories of William Faulkner</p> − <br> − <p> − 110 1# $a États-Unis. $b Bureau of Labor Statistics<br> − 410 2# $a Estados Unidos de América, Buró de Estadísticas Laborales<br> − ''and not''<br> − 410 2# $a Estados Unidos de América. $b Buró de Estadísticas Laborales</p> − <br> − <p> − 110 2# $a Zhongguo yi ke da xue. $b Fu shu di 1 yi yuan<br> − 410 2# $a China Medical University, First Affiliated Hospital<br> − ''and not''<br> − 410 2# $a China Medical University. $b First Affiliated Hospital</p> − − </li> − − When changing the form of a superordinate body, a geographic name, or a personal name in a 1XX, update all of the existing NARs that use that component in a 4XX, unless the 4XX represents the former authorized access point (e.g., $w/2=e). ''Exception:'' Do not apply this instruction in the case of migrated authority records that have not been re-evaluated. − + − When an authorized access point for a person (100) is changed because the person has changed his or her name, record the earlier form of name in a 400 with $w nne if the variant is valid under RDA instructions.+ + + − '''Examples:'''+ − <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;"> − 100 0# $a François, $c pape, $d 1936-<br> − 400 1# $w nne $a Bergoglio, Jorge Mario, $d 1936- − <div style="font-family:sans-serif; margin-left:85px;"> − (''Name changed upon election as pope'') − </div><br> − 100 1# $a Rancic, Giuliana<br> − 400 1# $w nne $a DePandi, Giuliana<br> − <div style="font-family:sans-serif; margin-left:85px;"> − (''Nom changé après le mariage'')</div> − </div> − 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) is changed because of a change in cataloging instructions, record the earlier form in a 4XX using $w. If the variant form is a valid reference under current RDA instructions, use $w nne. If the variant form is not a valid reference under current RDA instructions, use $w nnea.+ + + + − '''Examples:'''+ − <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;"> − 130 #0 $a Bible. $p Matthieu <br> − 430 #0 $w nnea $a Bible. $p N.T. $p Matthieu − <div style="font-family:sans-serif; margin-left:85px;"> − (''Coded "nne" because the variant is valid in RDA'') − </div><br> − 100 1# $a Smith, Jonathan Kennon Thompson, $d 1939-2014<br> − 400 1# $w nne $a Smith, Jonathan Kennon − <div style="font-family:sans-serif; margin-left:85px;"> − (''Coded "nne" because the variant is valid in RDA; 100 form changed based on usage and dates of birth and death added because 100 was being changed'') − </div> <br> − 100 0# $a Périclès, $d environ 495 av. J.-C.-429 av. J.-C.<br> − 400 0# $w nnea $a Périclès, $d ca 495-429 av. J.-C. − <div style="font-family:sans-serif; margin-left:85px;"> − (''Coded "nnea" because the abbreviation "ca." is not valid for period of activity in RDA'') − </div> − </div> − + − PFAN series practice: Transcription of the series statement is mandatory if applicable. Searching for series authority records, providing authorized access points for the series, and the creation and maintenance of series authority records are optional.+ + + + + + + + + − Variant access points may be recorded in any SAR, including those for series-like phrases.+ − 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-02-23] + − <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>]] − = 5XX - See Also From Tracings - General Information =+ − + − When otherwise modifying a NAR that contain codes that are no longer used such as subfield $w position zero (0) code “d” or “f,” PFAN catalogers should upgrade the NAR to RDA.+ − PFAN catalogers applying RDA instructions may use subfield $i in conjunction with subfield $w code “r” for relationship designators. When applying RDA relationship designators in 5XXs, supply terms from Appendix I, J or K; capitalize the initial letter of the term and follow the term with a colon.+ − For information on the use of relationship designators and/or $w codes in a specific 5XX field, see the section in this Manual for that field.+ − + + − Follow the conventions in the authority format for use of subfield $w. Do not supply subfield $w unless a value other than “n” would be appropriate in one of the positions. When supplying subfield $w,+ − give it as the first subfield in the field. Supply character positions preceding, but not succeeding, the value, e.g., − <div style="font-family:courier new; margin-left:50px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">+ − $w a = to indicate a reference from an earlier authorized access point − + − $w r = to indicate that a subfield $i or subfield $4 is used to denote relationship information+ − + + + − '''NARs'''+ − Un rappel de renvoi « voir aussi » (5XX) ne doit pas se normaliser sous la même forme qu'un autre renvoi « voir aussi » dans la même notice d'autorité, sauf si les deux zones 5XX contiennent un indicateur de relation dans la sous-zone $i et que les textes des indicateurs de relation sont différents.+ − '''SARs'''+ + + + + + + + − 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.+ − [2021-02-23]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#5XX_Fields_Tracing_and_References_-_General_Information|''Supplement'' <big>⮞</big>]]+ − = 500 See Also From Tracing - Personal Name =+ − + + − Catalogers may use subfield $i with subfield $w coded “r” when providing relationship links between a personal name and 1) the name of another person, family, or corporate body or 2) the authorized access point for a work or expression. This technique may also be used to relate authorized access points for works and expressions containing personal names. When using a term from Appendix I, J or K in subfield $i, use a capital letter for the first letter of the term and follow the term with a colon.+ + + + + + − '''Examples :'''+ − <pre style="font-family:courier new;"> − 130 #0 $a Yentl (Film) − 500 1# $w r $i Réalisateur de cinéma : $a Streisand, Barbra − 100 1# $a Alcott, Louisa May, $d 1832-1888. $t Little men+ − 500 1# $w r $i Suite de : $a Alcott, Louisa May, $d 1832-1888. $t Little women − </pre> − When recording pseudonymous relationships for personal names when only two authority records are involved, catalogers may either 1) use subfield $i and code “r” in subfield $w or 2) use simple see-also references. For more information on these techniques and instructions on recording multiple pseudonyms (i.e., those involving a 663 field), see the FAQ – LC/PCC RDA Practice for Creating NARs for Persons Who Use Pseudonyms available at: http://www.loc.gov/catdir/cpso/pseud.pdf+ − − Catalogers are reminded that when a variant name (400) and an authorized access point (100) are in conflict an addition should be made to either the 400 or 100 to resolve the conflict (e.g., fuller form of name, date of activity, etc.); the previous practice of changing the 400 to a 500 to resolve the conflict is no longer an option. When catalogers encounter a variant form in a 500 field in the course of updating a NAR, they should resolve the conflict and change the field to a 400. − + − + − + − + − Suivre les instructions fournies dans les [https://drive.google.com/file/d/1URStT5DgcEj52ghmYFq8oCbNXpXhvZX-/view Lignes directrices du PCC pour l'application des indicateurs de relation dans les notices d'autorité de NACO].+ − Follow instructions provided in the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records+ − [2021-02-15]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#510_See_Also_From_Tracing-Corporate_Name|''Supplement'' <big>⮞</big>]]+ + + − + − '''Généralités''' + + − Suivre les instructions fournies dans les [https://drive.google.com/file/d/1URStT5DgcEj52ghmYFq8oCbNXpXhvZX-/view Lignes directrices du PCC pour l'application des indicateurs de relation dans les notices d'autorité de NACO]. + + + − Follow instructions provided in the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records+ + + − See BAC-BAnQ PS 11.13.1.8 for guidance on relating authority records for ongoing conferences.+ − [2021-02-15]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#511_See_Also_From_Tracing-Meeting_Name|''Supplement'' <big>⮞</big>]] − + − '''General'''+ + + − Catalogers may use subfield $i with subfield $w coded "r" when providing relationship links between authorized access points for works or expressions. When supplying RDA Appendix J terms in subfield $i, use a capital letter for the first letter of the term and follow the term with a colon.+ − [2021-02-15]+ + − [[#toc|''Retour au sommaire'' <big>⮝</big>]] | [[PFAN_-_Guide_des_autorit%C3%A9s_de_noms_-_Suppl%C3%A9ment_MARC_21#530_Rappel_de_renvoi_.C2.AB_voir_aussi_.C2.BB_-_Titre_uniforme |''Supplément'' <big>⮞</big>]]+ + + − = 551 Rappel de renvoi « voir aussi » - Nom géographique =+ + − Ne pas utiliser la sous-zone $i avec le code « r » dans la sous-zone $w tant que les indicateurs de relation pour les lieux ne seront pas développés. (RDA a prévu un espace pour l'annexe L.)+ + − [2021-02-10]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#530_See_Also_From_Tracing-Uniform_Title|''Supplement'' <big>⮞</big>]]+ − = 551 See Also From Tracing - Geographic Name =+ − Do not use subfield $i with subfield $w coded “r” until relationship designators for places are developed. (Currently RDA has a placeholder for Appendix L).+ − + − + − + + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#641_Series_Numbering_Peculiarities|''Supplement'' <big>⮞</big>]]+ + − = 642 Series Numbering Example =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#642_Series_Numbering_Example|''Supplement'' <big>⮞</big>]]+ − = 643 Series Place and Publisher/Issuing Body =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#643_Series_Place_and_Publisher.2FIssuing_Body|''Supplement'' <big>⮞</big>]]+ − = 644 Series Analysis Practice =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#644_Series_Analysis_Practice|''Supplement'' <big>⮞</big>]]+ − = 645 Series Tracing Practice =+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#645_Series_Tracing_Practice|''Supplement'' <big>⮞</big>]]+ − = 646 Series Classification Practice =+ − + + − + − '''General''' − The 663 field contains the explanatory text and authorized access points for relationships between a 100 (established name) and other 100s (established names) that cannot be adequately conveyed by one or more simple see also references generated from 500 fields.+ − Generally, this situation occurs when a person uses more than two identities, when more than one person shares an identity with one or more others, or when multiple persons use the same pseudonym independent of each other or as a result of some other arrangement.+ − The text of the 663 may be adjusted to fit extraordinary situations; however, keep the text as simple as possible, allowing the MARC fields and coding to convey the information desired.+ + − Do not use the 663 technique to show relationships between corporate bodies or between persons and corporate bodies.+ − More information on creating NARs for persons with alternate identities is found in the [[Images/f/f3/FAQ – Pratique de LC-PCC pour la création de notices d’autorité de nom pour les personnes qui utilisent des pseudonymes.pdf|FAQ – LC/PCC RDA and AACR2 practice for creating NARs for persons who use pseudonyms]].+ − '''Only two identities'''+ + − When only two NARs are created for a person, the NARs are generally connected with 500 see also references and no 663 field. However, when one of the NARs is for a joint pseudonym or a pseudonym used by several persons working independently of each other, the 663 technique is used.+ − − '''More than two identities - "basic" authorized access point and references'''+ − When more than two authorized access points are created for the same person, identify a “basic” authorized access point using the 663 field technique. This decision is based on the desire to simplify the reference structure and to assist catalogers in determining which name to use as the subject of biographical or critical works. The “basic” authorized access point should be determined by the predominantly used form of name or, lacking sufficient evidence, by choosing the real name of the person as the “basic” form.+ − On the authority record for the “basic” name authority record add 500 see also references with a subfield w coded “nnnc” from all other names used. Justify the 500 in 670 citations according to normal practice. Provide a 663 field listing all the other names with the following text (may be adjusted to fit the situation):+ − <div style="font-family:courier new; 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;">+ − 663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b [established form of name]] $b [established form of − name]] − </div> − On each of the other name authority records, trace a 500 see also reference with subfield $w coded “nnnc” from the “basic” name, justifying that reference in a 670 citation, according to normal practice. Other names may be mentioned in the 670 if it is convenient to do so. Provide a 663 field with the following or similar text (may be adjusted to fit the situation):+ − <div style="font-family:courier new; 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;">+ − 663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b [established form of name chosen as the basic heading] − </div> − When the author uses another new name, create a new name authority record for that name and also add it to the reference structure and 663 listing on the authority record for the “basic” name. References to the new name in the 500 and 663 fields are only added to the “basic” NAR.+ − + − + − "Basic" NAR: − <div style="font-family:courier new; margin-left:50px; 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 1# $a Harris, John, $d 1916-1991 − 500 1# $w nnnc $a Hennessy, Max, $d 1916-1991+ − 500 1# $w nnnc $a Hebden, Mark, $d 1916-1991+ − 663 ## $a Pour les œuvres de cette personnes écrites sous d'autres noms, chercher aussi sous : $b Hebden, Mark, 1916-1991 $b Hennessy, Max, 1916-1991 + − </div> − + − NAR for first 500 on "basic" NAR:+ + + − + − 100 1# $a Hennessy, Max, $d 1916-1991+ − + − 500 1# $w nnnc $a Harris, John, $d 1916-1991 − − 663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b Harris, John, 1916-1991 + + − NAR for second 500 on "basic" NAR:+ − <div style="font-family:courier new; margin-left:50px; 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 1# $a Hebden, Mark, $d 1916-1991 − 500 1# $w nnnc $a Harris, John, $d 1916-1991+ − 663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b Harris, John, 1916-1991+ − </div>+ − </div>+ + + − '''Joint pseudonyms'''+ − A joint pseudonym represents one identity used by two or more persons working in collaboration with each other. If a person uses a joint pseudonym and another name (as found in the catalog), the “basic” authorized access point technique is used.+ + − '''Examples :'''+ − <div style="padding-left:50px;"> − NAR for joint pseudonym: − + − 100 1# $a Phillips, Mark+ − 500 1# $w nnnc $a Garrett, Randall+ − 500 1# $w nnnc $a Janifer, Laurence M.+ − 663 ## $a Pseudonyme conjoint de Randall Garrett et Laurence M. Janifer. Pour les œuvres de ces personnes écrites sous leurs propres noms, chercher aussi sous : $b Garrett, Randell $b Janifer, Laurence M.+ − + + − NAR for first 500 on joint pseudonym NAR:+ − <div style="font-family:courier new; padding-right:25px; margin-left:50px; 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 Garrett, Randall − 500 1# $w nnnc $a Phillips, Mark+ − 663 ## $a Pour les œuvres de cette personne écrites en collaboration avec Laurence M. Janifer, chercher aussi sous : $b Phillips, Mark+ − </div> + + + − NAR for second 500 on joint pseudonym NAR:+ − <div style="font-family:courier new; padding-right:25px; margin-left:50px; 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 Janifer, Laurence M. − 500 1# $w nnnc $a Phillips, Mark − 663 ## $a Pour les œuvres de cette personne écrites en collaboration avec Randall Garrett, chercher aussi sous : $b Phillips, Mark − </div> − </div> + − '''Pseudonyms used by multiple persons''' + − When multiple persons working independently of each other use the same pseudonym and one or more other names (as found in the catalog), the “basic” authorized access point technique is used.+ + − + − <div style="padding-left:50px;"> − NAR for pseudonym used by multiple persons: − <div style="font-family:courier new; margin-left:50px; 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 1# $a Robeson, Kenneth − 500 1# $w nnnc $a Dent, Lester, $d 1904-1959+ + + + − 500 1# $w nnnc $a Goulart, Ron, 1933-+ − […]+ − 663 ## $a Pseudonyme utilisé par plusieurs personnes qui écrivent individuellement. Pour les œuvres de ces personnes écrites sous leurs propres noms ou d'autres noms, chercher aussi sous : $b Dent, Lester, 1904-1959 $b Goulart, Ron, 1933- […]+ − </div> + − NAR for first 500 on pseudonym used by multiple persons NAR:+ + − + − 100 1# $a Dent, Lester, $d 1904-1959+ + + + + + + + − 500 1# $w nnnc $a Robeson, Kenneth+ − 663 ## $a Pour les œuvres de cette personne écrites sous un autre nom, chercher aussi sous : $b Robeson, Kenneth+ + + + − NAR for second 500 on pseudonym used by multiple persons NAR:+ − <div style="font-family:courier new; margin-left:50px; 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 1# $a Goulart, Ron, ‡d 1933- − 500 1# $w nnnc $a Robeson, Kenneth+ + + − 500 1# $w nnnc $a Silva, Joseph, $d 1933-+ + + + + − […]+ − 663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b Robeson, Kenneth $b Silva, Joseph,1933- […]+ − + − + − [2021-02-15]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#663_Complex_See_Also_Reference-Name|''Supplement'' <big>⮞</big>]] − + + + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#665_History_Reference|''Supplement'' <big>⮞</big>]]+ − + + + + − '''Généralités'''<br>+ − Give information of permanent value and general interest that would be useful also to PFAN institutions and outside of PFAN. A representative listing of notes is given below. Generally, wording is recommended but not prescriptive unless specified in the instructions. The separate 667 fields may be given in any order.+ + − + − <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;"> − 667 ## $a N'est pas la même personne [ou œuvre] que : [name or title, Canadiana number]. − 667 ## $a Ne peut être identifié comme étant : [name or title, Canadiana number].+ + − 667 ## $a Réexaminer avant de réutiliser.+ − 667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of+ − undifferentiated name record]. − 667 ## $a Codée "provisoire" car [reason for coding].+ + − 667 ## $a Date de naissance supprimée de toutes les zones suite à la demande de l'auteur, [date updated].+ − 667 ## $a Pour les œuvres parues avant/après [date].+ − <br> − <div style="font-family:sans-serif; margin-left:85px;"> − (''Used for official language changes'')</div> − </div> − See Appendice 1 in this manual for information and instructions about 667 fields added to authority records as part of a special project.+ − + + + + + + − When a person uses two or more identities in manifestations, name authority records may be created for each identity. In the interest of efficiency, catalogers may use a 667 field to list pseudonyms not found in publications instead of creating NARs for these unused pseudonyms. In this case, list the unused pseudonyms in a 667 field following the phrase: “Pseudonymes non trouvés dans les œuvres publiées.”+ − + − <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;"> − 667 ## $a Pseudonymes non trouvés dans les œuvres publiées : Miz Scarlett, SCC et Stevenopolis. − </div> − This note may also be added to an NAR for a person who has multiple NARs for multiple identities when some of the pseudonyms are not found in publications. In this case, list only the unused pseudonyms in the 667 field, and follow appropriate instructions for the other pseudonyms.+ − '''Examples:'''+ − + − 100 1# $a Gorey, Edward, $d 1925-2000 − 500 1# $w nnnc $a Dowdy, Regera, $d 1925-2000+ − 500 1# $w nnnc $a Mude, O., $d 1925-2000+ − 663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b Dowdy, Regera, 1925-2000 […]+ − 667 ## $a Pseudonymes non trouvés dans les œuvres publiées : Drew Dogyear, Wardore Edgy, + + − […]+ − </div> − More information on creating NARs for persons with alternate identities is available in the manual, 663 section, and the [document: Pratique de LC-PCC pour la création de notices d'autorité de noms pour les personnes qui utilisent des pseudonymes.+ − '''NARs for series of conferences, etc. (ÉP de BAC-BAnQ 11.13.1.8.2)'''+ − Add a 667 field on the NAR for the collective conference when there are authority records for both collective and individual instances of an ongoing conference.+ − '''Examples:'''+ − 110 2# $a Veterinary Orthopedic Society. $b Annual Conference+ − 667 ## $a Voir aussi les points d'accès connexes pour les occurrences individuelles de cette conférence, qui comprennent de l'information spécifique sur le numéro, la date ou le lieu de la conférence individuelle.+ + + + + + + − + − Apply these instructions when creating new NARs and revising existing NARs.+ − − <div style="margin-left:16px; text-indent:-16px;">1) Add notes indicating subject cataloging usage when an authorized access point is not appropriate for use as a subject heading for these situations:</div> − <ol>+ − + + − Cette instruction s'applique aux notices d'autorité de noms pour les collectivités représentant la fonction lorsque le nom du titulaire est inclus comme partie du point d'accès autorisé de la collectivité. Voir RDA 11.2.2.18 (Dignitaires gouvernementaux) et 11.2.2.26 (Dignitaires religieux) pour les instructions sur les collectivités. Utiliser cette note 667 dans la notice d'autorité de nom pour la collectivité pour indiquer l'utilisation en indexation :+ + + − This instruction applies to NARS for corporate bodies representing the office when the name of the incumbent is included as part of the authorized access point for the corporate body. See RDA+ − 11.2.2.18 (Government Officials) and 11.2.2.26 (Religious Officials) for instructions on the corporate bodies. Use this 667 note on the NAR for the corporate body to indicate subject cataloging usage: − − <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;"> − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous [personal name heading]. − </div> − Assign value “n” in 008/11 and value “b” in 008/15.+ + + − '''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;"> − 008/11 = n − 008/15 = b+ − 110 1# $a États-Unis. $b Président (1923-1929 : Coolidge)+ − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Coolidge, Calvin, 1872-1933.+ − <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;"> − 008/11 = n − 008/15 = b+ + + − 110 2# $a Église catholique. $b Pape (1503-1513 : Jules II)+ + − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Jules II, pape, 1443-1513.+ − − See also 008/11 and 008/15 in this manual.+ − </li> − <li type="a">'''Earlier/later linear jurisdictional name changes'''+ − La politique d'indexation du RVM est d'employer comme point d'accès matière ou comme subdivision géographique uniquement le dernier nom d'une juridiction politique qui a eu un ou plusieurs noms antérieurs, aussi longtemps que l'identité territoriale demeure essentiellement la même (voir Guide pratique du Répertoire de vedettes-matière de l'Université Laval, 5.14.3.1). Lors de la création d'une notice d'autorité de nom ayant un point d'accès autorisé antérieur/ultérieur pour un lieu dans cette situation, les catalogueurs doivent ajouter une note 667 sur l'utilisation comme vedette-matière dans la notice d'autorité pour le nom antérieur du lieu et modifier les zones 008 appropriés (008/11 et 008/15).+ − The "politique d'indexation du RVM" is to assign as a subject access point or as a geographic subdivision only the latest name of a political jurisdiction that has had one or more earlier names, as long+ − as the territorial identity remains essentially unchanged (see "Guide pratique du Répertoire de vedettes-matière de l'Université Laval", 5.14.3.1). When creating a NAR with an earlier/later authorized access point for a place in in this situation, catalogers must add a 667 subject usage note to the authority record with the earlier place name and adjust the appropriate 008 fields (008/11 and 008/15).<br>+ − + − '''Examples:'''+ − + − 008/11 = n+ + + − 008/15 = b+ − 151 ## $a Ceylan+ + − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Sri Lanka.+ − </div> − </li> − <li type="a">'''NARs for families'''<br>+ − Authorized access points for families are not valid for subject use. In an NAR for a family, 008/11 should be set to value “n” and 008/15 should be set to “b.” Per LAC-BAnQ PS 10.0, when creating an NAR+ − for a family add this 667 field noting subject usage:+ − − <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;"> − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière; utiliser une vedette de nom de famille provenant du RVM. − − − <li type="a">'''NARs for fictitious characters'''<br>+ − Authorized access points for families are not valid for subject use. In an NAR for a family, 008/11 should be set to value “n” and 008/15 should be set to “b.” Per LAC-BAnQ PS 9.0, when creating an NAR+ − for a family add this 667 field noting subject usage: − <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;">+ − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière; utiliser une vedette de personnage fictif provenant du RVM.</div>+ − − + − <div style="margin-left:16px; text-indent:-16px;">2) Add this note to a name authority record for a city section indicating that it is not appropriate for use as a geographic subdivision (see SHM H 835 for more information):</div>+ − <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;">+ − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme subdivision géographique.+ − + − + + + + − 151 ## $a Hollywood (Los Angeles, Calif.) − 667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme subdivision géographique.+ + + + − + + + + + + + + + + + + + + + + + − In an authority record that contains a non-Latin script variant access point, use the 667 field with a note stating: “Le renvoi en écriture non latine n'a pas été évalué.” If there are multiple non-Latin script variant access points, use a note stating: “Les renvois en écriture non latine n'ont pas été évalués.” Assign 008/29 value “b” to indicate that the variant access point is not evaluated.+ − '''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;"> − 008/29 = b − 100 1# $a Moroz, Valentin, $d 1936-+ − 400 1# $a Мороз, В. Я. $q (Валентин Якович), $d 1936-+ − 400 1# $a Мороз, Валентин Якович, $d 1936-+ + − 667 ## $a Les renvois en écriture non latine n'ont pas été évalués.+ − </div> − [2021-02-11]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#667_Nonpublic_General_Note|''Supplement'' <big>⮞</big>]] − = 670 Sources found =+ − '''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. − === Introduction===+ − The purpose of this field is to record information about the name or title represented in the 1XX field. It includes facts that contribute to the identification of the entity, that justify the choice of the name+ − or title and any additional elements used to construct the authorized access point (1XX). The information also justifies, as needed, variant forms of the name or title (4XX), other identifying elements (046, 3XX, − and 678), and clarifies relationships between the 1XX and other entities in the file. − <ol>'''Functions of the 670 field:'''+ − * To record information, from sources (e.g., books, phone calls, websites), in support of the choice and form of the authorized access point, variants, and other identifying elements+ − * To store information that may be used to break a conflict later+ − * To record information on relationships between entities (e.g., a person is the author of a work, a corporate body was absorbed by another corporate body) − * To identify a person with works in diverse subject areas or of diverse forms − * To identify different individuals whose access points must remain identical for now (i.e., undifferentiated personal names) − * To clarify whether different forms of a name or of a title are simply variations or reflect a change in the name or title − * To record research required by the current guidelines − * To facilitate authority and bibliographic file maintenance, i.e., the information in 670 fields aids in making decisions about duplicate authorized access points and misattributions − * To support machine manipulation based on algorithms using information in the 670 − </ol> − Generally, the first 670 field cites the resource for which the authority record is being established, i.e., the resource being cataloged. If the resource being cataloged or consulted provides no information to+ − justify the authorized access point, variants, or other elements recorded in the NAR, see the 675 section of this Manual for instructions on citing the resource in a 675 field. + + − 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.+ − <ol>'''Best practices for 670 fields:'''+ − * In subfield $b, summarize and edit information found as needed to avoid extraneous or repetitive information.+ − * Avoid citing subjective information or information that is of dubious value in identifying an entity within a bibliographic context. − * Exercise caution when recording information about living persons that may be private or controversial in nature. − </ol> − 670 fields in existing NARs may not conform to these guidelines. For example, 670 fields in older NARs may lack subfield $b with justifying information. 670 fields in NARs that were part of a special project may not conform to these guidelines and/or may contain information that seems unusual or incorrect. + − ''Note :'' The examples given throughout the following text have various conventions in regard to punctuation and style. These conventions are '''not prescriptive''' and should be considered as best practices to facilitate the exchange of information in a shared database environment. Catalogers are expected to use judgment and common sense. Punctuation and style need not be consistent from record to record as long as the information is clear and accurate.+ + − === Format of 670 fields ===+ − − '''General''' − À l'exception de l'eszett (ß ou ſʒ) et du symbole euro (€), tous les caractères figurant dans le <https://www.marc21.ca/M21/M9230.html tableau des codes MARC] peuvent être utilisés dans les notices d'autorité ajoutées au fichier d'autorité Canadiana ([http://original.rdatoolkit.org/lcpschp1_lcps1-39.html voir LC-PCC PS pour 1.4]). Lorsque des données provenant d'un site Web sont copiées/collées dans une zone 670, vérifier que tous les caractères peuvent être utilisés dans la notice. Certains caractères non valides ressemblent à ceux qui sont valides. Par exemple, le tiret (–) non valide ressemble au trait d'union (-) valide.+ − With the exception of the eszett (ß or ſʒ) and the euro sign (€), all characters found in the MARC code table (http://www.loc.gov/marc/specifications/specchartables.html) are valid for use in authority records contributed to the LC/NACO Authority File (see LC-PCC PS 1.4). When pasting data from a website into a 670 field, verify that all characters are valid for use in the record. Some non-valid characters resemble those that are valid. For example, the invalid en dash (–) resembles the valid hyphenminus (-). − Si une substitution pour un symbole non reproductible est indiquée entre parenthèses (voir [http://original.rdatoolkit.org/lacbanqpschp1_lacbanqps1-574.html ÉP de BAC-BAnQ pour 1.7.5] et [http://original.rdatoolkit.org/lcpschp1_lcps1-747.html LC-PCC PS pour 1.7.5]), une explication de cette interpolation peut également être fournie.+ + − '''Example:'''+ − <pre style="font-family:courier new;"> − 670 ## $a Poch, Dina K. I [love] my in-laws, 2007 : $b page de titre (I [love] my in-laws; "[love]" est représenté par un symbole de cœur sur la page de titre) − </pre> − Les données doivent être fournies sous forme romanisée. Normalement, il est entendu que le catalogueur a fourni la romanisation; par conséquent, lors de la transcription de données trouvées dans la source sous forme romanisée, ajouter après celle-ci l'expression entre crochets ['''forme romanisée''']. Dans des langues telles que l'arabe et l'hébreu, où les voyelles sont généralement omises dans l'orthographe des textes, le catalogueur fournit les voyelles manquantes lors de la transcription des données. Lors de la transcription de texte qui inclut les voyelles, ajouter après entre parenthèses ['''vocalisé'''] ou ['''en partie vocalisé'''] selon le cas.+ + − Si un catalogueur choisit de fournir des variantes de point d'accès en écriture non latine, les 670 $b doivent contenir aussi bien la transcription du ou des textes en écriture non latine trouvés dans la source que la ou les formes systématiquement romanisées.+ − '''Example:'''+ − <pre style="font-family:courier new;"> − 670 ## $a Moskovskie matematičeskie olimpiady 1993-2005 g., 2006 : $b page de titre (Р.М. Федоров = R.M. Fedorov) − </pre> − Lorsque les notices d'autorité sont créées à l'aide de programmes de génération automatique d'autorités, il est possible que de l'information supplémentaire soit incluse. Ces données peuvent également être formatées d'une manière différente de celle indiquée dans le présent document. En général, ces données doivent être conservées telles qu'elles sont générées afin de maintenir la rentabilité de ce processus, à moins que les données ne prêtent à confusion ou ne provoquent des erreurs de validation. Les noms et les titres pour lesquels les notices d'autorité sont créées constituent l'exception à cette règle. Suivre les instructions de ces sections pour enregistrer ces données.+ − '''Subfield $a – Source citation'''+ + + − A 670 field should include the following data in subfield $a:+ − # Le titre propre de la ressource citée, suffisamment complet pour permettre une identification ultérieure dans un catalogue en ligne. Des abréviations et des points de suspension peuvent être utilisés. Faire précéder un titre générique ou non distinctif du nom du créateur par lequel commencerait le point d'accès autorisé pour l'œuvre. Si le point d'accès autorisé pour l'œuvre est le même que le titre propre plus un qualificatif, il peut être fourni à la place du titre propre pour éviter toute ambiguïté. Lorsque des informations sont fournies dans la sous-zone $a d'une zone 670 pour justifier un point d'accès autorisé ou une variante de point d'accès, suivre les instructions supplémentaires sous Enregistrement des noms et des titres. + − + − <ol>'''Examples:'''+ − <pre style="font-family:courier new;"> − 670 ## $a Barlow, Nadine G. Mars, 2008 : $b page de titre ([data]) − 670 ## $a Socialism (Routledge (Firme)), 2003 : $b $b page de titre ([data])+ − </pre> − </ol> − Also see the guidelines below for specific categories:+ − * '''Multipart monographs.''' If the part is the first part, give the date of publication as an open date.+ − * '''Serials other than monographic series.''' Generally, use a chronological designation instead of a publication date. If there is no designation date, use the numeric designation and the date of publication. Indicate, following the designation statement, if a “surrogate” was used. − <ol>+ − <pre style="font-family:courier new;"> − 670 ## $a The Verdict, February 1975 : $b page de titre ([data]) − not − 670 ## $a The Verdict, vol. 2, no. 1 (February 1975) : $b page de titre ([data]) − 670 ## $a Studies in Confederate history, No. 1 (1966), substitut : $b couverture ([data]) + − not − 670 ## $a Studies in Confederate history, 1966, substitut : $b couverture ([data]) − </pre> − </ol> − * '''Integrating resources.''' Apply the instructions at RDA 2.2.2.4.2 for source of the title proper of a website. Identify the iteration from which information was taken (e.g., “viewed on”dates for updating websites, update number or release number for updating loose-leafs).+ − <ol> − <pre style="font-family:courier new;"> − 670 ## $a Internet Broadway database, consulté le 21 janvier 2003 : $b about IBDB (League of American Theatres and Producers) − </pre> − </ol> − '''Subfield $b – Information found'''+ + − A 670 field should include the following data in subfield $b:+ + − # The specific location(s) of the information found. For multipart resources with numbered parts, provide the designation of the part and the location within the part (e.g., v. 6, page 10; map recto, label). Abbreviations may be used (e.g., t.p., v. 6).+ − # Information found. Following the location, cite the information found there, enclosed in parentheses. As appropriate, give multiple occurrences of information from the same source following the location of the information. − <ol> − '''Examples:''' − <pre style="font-family:courier new;"> − 670 ## $a The complete guide to creating enduring festivals, 2015 : $b page de titre (Dr. Ros Derrett, OAM) page xi (Roslyn Derrett) − 670 ## $a Da real world, 1999 : $b conteneur (Beyoncé) − 670 ## $a The World Book encyclopedia, 2010 : $b v. 17, p. 106 (Sand, George ; 1804-1876; nom de plume de Amantine-Lucile-Aurore Dupin)+ − + − − Also see the guidelines below for specific categories:+ − * '''CIP.''' [à venir] − * '''Internet resources.''' For websites, provide the name of the location within the website if appropriate (e.g., about us; history, timeline; government, executive branch).+ − <ol> − <pre style="font-family:courier new;"> − 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) − </pre> − </ol> − * '''Multiple locations within a resource.''' − <ol> − '''CIP et ressource publiée.''' Lorsqu'on ajoute de nouvelles informations à une zone 670 créée pour un CIP, indiquer que les nouvelles informations proviennent de la ressource publiée. − <pre style="font-family:courier new;"> − [Exemples à venir] − </pre> − '''NARs.''' For NARs, generally, use “etc.” to avoid giving more than two locations or a sequence of locations (e.g., p. 316, etc., for sequence p. 316-325, 329-331). − <pre style="font-family:courier new;"> − 670 ## $a Drevon, André. Alice Milliat, 2005 : $b page de titre (Alice Milliat) p. 9, etc. (née Alice Joséphine Marie Million le 5 mai 1884 à Nantes; morte le 19 mai 1957; athlète féminine) − </pre> − '''SARs.''' For SARs, always give each location separately. − ''PFAN series practice:'' In post-cataloging authority work without the piece in hand, use the location “ressource non disponible.” If the piece is examined again and the authority record is updated, it is allowable to edit the corresponding 670 field to provide a location and additional forms of series titles as needed. − <pre style="font-family:courier new;"> − 670 ## $a From child to adult, 1970 : $b ressource non disponible (American Museum sourcebooks in anthropology) − </pre> − </ol> − '''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the information'''+ − Suivre les directives du Guide pour les sous-zones $u et $v présentées à la zone 046.+ − Follow the LC/PCC practice for subfield $u and subfield $v provided in the 046 field.+ + + − Les catalogueurs peuvent facultativement fournir un identificateur de ressource uniforme (URI) dans la sous-zone $u de la zone 670 pour établir un lien avec la ressource citée si celle-ci contient des informations importantes sur l'entité établie qui ne peuvent être citées succinctement dans la notice d'autorité. Noter que l'utilisation d'un URI dans la zone 670 $u ne supplée pas à l'obligation de citer dans les sous-zones $a et $b de la zone 670 les données pertinentes nécessaires pour justifier le point d'accès autorisé (y compris les ajouts) ou les variantes (cette information continuera d'être disponible si le site change ou disparaît). Toutefois, les informations trouvées dans les sources en ligne peuvent être ajoutées aux zones 046 ou 3XX avec les citations appropriées dans les sous-zones $v et $u et ne pas être répétées dans une 670 lorsque ces informations ne sont pas utilisées dans une 1XX ou une 4XX. Si une URI est incluse dans une 670, elle doit être indiquée dans la sous-zone $u.+ − 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. − '''Example:'''+ − − 670 ## $a British Oceanographic Data Centre, consulté le 23 novembre 2009 : $b About us (British Oceanographic Data Centre, National Environment Research Council; BODC, is a national facility for looking after and distributing data concerning the marine environment) $u [http ://www.bodc.ac.uk/ http ://www.bodc.ac.uk/] − </pre> − === Recording names and titles ===+ − Record names or series titles used in the authorized access point or variant access points in full, as they appear in the source, without abbreviation by the cataloger.+ + + + − When preparing an authority record for the text of a law or a subject compilation of laws, if a source being cited contains an official short title or citation title, cite that title, preceded by the term+ − “citation title” and its exact location. − <ol> − '''Example:''' − <pre style="font-family:courier new;"> − 670 ## $a Workers' compensation law of the state of North Carolina, c1980 : $b page de titre (Workers' compensation law of the state of North Carolina) titre de référence, p. 49 (The North Carolina Workers' Compensation Act) − </pre> − </ol> − 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+ − subfield $b may be omitted, provided no important information is lost.+ + − If information about an earlier or later name or title is found in the same source as the name or title in the authorized access point, give all the information in the 670 field. Do not separate the+ − information about the earlier or later name or title in order to give it in a 675 field. − <ol> − '''Example:''' − <pre style="font-family:courier new;"> − 670 ## $a Strafvollzug, 1985 : $b page de titre (Rechtsgeschichte) p. 2 (Suite de : Veröffentlichungen / Justizministerium Nordrhein-Westfalen) − </pre> − </ol> − + + + − To facilitate international contribution and use of authority records, when recording dates, generally use the spelled out or [https://www.noslangues-ourlanguages.gc.ca/fr/cles-de-la-redaction/mois#2 abbreviated] forms for months. (For dates recorded using automated authority generation programs, see the Format of 670 fields section of this document.) Do not change the style of dates in existing records. As a best practice, if a date is not included in subfield $d of the 100 field, consider adding a 046 field if dates are available.+ − + + + − Justify names or titles given as variant access points by information cited from sources. However, justification is not required in the following cases:+ − # Variant access points made on the basis of the cataloger's awareness of different romanizations or orthographies;+ − # A variant title derived from the resource being cataloged, from other resources cataloged under the same access point, or from information in standard reference sources;+ − # References for authorized access points of corporate bodies reflecting changes due to national orthographic reform, changes in names due to an official language change, or changes involving only a parent body to which the body being established is subordinate.+ − # Optional references from AACR2 or pre-AACR 2 forms on SARs and on retrospective NARs.+ − === Justifying other elements ===+ − Information recorded in the 046, 3XX, or 678 field of the authority record should generally be justified unless it is otherwise obvious from information recorded in subfield $a of a 670 citation or it can+ − be easily inferred from other identifying elements recorded, including the preferred name.+ + − For the 046 field and many of the 3XX fields, a subfield $u or subfield $v recorded in the same field may be used instead of or in addition to a 670. See the 046 section of this document for guidelines+ − on subfield $u and subfield $v.+ + + − === Recording other data ===+ − + − Use judgment to determine how much data to record in the authority record. Do not abbreviate or translate attributes such as title of the person (RDA 9.4) that appear in conjunction with personal names in statements of responsibility and that potentially could be used as part of the access point. Other data may be abbreviated or summarized. Generally informally translate other data from foreign languages into English, paraphrasing or summarizing as convenient. + − + − Use judgment to determine how much data other than forms of the title/phrase to record in the permanent authority record. Numbering and names of issuing bodies are not required but may be given. − === Special types of citations ===+ − The most commonly occurring citations are listed below. If these are not appropriate, devise others as needed.+ − '''Canadiana'''+ − When converting information found in obsolete or non-active MARC fields (e.g., 664, 665, 666) into a 670 note, cite the LC/NAF in a citation such as those provided in the examples below:+ − <pre style="font-family:courier new;"> − 670 ## $a Information convertie à partir d'une zone 665 dans cette notice, [date of conversion] $b ([data converted from 665 field]) − 670 ## $a Information de la zone 665 anciennement dans cette notice ([data moved from 665 field])+ − </pre> − + + + + + + − La façon de citer ces fichiers dans la zone 670 est la suivante :+ − The way to cite these files in zone 670 is as follows:+ − + − 670 ## $a LC/NAF, [date de la recherche] $b (point d'accès : [data]; variantes : [data]) − </pre> − ''Note :'' Le fichier LC/NAF a aussi été cité antérieurement sous d'autres noms, par exemple Base de données LC/NACO et Fichier de LC/NACO.+ + + + + + − + − 670 ## $a OCLC, [date de la recherche] $b (point d'accès : [données]; usage: [données]) − 670 ## $a Fichier interne de BAnQ, [date de la recherche] $b (point d'accès : [données]; variantes : [données])+ − </pre> − + − '''Notices d'autorité de noms.''' <br> − Indiquer la date de la recherche, en utilisant les noms de mois ou leurs abréviations. Entre parenthèses, précédé par la mention '''point d'accès :''' ou '''points d'accès :''' , mentionner le ou les points d'accès trouvés, même si le point d'accès autorisé actuel est identique. S'il est jugé utile de mentionner une ou plusieurs variantes de point d'accès trouvées dans une notice d'autorité, les mentionner en les faisant précéder de la mention '''variante :''' ou '''variantes :'''. − Si différentes formes du nom apparaissent dans les notices bibliographiques, enregistrer le point d'accès ainsi que toutes les formes trouvées, y compris les formes identiques au point d'accès autorisé. Séparer le point d'accès des autres formes de nom et faire précéder les autres formes d'une mention appropriée, par exemple, '''usage :''', '''forme non transcrite :''' ou '''formes non transcrites :'''.+ − Ne pas citer les notices bibliographiques ou l'emplacement exact des variations trouvées.+ + + + + + + + + + + + + + + + + + + + + + − + − S'agissant des notices bibliographiques, '''forme non transcrite''' (ou '''formes non transcrites''') désigne une forme de nom qui ne correspond pas nécessairement à une forme transcrite. Par exemple, dans les notices RCAA2, le nom d'un éditeur qui figure sur la ressource comme « ABC Publishing Company" pourrait avoir été enregistré dans la mention de publication sous la forme "ABC Pub. Co ». Normalement, il n'est pas nécessaire de citer une telle forme dans une zone 670.+ + − <pre style="font-family:courier new;">+ − 670 ## $a OCLC, 7 août 2020 $b (points d'accès : Riva, J.; Riva, J. (John), 1929- ; Riva, John; Riva, John, 1929- ; Riva, John F.; Riva, John Fioretto Valder; usage : John Riva [forme prédominante]; J. Riva; John F. Riva) − − 670 ## $a LC/NAF, 7 janvier 2020 $b (point d'accès : Schumann, Clara, $d 1819-1896; variantes : Shuman, Klara, 1819-1896; Shūman, Kurara, 1819-1896; Vik, Klara, 1819-1896; Wieck-Schumann, Clara, 1819-1896) − </pre> − + − Indiquer la date de la recherche, en utilisant les noms de mois ou leurs abréviations, suivie de la citation de la notice bibliographique. Entre parenthèses, indiquer la mention de la collection qui se trouve dans cette notice.+ + + + + + + + + + + − + − 670 ## $a OCLC, 27 janv. 2021, Les Déchets ménagers, c1980 $b (Les Cahiers de l'AGHTM) − </pre> − − + + + + + − Si un point d'accès est trouvé dans un catalogue ou une base de données en ligne, utiliser son jugement pour créer une citation 670. Commencer la zone 670 par une désignation du catalogue ou de la base de données dans laquelle ces autres notices bibliographiques ont été trouvées. Il n'y a pas de formulation prescrite pour ces citations; des exemples sont donnés ci-dessous :+ − <pre style="font-family:courier new;">+ − 670 ## $a NUC pre-56 $b ([données]) − 670 ## $a Catalogue de BAnQ, , [date] $b ([données]) − 670 ## $a BnF dans VIAF, [date] $b ([données]) − 670 ## $a Autorités BnF, [date] $b ([données]) − 670 ## $a SUDOC, [date] $b ([données]) − 670 ## $a Fichier ISNI de BAnQ, [date] $b ([données]) − 670 ## $a Advitam, [date] $b ([données]) − </pre> − + + + + + + + + + + + + + + + + + + − Indiquer le nom de la base de données et la date de la recherche dans la sous-zone $a. Dans la sous-zone $b, indiquer le ou les noms de l'entité, le type d'entité, la désignation ou la classe de l'élément (par exemple, ADM1, PPL, civil), les coordonnées et le nom du lieu plus vaste, s'il y a lieu. (D'autres informations pertinentes peuvent également être fournies.) Les noms de variantes (y compris les noms en caractères non latins) peuvent être donnés dans une seule liste, comme indiqué ci-dessous. Si possible, utiliser le signe des degrés (et non le zéro en exposant) pour indiquer les degrés, utiliser la lettre modificative prime pour les minutes et la lettre modificative double prime pour les secondes.+ − + − 670 ## $a Base de données toponymiques du Canada, consultée le 4 décembre 2020 $b (nom : Avonmore; lieu : Stormont; province : Ontario; terme concis : UNP-Lieu non organisé; terme générique : localité; latitude - longitude : 45° 10ʹ 17ʺ N, 74° 58ʹ 2ʺ W; 45.17152, -74.96713) − 670 ## $a Banque de noms de lieux du Québec, consultée le 3 septembre 2020 $b (Rouville; type d'entité : municipalité régionale de comté; établie en janvier 1982, la MRC de Rouville a succédé à l'ancienne municipalité du comté de Rouville d'où elle tire son nom; coordonnées : latitude nord 45° 26ʹ 00ʺ, longitude ouest 73° 03ʹ 00ʺ; coordonnées décimales : -73.05, 45.43333)+ − 670 ## $a GNIS, consulté le 5 mai 2016 $b (Allegany County; civil, 39°37ʹ17ʺN 078°41ʹ56ʺW, situé au Maryland; variante : Alligany County)+ − 670 ## $a GEOnet, consulté le 12 avril 2014 $b (Bellinzona [forme approuvée]; PPLA à Ticino, Suisse, 46°11ʹ43ʺN, 009 01ʹ22ʺE; il existe aussi un district du même nom à Ticino)+ + + + − 670 ## $a GEOnet, consulté le 4 mai 2016 $b (Taitung [forme conventionnelle], Taitung County [forme conventionnelle], Taidong [forme approuvée], Taidong Xian [forme approuvée]; ADM1 àTaiwan, 22°53ʹ01ʺN 121°02ʹ54ʺE; variantes : Taidong Sian; T'ai-tung; T'aitung Hsien; écriture non latine : 臺東縣; 臺東)+ − </pre> − + − Indiquer la source non bibliographique, la date et les informations. La source peut être indiquée de manière spécifique (« Lettre de l'auteur » , « Appel téléphonique à l'éditeur » , etc.) ou en termes généraux (« Information de l'auteur » , « Information de l'éditeur » , etc.). Lorsqu'on indique une source spécifique, il n'est pas nécessaire de montrer comment l'information a été reçue, par exemple, que la lettre a été reçue par télécopieur plutôt que par courrier. Lorsqu'un appel téléphonique à un éditeur, une agence ou une organisation est cité, il convient généralement de donner le nom du groupe appelé, plutôt que le titre ou le nom de la personne contactée.+ − <pre style="font-family:courier new;">+ − 670 ## $a Appel téléphonique à H. Jones, 31 janvier 1992 $b (Harry Jones est le vrai nom de Lionel Jones) − 670 ## $a Lettre de l'auteur, 29 mai 1994 $b (la date de naissance correcte pour ______________ est le 14 octobre 1950)+ − 670 ## $a Information de l'éditeur, 6 février 1991 $b (le deuxième prénom de James Allan est Stephen, pas Steven)+ − 670 ## $a Courriel de l'éditeur, 6 avril 2016 $b (__________)+ − </pre>+ − '''Citations pour les notices d'autorité de collections de rééditions'''+ + − Si une notice d'autorité de collection concerne uniquement une réédition, commencer la 670 par le terme correspondant au type de réédition et une barre oblique. Ne pas inclure une 670 pour une réédition si la notice d'autorité sujet couvre à la fois l'original et une ou plusieurs rééditions. Ne pas ajouter de zones 670 supplémentaires pour d'autres types de rééditions cataloguées ultérieurement. (Voir 64X Traitement de la collection, Rééditions pour plus d'informations sur les rééditions).+ − <pre style="font-family:courier new;">+ − 670 ## $a Édition en gros caractères/La diligence du fou, c1989 : $b page de titre du CIP (Un roman de l'Ouest d'Evans) − </pre> − '''Citations pour les notices d'autorité de noms indifférenciés'''+ + − Pour des informations sur les citations existantes dans les notices d'autorité de noms indifférenciées, voir la section 008/32 Nom de personne indifférencié dans ce Guide.+ − [2021-02-26]+ − <br>[[#toc|''Retour au sommaire'' <big>⮝</big>]] | [[PFAN_-_Guide_des_autorit%C3%A9s_de_noms_-_Suppl%C3%A9ment_MARC_21#670_Source_des_donn.C3.A9es |''Supplément'' <big>⮞</big>]]+ − + − = 672 Title related to the entity =+ − + + + − The 672 field may be used to record a title that is related to the entity represented by the 100, 110, 111, or 151 in the name authority record. + − For example, in an authority record for a corporate body, 672 fields may be used to record titles for which the corporate body is a creator, issuing body, or subject. The primary purpose of the 672 field is to document that there is a relationship between the 1XX entity and the title recorded in the 672 field.+ + + − Use of the 672 field does not negate the need to use the 670 field for the title for which the authority record is being created, nor to use the 670 fields to justify information recorded in the 1XX and 4XX such as preferred and variant forms of name.+ + + − New 672 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 672 fields when inputting new 672 fields.+ + − Non-Latin script elements should be given in romanized form.+ − A title recorded in a 672 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 672 field.+ + − '''Examples:'''+ − <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;">+ − + − 672 #3 $a La consolation<br> − 672 #0 $a Yeux noirs − <br> − <div style="font-family:sans-serif;">(''672 fields with titles proper'')</div> − + − 100 1# $a Boyer, Frédéric+ − 672 #0 $a Cervantes − − − <br>+ − 111 2# $a Concile du Vatican $n (2e : $d 1962-1965 : $c Basilica di San Pietro in Vaticano) − 672 #0 $a Constitutio de sacra liturgia − <br> − <div style="font-family:sans-serif;">(''672 field with preferred title'')</div> − <br>+ − 151 ## $a Espagne − 672 #0 $a Llei d'enjudiciament civil i normes complementàries − <br> − <div style="font-family:sans-serif;">(''672 field with variant title for the work associated with the Catalan expressionof the work and date of expression'')</div> − </div> − '''Subfield $b – Remainder of title'''+ − When recording a title proper, subfield $b may be used to record the other title information or parallel title proper to eliminate confusion for titles needing further identification.+ + − '''Examples:'''+ − <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;"> − 672 #3 $a La rivière $b initiations outaouaises − <br> − <div style="font-family:sans-serif;">(''Subfield $b contains other title information'')</div> − <br>+ − 672 #4 $a Las estrellas $b Stars − <br> − <div style="font-family:sans-serif;">(''Subfield $b contains parallel title proper'')</div> − </div> − '''Subfield $f – Date'''+ − Subfield $f is used to record a date appropriate to the entity recorded in $a (e.g., use date of work for a preferred title and date of publication for a title proper). Do not use brackets in $f when recording a supplied date of publication or production. Do not give a date of distribution, date of manufacture, or copyright date in $f.+ − '''Examples:'''+ − + − 672 for work:<br> − 672 #0 $a Amor en los tiempos del cólera $f 1985 − − − <br>+ − 672 for expression:<br>+ − 672 #2 $a L'amour aux temps du choléra $f 1987 − <br> − <div style="font-family:sans-serif;">(''Date of French expression of Amor en los tiempos del cólera'')</div> − <br>+ − 672 for manifestation:<br> − 672 #0 $a Miłość w czasach zarazy $f 2005 − <br> − <div style="font-family:sans-serif;">(''Date of publication of manifestation of Polish expression of Amor en los tiempos del cólera'')</div> − </div> − '''Subfield $w – Bibliographic record control number'''+ − Subfield $w is used to record bibliographic record control numbers (e.g., 001, 010, and 016 fields in bibliographic records). It is recommended that catalogers provide $w when readily available. Subfield $w should be repeated for each instance of a separate control number (e.g., an LCCN and an OCLC record number should be provided in separate subfields). For further instructions on inputting record control numbers, see the subfield $w section within the CONSER Editing Guide (CEG) – Section E.+ + + − MARC 21 Format for Serials as Applied within CONSER – Variable Data Fields – 76X-78X Linking Entries – Linking Entry Fields General Information.+ − Note: subfield $w should only be used with titles for the manifestation.+ + − '''Example:'''+ − [in $w “#” = space input by cataloger]+ − <pre style="font-family:courier new;"> − 672 #0 $a Bread and other bakery products industry $w (DLC)###88646267 $w (OCoLC)3774505 $w (CaOONL)84079116XE − </pre> − [2020-12-14] − − + − '''General''' − The 673 field may be used to record a title that is not related to the entity represented by the 100, 110, 111, or 151 in the name authority record. For example, in an authority record for a person, the 673 may be used to record the titles of works written by a different person with a similar name. The primary purpose of the 673 field is to document that there is no relationship between the 1XX entity and the title recorded in the 673 field.+ − Use of the 673 field does not negate the need to use the 675 field as described in the 675 section of this Guide.+ − New 673 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 673 fields when inputting new 673 fields.+ − Non-Latin script elements should be given in romanized form.+ − A title recorded in a 673 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 673 field. For specific subfields in the 673 field, apply the same instructions given in the [[PFAN - Name Authority Manual#672 Title related to the entity|672 section of this Manual]].+ − '''Examples:'''+ − + − − 100 1# $a Boyer, Frédéric, $d 1961- − 672 #0 $a Cervantes $f 1977 − <br> − <div style="font-family:sans-serif;">(''Title proper associated with different Frédéric Boyer'')</div> − <br>+ − 110 2# $a National Gallery of Art (É.-U.) − 673 #0 $a Paintings and drawings on the backs of National Gallery pictures $w (DLC)### 47008205 $w (OCoLC)1654530 − <br> − <div style="font-family:sans-serif;">(''Title proper associated with the National Gallery in London'')</div> − </div> − BUT NOT+ − <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;">+ − 110 2# $a National Gallery of Art (É.-U.)+ − 673 #4 $a Impressed by light : $b British photographs from paper negatives, 1840-1860 − <br> − <div style="font-family:sans-serif;">(''Although the National of Art is not the creator, it is the publisher so this title should be record in a 672'')</div> − </div> − [2021-02-25]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#673_Title_Not_Related_to_the_Entity|''Supplement'' <big>⮞</big>]] − = 675 Sources not found =+ − '''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.+ − In April 2012 this field was redefined as: “Citation for a consulted source in which no information is found related in any manner to the entity represented by the authority record or related entities.” PFAN catalogers are not required to change any existing 675 fields simply to meet this new definition.+ − When creating a new NAR always cite the resource being cataloged in the 675 field if the item being cataloged provides no information related in any manner to the entity represented in the authority record. Also cite in the 675 field other sources consulted that contain no information, when that very lack of information is considered worth recording for future users of the authority record.+ − '''Examples:'''+ − <pre style="font-family:courier new;"> − 675 ## $a Oxford classical dictionary, 1996 − 675 ## $a GEOnet, consulté le 2 avril 2014 − </pre> − + + + − [2020-12-14]+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#675_Source_Data_Not_Found|''Supplement'' <big>⮞</big>]]+ − + − + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − + − 678 0# $a Joseph Smith, Jr. (1805-1844) était un prophète mormon et le fondateur de l'Église de Jésus-Christ des saints des derniers jours.+ − </pre> − <div style="font-family:courier new; padding-left:75px; margin-top:0px; padding-top:10px; padding-right:25px; text-indent:-60px; border:1px solid #eaecf0; background-color:#f8f9fa;">+ − 678 1# $a L'Organisation du traité de l'Atlantique Nord (OTAN) est une alliance politique et militaire créée par la signature du Traité de l'Atlantique Nord, le 4 avril 1949. Elle regroupe des pays membres d'Amérique du Nord et d'Europe. Depuis 1999, plusieurs pays anciennement membres du Pacte de Varsovie ont rejoint l'OTAN, y compris la Hongrie, la Bulgarie et la Roumanie. D'autres pays non-membres participent aux programmes de l'OTAN tels que le Partenariat pour la paix. − In anticipation of LAC building the file in WMS and the batch addition of authority records from other institutions, the contents of all 665 fields in LAC and BAnQ records have been moved to 678 field. The original 665 field may have contained instructions on the access point(s) to be used as author and subject heading :+ − '''Example:'''+ − + − 151 ## Cascapédia (Québec) − − 678 1# Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules. Comme auteur, on utilise : Cascapédia (Québec) ; Cascapédia-Saint-Jules (Québec) ; Grande-Cascapédia (Cascapédia-Saint-Jules, Québec) ; Saint-Jules (Cascapédia-Saint-Jules, Québec). Comme vedette-matière, on utilise Cascapédia-Saint-Jules (Québec). − − − Delete these instructions in 678 field if they have been retained. Consider adding a 667 field as a subject heading if applicable. − + − <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;">+ − 151 ## Cascapédia (Québec) − <div style="padding-left:60px; margin-top:0px; padding-top:0px; padding-right: 20px; text-indent:-60px;"> − 667 ## UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Cascapédia-Saint-Jules (Québec). − 678 1# Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules. − </div> − </div> − + + + − Generally, a 678 field must be justified by a 670 field. If it is not justified and its contents are appropriate for a biographical or historical note, retain the field and add a 670 note citing the internal file of the institution that provided 678 field as follows :+ + − 670 ## Fichier interne de [ [[PFAN_-_Francophone_Name_Authority_Program#Participating_Libraries|abréviation de la bibliothèque participante]] ], [date de consultation de Canadiana] …+ − '''Example :'''+ − <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;">+ − <div style="padding-left:60px; margin-top:0px; padding-top:0px; padding-right:20px; text-indent:-60px;"> − 670 ## Fichier interne de BAC, 29 octobre 2020 $b (établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail) − − 678 1# Établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail. − − If the record has been modified after being migrated, the record history must be consulted to determine who originally added zone 678.+ − '''Example :''' − <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;"> − <div style="font-family:sans-serif;">Existing Field 678 which will be deleted as the content is not appropriate for a biographical note.</div> − 678 1# Né le 6 juin 1973. − − <div style="font-family:sans-serif;">670 field added:</div> − 670 ## Fichier interne de l'ULaval, 29 octobre 2020 $b (né le 6 juin 1973) − </div> − − '''Repeatability:''' − − Do not repeat this field. − − [2020-12-14] − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#678_Biographical_or_Historical_Data|''Supplement'' <big>⮞</big>]] − − = 7XX Heading linking entries = − '''''Note:''''' This section does not apply to the 781 field used in 151 name authority records to provide geographic subdivision information. See Manual, 781 section, for instructions for that field. − − '''General''' − − The use of an established heading linking entry 7XX field in an NAR or SAR is limited to recording the authorized access point from a national bibliography or in a separate national authority file or a separate equivalence. − − The form of heading in a 7XX field may match the 1XX form or a 4XX form in the same authority record. This is appropriate when the 7XX field form represents a form found in a different authority file than Canadiana. − − '''Example:''' − <pre style="font-family:courier new;"> − 100 1# $a Dion, Céline − 700 10 $a Dion, Céline $0 (DLC)n 87834212 − </pre> − − The source of the heading in the 7XX field may be specified using either second indicator value “7” with subfield $2 or a second indicator value that specifies the source. For access points coming from the LC/NAF file, prefer the second indicator with the value "0". − − [2021-02-18] − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]] − − = 781 Subdivision linking entry = − '''''PFAN optional practice:''''' − − For a geographic name heading that may also be used as a geographic subdivision, determine the form in which the heading is to be used as a geographic subdivision following the guidelines in instruction sheet [https://www.loc.gov/aba/publications/FreeSHM/H0830.pdf H 830 of the ''Subject Headings Manual'']. Enter the text of the geographic subdivision form in a 781 field with second indicator 0. For a geographic heading that is used directly, such as a country, enter the data in a single $z subfield. For a geographic heading that is used indirectly through a larger geographic entity, such as a city, enter the data in two successive $z subfields. Use no other subfields. Make no changes to values in bytes of the 008. − − '''Examples :''' − <pre style="font-family:courier new;"> − 151 ## $a France − 781 #6 $z France − − 151 ## $a Paris (France) − 781 #6 $z France $z Paris − − 151 ## $a Lycie + + + + − + Line 2,483:
Line 3,422: − + − − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→4XX - See From Tracings - General Information
{{In use| 24 h (Currently being edited by N. Mainville, LAC, 8 mars)}}
<!--{{In use| 24 h (Currently being edited by N. Mainville, LAC, )}}-->
[[fr:PFAN - Guide des autorités de noms]]
[[fr:PFAN - Guide des autorités de noms]]
{{Template:PFAN Tabs}}
{{Template:PFAN Tabs}}
= Introduction =
= Introduction =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
=== Name Authority Records ===
=== Name Authority Records ===
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
=== Series Authority Records ===
=== Series Authority Records ===
<!--<span style="color:red">''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.</span>-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
[2021-11-03] <!--(2021-10-27)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
= Fixed Fields =
= Fixed Fields =
== 008/10 Descriptive cataloging code ==
== 008/10 Descriptive cataloging code ==
When an existing NAR using code “a”, “b”, “c”, or “d” is modified in any way, evaluate the NAR and re-code it to RDA, changing the 008/10 code accordingly.
When an existing NAR using code “a”, “b”, “c”, or “d” is modified in any way, evaluate the NAR and re-code it to RDA, changing the 008/10 code accordingly.
Exception 1: If an existing NAR using code “c” is modified only to change or add a 5XX field, catalogers are strongly encouraged, but not required, to evaluate the NAR and re-code it to RDA,
If an existing NAR using code “c” is modified only to change or add a 5XX field, catalogers are strongly encouraged, but not required, to evaluate the NAR and re-code it to RDA,
changing the 008/10 code accordingly.
changing the 008/10 code accordingly.
Exception 2: Existing undifferentiated name authority records coded 008/10 “c” may be modified to remove one or more identities in order to create differentiated RDA authority records. When modifying
Existing undifferentiated name authority records coded 008/10 “c” may be modified to remove one or more identities in order to create differentiated RDA authority records. When modifying
an existing undifferentiated name authority record for this purpose, the updated undifferentiated name authority record must retain the existing 008/10 code.
an existing undifferentiated name authority record for this purpose, the updated undifferentiated name authority record must retain the existing 008/10 code.
[2021-02-19]
[2021-02-19]<!--(2021-02-24)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F10 Descriptive Cataloging Rules|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F10 Descriptive Cataloging Rules|''Supplement'' <big>⮞</big>]]
== 008/11 Subject heading system/thesaurus ==
== 008/11 Subject heading system/thesaurus ==
'''General'''
'''General'''
When applying RDA Chapter 9 for fictitious characters and RDA Chapiter 10 for family names assure that the NAR 008/11 is set to "n."
When applying RDA Chapter 9 for fictitious characters and RDA Chapiter 10 for family names assure that the NAR 008/11 is set to "n".
'''Corporate names for high government and religious officials'''
'''Corporate names for high government and religious officials'''
Assign value "n" (Not applicable) to name authority records for corporate names representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the authorized access point. Also assign value "b" in 008/15, and make a 667 note indicating the form of the access point used in subject cataloging.
Assign value "n" (Not applicable) to name authority records for corporate names representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the authorized access point. Also assign value "b" in 008/15, and make a 667 note indicating the form of the access point used in subject cataloging.
''Examples of corporate names not appropriate for use as subject headings:''
<pre style="font-family:courier new;">
<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 (1953-1961 : Eisenhower)
États-Unis. Président (1953-1961 : Eisenhower)
Iran. Shah (1941-1979 : Mohammed Reza Pahlavi)
Iran. Shah (1941-1979 : Mohammed Reza Pahlavi)
Illinois. Gouverneur (1973-1977 : Walker)
Illinois. Gouverneur (1973-1977 : Walker)
Église catholique. Pape (1958-1963 : Jean XXIII)
Église catholique. Pape (1958-1963 : Jean XXIII)
Church of England. Diocèse de Londres. Évêque (1675-1713 : Compton)
Church of England. Diocèse de Londres. Évêque (1675-1713 : Compton)
</pre>
</div>
See also [[PFAN - Name Authority Manual#008.2F15 Heading use-subject added entry|Manual 008/15]] and the [[PFAN - Name Authority Manual#667 Nonpublic general note|Manual 667]] section "NARs and subject usage."
See also [[PFAN - Name Authority Manual#008.2F15 Heading use-subject added entry|Manual 008/15]] and the [[PFAN - Name Authority Manual#667 Nonpublic general note|Manual 667]] section "[[PFAN_-_Name_Authority_Manual#NARs_and_subject_usage|NARs and subject usage]]."
Follow these guidelines for newly-created NARs. Make these changes also when modifying
Follow these guidelines for newly-created NARs. Make these changes also when modifying
existing name authority records for any reason.
existing name authority records for any reason.
[2021-02-23]
[2021-03-09] <!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F11 Subject Heading System.2FThesaurus|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F11 Subject Heading System.2FThesaurus|''Supplement'' <big>⮞</big>]]
'''Corporate names for high government and religious officials'''
'''Corporate names for high government and religious officials'''
''Background:'' For Heads of state, heads of governments, etc., International intergovernmental
bodies, Religious officials, and Popes, descriptive catalogers may be required to establish an authorized
bodies, Religious officials, and Popes, descriptive catalogers may be required to establish an authorized
access point for the corporate name for the office as well as a personal name for the office holder. It is
access point for the corporate name for the office as well as a personal name for the office holder. It is
subject cataloging policy to assign only the personal name, not the corporate name, as a subject access
subject cataloging policy to assign only the personal name, not the corporate name, as a subject access
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:
<pre style="font-family:courier new;">
<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)
</pre>
</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:
<pre style="font-family:courier new;">
<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;">
Washington, George, 1732-1799
Washington, George, 1732-1799
</pre>
</div>
would be used as a subject access point.
would be used as a subject access point.
Assign value "b" (Not appropriate) to name authority records for corporate entities representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the entry. Also assign value "n" in 008/11, and make a 667 note indicating the form used in subject cataloging.
Assign value "b" (Not appropriate) to name authority records for corporate entities representing the office held for Heads of state, heads of governments, etc., International intergovernmental bodies, Religious officials, and Popes when the name of the incumbent is included as part of the entry. Also assign value "n" in 008/11, and make a 667 note indicating the form used in subject cataloging.
''Example:''
<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;">
<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 Église catholique. $b Pape (1958-1963 : Jean XXIII)
110 2# $a Église catholique. $b Pape (1958-1963 : Jean XXIII)
008/11 = n
008/11 = n
008/15 = b
008/15 = b
<div style="padding-left:60px; margin-top:0px; padding-top:0px; padding-right:15px; text-indent:-60px;">
<div>
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Jean XXIII, pape, 1881-1963.
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Jean XXIII, pape, 1881-1963.
</div>
</div>
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-02-23]
[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 create new undifferentiated records coded 008/32 “b”. All personal name authority records coded RDA should be differentiated.
* Do not use code “b” in an RDA name authority record; 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.
pair is a “citation” 670 that contains the normal data elements in a resource being cataloged citation.
''Example:''<br>
''Example:''<br>
<pre style="font-family:courier new;">
<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
100 1# $a Lloyd, Richard
100 1# $a Lloyd, Richard
670 ## $a [Auteur de Bound and minor words in Baruya]
670 ## $a [Author of Bound and minor words in Baruya]
670 ## $a Bound and minor words in Baruya, 1989: $b p. de t. (Richard Lloyd)
670 ## $a Bound and minor words in Baruya, 1989: $b p. de t. (Richard Lloyd)
670 ## $a [Point d'accès supplémentaire pour Alex, the amazing juggler]
670 ## $a [Added entry for Alex, the amazing juggler]
670 ## $a Alex, the amazing juggler, 1981: $b p. de t. (Richard Lloyd)
670 ## $a Alex, the amazing juggler, 1981: $b p. de t. (Richard Lloyd)
670 ## $a [Éditeur intellectuel de Allen Jones]
670 ## $a [Editor of Allen Jones]
670 ## $a Allen Jones, 1995: $b p. de t. (Richard Lloyd)
670 ## $a Allen Jones, 1995: $b p. de t. (Richard Lloyd)
</pre>
</div>
Alternatively, an existing undifferentiated name authority record may include a 667 note indicating that the record is undifferentiated and identifying the resource(s) associated with other persons with the same name. In this case, the record generally does not include 670 fields for persons other than the first one identified.
''Example:''<br>
''Example:''<br>
<pre style="font-family:courier new;">
<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;">
008/32 = b
008/32 = b
100 1# $a Jacques, Pierre
100 1# $a Jacques, Pierre
667 ## $a L'auteur de Les gouvernements au Canada n'est pas la même personne que le co-auteur de Esteve, A. Inventaire des secteurs résidentiels soumis ... ni la même personne que le co-éditeur de Les plus beaux textes sur les jeux ...
667 ## $a L'auteur de Les gouvernements au Canada n'est pas la même personne que le co-auteur de Esteve, A. Inventaire des secteurs résidentiels soumis ... ni la même personne que le co-éditeur de Les plus beaux textes sur les jeux ...
670 ## $a Les gouvernements au Canada, ©1978 : $b p. de t. (Pierre Jacques)
670 ## $a Les gouvernements au Canada, ©1978 : $b p. de t. (Pierre Jacques)
</pre>
</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:
* Créer une nouvelle notice d'autorité de nom pour cette personne avec des informations distinctives et ajouter une indication que la personne était auparavant sur une notice indifférenciée (voir Notes 667 dans les notices pour les identités qui figuraient auparavant sur des notices indifférenciées, ci-dessous). Si une notice d'autorité comportant la note 667 « 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 ») existe déjà pour cette personne, utiliser cette notice comme « nouvelle notice ».
* 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 667 notes on records for identities previously on undifferentiated records below).
* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
* Re-evaluate the new name authority record if it contains 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".
Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
* If the undifferentiated NAR is not being deleted because multiple identities remain, delete the pair of 670 fields pertaining to the newly created NAR.
* Réévaluer la nouvelle notice d'autorité de nom si celle-ci contient la note 667 « 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 ».
* If more than one identity remains in the undifferentiated NAR, and there is not sufficient information in the NAR to create new NARs for each name, leave the NAR coded AACR2.
* Si la notice d'autorité de nom indifférenciée n'est pas supprimée parce que plusieurs identités restent, supprimer les zones 670 qui se rapportent à la personne maintenant représentée sur la nouvelle notice d'autorité et, le cas échéant, éditer ou supprimer la zone 667 indiquant que la notice est indifférenciée pour supprimer la mention de cette personne.
* S'il reste plus d'une identité dans la notice d'autorité de nom indifférenciée et qu'il n'y a pas suffisamment d'information pour créer de nouvelles notices d'autorité de nom pour chaque nom, laisser la notice d'autorité de nom codée RCAA2.
In order to facilitate machine processing of authority records (e.g., matching, linking), when only one identity is left on an undifferentiated personal name authority record (i.e., other identities are being
disambiguated and removed), take the following steps:
<ul>
<ul>
<li>
<li>
Create a new NAR for the remaining single identity. If an authority record already exists for that entity 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". The authorized access point itself may be differentiated or it may be identical to the authorized access point in the undifferentiated NAR. In the new record:
<ul>
<ul>
<li style="list-style-image: none; list-style-type:circle;">
<li style="list-style-image: none; list-style-type:circle;">
Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.</li>
<li style="list-style-image: none; list-style-type:circle;">
<li style="list-style-image: none; list-style-type:circle;">
Add a 667 note:
<pre style="font-family:courier new;">
<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 : [numéro Canadiana de la notice de nom indifférenciée].
667 ## Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
</pre>
<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>
</li>
<li style="list-style-image: none; list-style-type:circle;">Add in 016 field subfield $z the Canadiana number of the undifferentiated name authority record to be deleted, if any.</li>
</ul>
</li>
</li>
<li>
<li>
Re-evaluate the new name authority record if it contains 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 ».</li>
<li>S'assurer que la notice d'autorité de nom indifférenciée contient seulement de l'information se rapportant à l'unique identité restante (par exemple, les zones 670). Le cas échéant, supprimer la zone 667 indiquant que la notice est indifférenciée.</li>
<li>Assure that the undifferentiated NAR only contains information relevant to the single identity remaining (e.g., 670s). If applicable, delete field 667 indicating that the record is undifferentiated.</li>
<li>Dans la notice d'autorité de nom indifférenciée, ajouter la notice 667 suivante pour garantir qu'une notice d'autorité de nom ne sera pas créée en double :
<li>Add that information in the 667 note on the undifferentiated record to assure that a duplicate NAR will not be created:
<div style="font-family:courier new; margin-left:50px; 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:50px; 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 Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [numéro Canadiana de la notice d'autorité de nom différenciée].
667 ## $a Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [Canadiana number of undifferentiated name record].
</div>
</div>
</li>
</li>
<li>Catalogueur du PFAN : Signaler la notice d'autorité de nom indifférenciée au [mailto:bac.pfansuppression-deletionfnap.lac@canada.ca?subject=Notice%20non%20différenciée%20à%20supprimer&body=Bonjour,%0D%0DLa%20notice%20doit%20être%20vue%20par%20un%20catalogueur.%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20à%20supprimer%20%3A%0D%0D bac.pfansuppression-deletionfnap.lac@canada.ca].<br>
<li>PFAN cataloguer: Report the undifferentiated name authority record to [mailto:pfansuppression-deletionfnap@bac-lac.gc.ca?subject=Notice%20non%20différenciée%20à%20supprimer&body=Bonjour,%0D%0DLa%20notice%20doit%20être%20vue%20par%20un%20catalogueur.%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20à%20supprimer%20%3A%0D%0D pfansuppression-deletionfnap@bac-lac.gc.ca].<br>
Suggested generic message:
<div style="padding-left:50px; width:500px;">
<div style="padding-left:50px; width:500px;">
<pre>
<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;">
Objet : Notice non différenciée à supprimer
Objet : Notice non différenciée à supprimer<br>
<br>
La notice doit être vue par un catalogueur.
La notice doit être vue par un catalogueur.<br>
Notice à conserver :
Notice à conserver :<br>
Notice à conserver :
Notice à conserver :<br>
Notice à supprimer :
Notice à supprimer : <br>
</pre>
</div>
</div>
</div>
<li>Catalogueur de BAC : Supprimer la notice d'autorité indifférenciée. </li>
<li>BAC cataloguer: Delete the undifferentiated authority record. </li>
</ul>
</ul>
''Exemple de notice indifférenciée de BAC''
''Example of an undifferentiated LAC record''
Undifferentiated authority record before disambiguation:
<pre style="font-family:courier new;">
<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
016 ## $a [Numéro Canadiana]
016 ## $a [Canadiana number]
100 1# $a Dupont, André
100 1# $a Dupont, André
667 ## $a L'auteur d'Histoire du département de la Manche n'est pas la même personne que l'auteur d'Hydraulique urbaine.
667 ## $a L'auteur d'Histoire du département de la Manche n'est pas la même personne que l'auteur d'Hydraulique urbaine.
670 ## $a Histoire du département de la Manche, c1975- : $b vol. 6, p. de t. (André Dupont)
670 ## $a Histoire du département de la Manche, c1975- : $b vol. 6, p. de t. (André Dupont)
</pre>
</div>
New notice for the author of Histoire du département de la Manche:
<pre style="font-family:courier new;">
<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 = a
008/32 = a
016 ## $a [Nouveau numéro Canadiana]
016 ## $a [New Canadiana number]
100 1# $a Dupont, André, $d 1920-
100 1# $a Dupont, André, $d 1920-
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [numéro Canadiana de la notice de nom indifférenciée].
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
670 ## $a Histoire du département de la Manche, c1975- : $b vol. 6, p. de t. (André Dupont)
670 ## $a Histoire du département de la Manche, c1975- : $b vol. 6, p. de t. (André Dupont)
670 ## $a LC/NAF, 24 février 2021 : $b (point d'accès : Dupont, André, $d 1920-)
</pre>
670 ## $a LC/NAF, 24 février 2021 $b (point d'accès : Dupont, André, 1920-)
</div>
<pre style="font-family:courier new;">
Undifferentiated authority record before disambiguation. Remained identify is for the author of Hydraulique urbaine:
<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
016 ## $a [Numéro Canadiana]
016 ## $a [Canadiana number]
100 1# $a Dupont, André
100 1# $a Dupont, André
667 ## $a Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [numéro Canadiana de la notice d'autorité de nom différenciée].
</pre>
667 ## $a Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [Canadiana number of undifferentiated name record].
</div>
<pre style="font-family:courier new;">
New record for the author of Hydraulique urbaine:
<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 = a
008/32 = a
016 ## $a [Nouveau numéro Canadiana] $z [Numéro Canadiana de la notice de nom indifférenciée]
016 ## $a [New Canadiana number] $z [Canadiana number of undifferentiated name record]
100 1# $a Dupont, André
100 1# $a Dupont, André
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [numéro Canadiana de la notice de nom indifférenciée].
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
670 ## $a Hydraulique urbaine, 1965 : $b page de titre (André Dupont)
670 ## $a Hydraulique urbaine, 1965 : $b page de titre (André Dupont)
</pre>
</div>
'''Exemple de notice indifférenciée dérivée du LC/NAF'''
''Example of undifferentiated record derived from LC/NAF''
Undifferentiated authority record before disambiguation:
<pre style="font-family:courier new;">
<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
100 1# $a Bowman, Anne
100 1# $a Bowman, Anne
667 ## $a 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
667 ## $a 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
670 ## $a [Author of Esperanza]
670 ## $a [Author of Esperanza]
670 ## $a Her Esperanza, 1855: $b t.p. (Anne Bowman)
670 ## $a Her Esperanza, 1855: $b t.p. (Anne Bowman)
670 ## $a [Illustrator of Reptiles]
670 ## $a [Illustrator of Reptiles]
670 ## $a Reptiles, c1996: $b copyr. p. (illus.: Anne Bowman)
670 ## $a Reptiles, c1996: $b copyr. p. (illus.: Anne Bowman)
</pre>
</div>
New record for the author of Esperanza:
<pre style="font-family:courier new;">
<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 = a
008/32 = a
016 ## $a [Nouveau numéro Canadiana]
016 ## $a [New Canadiana number]
100 1# $a Bowman, Anne, $d activité 19e siècle
100 1# $a Bowman, Anne, $d activité 19e siècle
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [numéro Canadiana de la notice de nom indifférenciée].
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
670 ## $a Esperanza, 1855 : $b page de titre (Anne Bowman)
670 ## $a Esperanza, 1855 : $b page de titre (Anne Bowman)
</pre>
</div>
Undifferentiated authority record before disambiguation. Remained identify is for the illustrator of Reptiles:
<pre style="font-family:courier new;">
<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
016 ## $a 0000X0000F
100 1# $a Bowman, Anne
100 1# $a Bowman, Anne
667 ## $a Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [numéro Canadiana de la notice d'autorité de nom différenciée].
667 ## $a Dernière identité sur notice indifférenciée; signalée pour suppression car remplacée par [Canadiana number of undifferentiated name record].
670 ## $a Reptiles, c1996: $b copyr. p. (illus.: Anne Bowman)
670 ## $a Reptiles, c1996: $b copyr. p. (illus.: Anne Bowman)
</pre>
</div>
New record for the illustrator of Reptiles :
<pre style="font-family:courier new;">
<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 [Nouveau numéro Canadiana]
016 ## $a [New Canadiana number]
100 1# $a Bowman, Anne
100 1# $a Bowman, Anne
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [numéro Canadiana de la notice de nom indifférenciée].
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
670 ## $a Reptiles, c1996 : $b page de copyright (illus.: Anne Bowman)
670 ## $a Reptiles, c1996 : $b page de copyright (illus.: Anne Bowman)
</pre>
</div>
=== Notes 667 dans les notices pour les identités qui figuraient auparavant sur des notices indifférenciées ===
=== 667 notes on records for identities previously on undifferentiated records ===
Always add a 667 note to a new NAR to identify the Canadiana number of the authority record in which information about that person had been recorded:
<pre style="font-family:courier new;">
<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 : [numéro Canadiana de la notice d'autorité de nom indifférenciée].
667 ## $a Anciennement incluse dans une notice d'autorité de nom indifférenciée : [Canadiana number of undifferentiated name record].
</pre>
<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>
==== 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.
== 008/33 Level of establishment ==
''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
100 1# $a Lemieux, Claire
'''Provisional''' (008/33 value “c”) records:
667 ## $a Cas possible d'homonymie avec l'autrice et illustratrice de : Le cadeau de Kato, 2016 (Claire Lemieux)
<ol>'''General'''<br>
670 ## $a Ds: Bouchard, J. Espace mathématique 1 (illustratrice)
</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:
'''Special administrative regions of Hong Kong and Macau'''<br>
<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;">
667 ## $a Notice d'autorité de nom indifférenciée représentant une seule identité; signalée pour suppression. </li>
<li>Create a new name authority record for the identity. The authorized access point itself may be differentiated or it may be identical to the authorized access point in the undifferentiated NAR. If an authority record already exists for that entity 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".</li>
<li>Add a 667 note:
<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].
<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>
'''Additional information for PFAN participants'''<br>
<li>Add in 016 field subfield $z the Canadiana number of the undifferentiated name authority record to be deleted, if any.</li>
<li>Re-evaluate the new name authority record if it contains the note 667 " 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 ".</li>
<li>PFAN cataloguer: Report the undifferentiated name authority record to [mailto:pfansuppression-deletionfnap@bac-lac.gc.ca?subject=Notice%20non%20différenciée%20à%20supprimer&body=Bonjour,%0D%0DLa%20notice%20doit%20être%20vue%20par%20un%20catalogueur.%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20%C3%A0%20conserver%20%3A%0D%0DNotice%20à%20supprimer%20%3A%0D%0D pfansuppression-deletionfnap@bac-lac.gc.ca].<br>
Suggested generic message:
<div style="padding-left:50px; width:500px;">
# If the contributing library does not have the language expertise to establish the authorized access point as a fully established authority record; this would include situations where the library lacked adequate reference sources for research or where the cataloger was not confident of the correct grammatical form for the access point.<br>
<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;">
Objet : Notice non différenciée à supprimer<br>
<br>
</ol>
La notice doit être vue par un catalogueur.<br>
Notice à conserver :<br>
Notice à conserver :<br>
Notice à supprimer : <br>
</div>
</div>
'''Preliminary''' (008/33 value “d”) records:<br>
BAC cataloguer: Delete the undifferentiated authority record.
</ul>
<br>
''Example of an undifferentiated record that represents a single identity''
<ol>Preliminary authority records (008/33 value “d”) generally are the result of retrospective projects. PFAN catalogers are expected to routinely upgrade NARs coded preliminary when making other modifications to the record. Because of this maintenance requirement, PFAN participants are asked to contact the PFAN Standards Committee before embarking on projects that may result in large numbers of NARs coded preliminary being added to the NACO Authority File.</ol>
<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:sans-serif">Undifferentiated authority record before disambiguation:</div>
008/32 = b
100 1# $a Lemieux, Claire
''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
667 ## $a 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
667 ## $a Cas possible d'homonymie avec l'auteur et illustrateur de : Le cadeau de Kato, 2016.
670 ## $a Ds: Bouchard, J. Espace mathématique 1 (illustratrice)
</div>
== 008/39 Cataloging source ==
<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:sans-serif">Undifferentiated authority record after disambiguation :</div>
008/32 = b
100 1# $a Lemieux, Claire
667 ## $a Notice d'autorité de nom indifférenciée représentant une seule identité; signalée pour suppression.
667 ## $a 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
667 ## $a Cas possible d'homonymie avec l'auteur et illustrateur de : Le cadeau de Kato, 2016.
670 ## $a Ds: Bouchard, J. Espace mathématique 1 (illustratrice)
</div>
<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:sans-serif">New authority record after disambiguation</div>
008/32 = a
016 ## $a [New Canadiana number]
100 1# $a Lemieux, Claire
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [no Canadiana number, use OCLC number from undifferentiated name record].
670 ## $a Bouchard, J. Espace mathématique 1 $b (illustratrice)
670 ## $a Le cadeau de Kato, 2016 $b (Claire Lemieux)
[2021-02-15]
[...]
670 ## Téléphone à l'artiste, 13 septembre 2021 $b (confirme que l'autrice de Le cadeau de Kato est la même personne que l'illustratrice de Espace mathématique et des affiches Double trouble et Opération Nez rouge)
</div></span>
'''Recording coordinates for countries, states, counties'''<br>
[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>]]
== 008/33 Level of establishment ==
'''NARS'''
<div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;">
<div style="margin-left:25px; margin-bottom:25px;">
'''Provisional''' (008/33 value “c”) records:
<div style="margin-left:25px; margin-bottom:25px;">
'''General'''<br>
</div>
<div style="margin-bottom:25px;">Code an NAR as provisional (008/33 value “c”) if the authorized access point cannot be formulated satisfactorily because of inadequate information. If the necessary information later becomes available, re-evaluate the NAR and upgrade it to fully established (008/33 value “a”). In no case should a provisional-level authority record be created with an access point that conflicts with an existing NAR according to PFAN normalization rules.</div>
<div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;">
</div>
'''Special administrative regions of Hong Kong and Macau'''<br>
<div style="margin-bottom:25px;">Because there is uncertainty about whether Hong Kong and Macau will continue to have two official languages, code all NARs for government bodies in these two places, at the level of the special administrative region and below, as provisional (008/33 value “c”), regardless of the language in which the authorized access point has been established. If a form in the second of the two official languages becomes available, add that form as a variant access point rather than revising the existing authorized access point. Consult [http://original.rdatoolkit.org/rdachp11-fr_rda11-1365.html RDA 11.2.2.5.2] and the [http://original.rdatoolkit.org/lacbanqpschp11_lacbanqps11-105.html related policy statement] for instructions on choosing the language of the referred name. Please note that this policy for provisional status does not apply to non-government bodies.</div>
'''Additional information for PFAN participants'''<br>
PFAN participants may also create provisional records in the following two exceptional situations:<br>
<ol>
<li>If the contributing library does not have the language expertise to establish the authorized access point as a fully established authority record; this would include situations where the library lacked adequate reference sources for research or where the cataloger was not confident of the correct grammatical form for the access point.<br>
<li>
<li>If the contributing library is unable, due to limited resources or other constraints, to complete related authority work or to determine the appropriate reference structure that is required for fully established authority records.<li>
</ol>
</div>
</div>
<div style="font-family:courier new; background-color:#f8f9fa; border:1px solid #eaecf0;">
<div style="margin-left:25px; margin-bottom:25px;">
'''Preliminary''' (008/33 value “d”) records:<br>
:: 034 ## $d W119.697222 $e W119.697222 $f N034.420833 $g N034.420833<br>
<div style="margin-left:25px; margin-bottom:25px;">
<div style="margin-bottom:25px;">Preliminary authority records (008/33 value “d”) generally are the result of retrospective projects. PFAN catalogers are expected to routinely upgrade NARs coded preliminary when making other modifications to the record. Because of this maintenance requirement, PFAN participants are asked to contact the PFAN Standards Committee before embarking on projects that may result in large numbers of NARs coded preliminary being added to the NACO Authority File.</div>
<div style="margin-bottom:25px;">As needed, catalogers may upgrade NARs coded preliminary when working with earlier/later corporate body records, even if the access points in the records being upgraded are not used in the local bibliographic database. Occasionally catalogers may need to create a new NAR without having an item in hand, e.g., for an earlier or later name heading using information from reference sources, or a heading based on information found in field 245 subfield “c” of bibliographic records when resolving NAR conflicts. Do not code these occasional NARs as “preliminary”.</div>
</div>
</div>
</div>
<!--'''SARs'''
''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.
'''Coordinate Conversion Tools'''<br>
Generally, series data elements should be viewed on the publication and series authority records should be coded “a” (full). In post-cataloging authority work it is permissible to create SARs without the piece in hand; these records are coded “d” (preliminary). When a publication in the series has been examined and the preliminary authority record reviewed and updated as necessary, upgrade the SAR to full level.-->
[2021-11-03]<!--(2021-10-27)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#008.2F33_Level_of_establishment|''Supplement'' <big>⮞</big>]]
== 008/39 Cataloging source ==
<!--''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.-->
Whatever value is originally input into this field remains; do not change this value when updating a record unless the original value was incorrect.
<!--La valeur d'origine est incorrecte si elle n'est pas « blanc » pour une notice créée à l'origine par BAC, BAnQ ou LC (sigle CaOONL, CaQMBN ou DLC dans la 040 $a) ou « c » (Programme de catalogage coopératif) pour une notice créée à l'origine par une université ou un participant NACO (sigle de l'université ou du participant NACO dans la 040 $a). -->
'''Sources'''<br>
[2021-11-03]<!--(2021-10-20)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#008.2F39_Cataloging_source|''Supplement'' <big>⮞</big>]]
= 016 National Bibliographic Agency Control Number =
Field 016 is mandatory whenever a cataloguer creates, updates or uses an authority record.
When creating an authority record, and when updating or using an existing record without a Canadiana number in field 016, first check the LC/NAF to see if the same entity is represented by an authority record, and if this authority record includes a Canadiana number. Note that the authorized access point, in the LC/NAF, may be different from the Canadiana access point. If the LC/NAF record does include a Canadiana number, add this number to the Canadiana record, changing the final E to an F (or adding an F at the end of the Canadiana number, if there is no final letter).
When updating or using an existing authority record that includes a Canadiana number, please check that the language code F is present at the end of the field.
'''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).
'''Subfield $b – Language of cataloging'''<br>
<ol>'''PFAN'''
<br>
When identifying a duplicate, ask that the duplicate be deleted (see [[PFAN_-_Other_Documentation#Procedures_for_Duplicates|Procedures for duplicates]]). DO NOT “reuse” the authority record to describe a different entity. This causes problems for bibliographic services and for other library systems.<br>
If field 016 is present in the authority record to be deleted, record the Canadiana number of the deleted record in field 016, subfield $z, in the preferred authority record.<br>
If there is no field 016 in the record to be deleted, please add one, using the number 0000X0000F. Do not record this number in field 016, subfield $z, in the preferred authority record.
See also the “[[PFAN_-_Name_Authority_Manual#Duplicates|Duplicates]]” section in this Manual, field 667.<br>
<br>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#040_Cataloging_Source|''Supplement'' <big>⮞</big>]]
______<br>
'''LAC'''<br>
When identifying a duplicate, delete it. DO NOT “reuse” the authority record to describe a different entity. This causes problems for bibliographic services and for other library systems. <br>
If field 016 is present in the authority record to be deleted, record the Canadiana number of the deleted record in field 016, subfield $z, in the preferred authority record.</ol>
'''LAC'''<br>In the Canadiana authority file, cataloguers must add the 042 field every time they create, derive or revise an authority record. This code identifies the “virtual” Canadian authority file, which is spread across two separate authority files (LC/NAF and Canadiana).
<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>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#042_Authentication_Code|''Supplement'' <big>⮞</big>]]
[2022-01-26]<!--(2022-01-26)-->
'''General'''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#016_National_Bibliographic_Agency_Control_Number|''Supplement'' <big>⮞</big>]]
= 022 International Standard Serial Number =
<!--''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.-->
'''General'''<br>
Record the ISSN whenever it is available from the item in hand, from analytic bibliographic records, or from the collected set bibliographic record for the series; otherwise, recording the ISSN is optional.
When it is known there are separate ISSN assigned to different formats of a series represented by a single SAR, prefer to record in 022 subfield $a the ISSN that is the linking ISSN (ISSN-L) for the different formats. Identify ISSN for specific formats in separate 667 fields, following this pattern:
<pre style="font-family:courier new;">
<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;">
667 $a Version imprimée : ISSN YYYY-ZZZZ
667 $a Version en ligne : ISSN YYYY-ZZZZ
</div>
When the title of a publication has changed, confirm that an ISSN appearing on the publication belongs to the new title and not to the earlier title.
An incorrect ISSN can be given in a 667 field (e.g., “ISSN 1122-3344 is not a valid ISSN for this publication”).
[2021-11-03] <!--(2021-11-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#022_International_Standard_Serial_Number|''Supplement'' <big>⮞</big>]]
'''Example :'''
= 024 Other standard identifier =
<pre style="font-family:courier new;">
'''General'''<br>
Follow the guidelines in [https://www.loc.gov/aba/pcc/naco/documents/NACO-024-Best-Practices.pdf NACO Best Practices] for the 024 Field. As a general rule, limit the number of 024 fields in a NACO authority record to five. Do not routinely delete or change existing 024 fields when adding new ones.
'''Maintenance'''<br>
Catalogers are not required to maintain identifiers coded in the 024 field of PFAN authority records. When an 024 field is present in an authority record that is being reported for deletion (for example, in the case of a duplicate), catalogers should transfer the field to the record that is to be retained. When two authority records are being collapsed into one, and each record has a different 024 field, catalogers should include both 024 fields in the updated record.
'''Subfield $2 – Source of date scheme'''
[2021-11-01]<!--(2021-11-01)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#024_Other_Standard_Identifier|''Supplement'' <big>⮞</big>]]
= 034 Coded cartographic mathematical data =
'''Subfield $s – Start period, and $t – End period'''
'''Recording coordinates for countries, states, counties'''<br>
Coordinates for outside limits (bounding boxes or polygons) should generally be used with larger geographic entities such as countries, states, and counties to identify the coordinates of the entity. The
coordinates may be recorded in either degrees/minutes/seconds, decimal degrees, decimal minutes, and/or decimal seconds. Styles should not be mixed in a single 034 field, but the field may be repeated to
represent the different styles (see below for conversion utilities); the order of 034 fields when both styles are given does not matter. To facilitate the reuse of coordinates in geographic applications, the point (not the comma) should be used as the decimal point.
'''Subfield $u – Uniform Resource Identifier and Subfield and Subfield $v – Source of information'''
:'''Degrees/minutes/seconds''': record in the form hdddmmss (hemisphere-degrees-minutes-seconds).
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">034 ## $d W1800000 $e E1800000 $f N0840000 $g S0700000
<ol>
</div>
:'''Decimal degrees''': record in the form hddd.dddddd (hemisphere-degrees.decimal degrees)
<li>For fields 046, 368, 370-378, and 381:
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">034 ## $d E079.533265 $e E086.216635 $f S012.583377 $g S020.419532
<ol>
</div>
:'''Decimal degrees with plus ou minus''': record in the form +-ddd.dddddd (hemisphere[+/-]-degrees.decimal degrees) (“+” or N and E, “-” for S and W ; the plus sign is optional)
<li type="a">use $v if the information/source is not cited in a 670</li>
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">
034 ## $d +079.533265 $e +086.216635 $f -012.583377 $g -020.419532<br>
<div style="font-family:sans-serif; margin-left:50px;">''(Example with +/-)''</div>
034 ## $d 079.533265 $e 086.216635 $f -012.583377 $g -020.419532<br>
</li>
<div style="font-family:sans-serif; margin-left:50px;">''(Example without the optional plus sign)''</div>
</div>
</li>
</ol>
'''Subfield $v – Source of information'''
:'''Decimal minutes''': record in the form hdddmm.mmmm (hemisphere-degrees-minutes.decimal minutes)
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">
034 ## $d E07932.5332 $e E08607.4478 $f S01235.5421 $g S02028.9704
</div>
:'''Decimal seconds''': record in the form hdddmmss.sss (hemisphere-degrees-minutes-seconds.decimal seconds)
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">
034 ## $d E0793235.575 $e E0860727.350 $f S0123536.895 $g S0202858.125
</div>
'''Recording coordinates for cities, towns, and townships'''<br>
Coordinates for cities, towns, and townships should generally be recorded as center points rather than outside limits. For the 034 field, the longitude and latitude that form the central axis are recorded
twice to define the center point (i.e., the contents of $d and $e are identical, the contents of $f and $g are identical).
'''For online resources:'''
<div style="font-family:courier new; margin-left:25px; margin-bottom:25px; 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;">
034 ## $d W0950500 $e W0950500 $f N0303000 $g N0303000<br>
<div style="font-family:sans-serif; margin-left:50px;">''(Example showing degrees/minutes/seconds)''</div>
034 ## $d W119.697222 $e W119.697222 $f N034.420833 $g N034.420833<br>
<div style="font-family:sans-serif; margin-left:50px;">''(Example showing decimal degrees)''</div>
034 ## $d -119.697222 $e -119.697222 $f +034.420833 $g +034.420833<br>
<div style="font-family:sans-serif; margin-left:50px;">''(Example showing decimal degrees with plus/minus)''</div>
</div>
</pre>
'''Coordinate Conversion Tools'''<br>
PFAN institutions are encouraged to provide both degrees/minutes/seconds and decimal degrees when available. Numerous conversion tools are available on the Web to derive one from the other; here are two examples:
:'''Degrees/minutes/seconds to Decimal degrees:'''<br>
:http://vancouver-webpages.com/META/DMS.html
:'''Decimal degrees to Degrees/minutes/seconds:'''<br>
:http://vancouver-webpages.com/META/DD.html
'''Sources'''<br>
Subfield $2 has been defined for recording the source of the coordinate information– codes for commonly used sources are available from: [http://www.loc.gov/standards/sourcelist/cartographic-data.html ''Cartographic Data Source Codes''].
A 670 citation to the source would not be required if the only information from the source is recorded in field 034; a 670 citation should be made if necessary to record information beyond coordinates, such as variant names, hierarchy, time period of applicability, etc.
[2021-03-09]<!--(2021-03-04)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#034_Coded_Carographic_Mathematical_Data|''Supplement'' <big>⮞</big>]]
= 035 System Control Number =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#035_System_Control_Number|''Supplement'' <big>⮞</big>]]
= 040 Cataloging source =
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.
'''Subfield $b – Language of cataloging'''<br>
Subfield $b fre added automatically by WMS.
'''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 $e – Description conventions'''<br>
All new authority records created and submitted by PFAN cataloguers must have the code "z" in Field 008/10 and include the $e rda subfield in Field 040.
When adding the subfield $e manually, add it after subfield $b and before $c. It is not necessary to move the subfield $e to this position if it is already present elsewhere in the 040 or if it is being added by a macro or a template. Subfield $e rda is automatically added by the system in NARs and SARs when fixed field 008/10 (Rules) is set to “z” (Other).
[2021-02-15]<!--(2021-02-15)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#040_Cataloging_Source|''Supplement'' <big>⮞</big>]]
= 042 Authentication Code =
'''PFAN'''<br>This field is found in all authority records used by LAC. Do not modify or delete this field when code CaOONL appears in field 040.
When cataloguers (other than LAC cataloguers) derive an authority record from an LAC record which includes field 042, they must remember to delete this field.
_____
'''General'''
'''LAC'''<br>In the Canadiana authority file, cataloguers must add 042 $a nlc every time they create, derive or revise an authority record. This code identifies the “virtual” Canadian authority file, which is spread across two separate authority files (LC/NAF and Canadiana).
[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>]]
= 043 Geographic Area Code <span style="color:red>[New]</span>=
Field 043 can only be used in authority records for geographical names (151).
'''SARs'''
'''Subfield b – Local GAC code and Subfield $2 – Source of local code'''
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 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>]]
''Establishing an SAR access point:''
= 046 Special coded dates =
'''General'''
Best practice: When encoding date information, give the fullest information about the date that is readily available (the date in field 046 may be more precise than a date used in the 100 subfield $d).
<li>Exclude from the authorized access point the following information included in the series statement in the bibliographic record for the component part:
<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.
<li type="a">other title information;</li>
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>
<li type="a">statement of responsibility;</li>
''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;">
046 ## $f 1884-10-11 $g 1962-11-07 $2 edtf
100 1# $a Roosevelt, Eleanor, $d 1884-1962
670 ## $a When you grow up to vote, 1932 : $b p. de t. (Eleanor Roosevelt (Mrs. Franklin D. Roosevelt))
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)
<li type="a">ISSN;</li>
<div style="margin-top:25px;">
046 ## $f 1946-06 $2 edtf
100 1# $a Vickers, Roy Henry, $d 1946-
670 ## $a Solstice, c1988 : $b p. de t. (Roy Henry Vickers) jaquette (artiste amérindien; né en juin 1946 à Greenville, Colombie-Britannique)
</ol>
</div>
<div style="margin-top:25px;">
046 ## $k 1981 $2 edtf
100 1# $a Allende, Isabel. $t Casa de los espíritus
= 100 Heading - Personal Name =
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 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>
</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>
<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
<pre style="font-family:courier new;">
</pre>
100 0# $a Hellanicus $c (Grammairien), $d environ 200 av. J.-C.
'''''Authorized access points for persons'''''
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>
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>'''Example:'''
<span style="color:red>'''Repeatability:'''</span>
<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>'''Example:'''
<span style="color:red>'''Conflicting dates'''</span>
</pre>
<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>
<pre style="font-family:courier new;">
<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:''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#100_Heading-Personal_Name|''Supplement'' <big>⮞</big>]]
= 151 Heading - Geographic Name =
<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 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))
'''Subfield $a – Content type term'''
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>
<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.)
'''Examples:'''
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)
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
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>
<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>
</pre>
<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>
<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>
<pre style="font-family:courier new;">
<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>
</pre>
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;">
<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>
</div>
<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-
670 ## $a Prisonnier à Guantanamo, 2008 : $b page de titre (Mollah Abdul Salam Zaeef)
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>
'''Subfield $2 – Source of date scheme'''
Always add subfield $2 edtf except after a century.
'''<span style="color:red>Subfields $q – Establishment date, $r – Termination date,</span> $s – Start period, and $t – End period'''
<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>
''<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>
<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>
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
''<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)
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:
<pre style="font-family:courier new;">
<ol>
<li type="a">use of $v is optional if the same information/source is already cited in the 670</li>
</pre>
<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>
<pre style="font-family:courier new;">
</li>
</ol>
</pre>
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.
<pre style="font-family:courier new;">
'''Repeatability:'''
'''Subfield $v – Source of information'''
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
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
'''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; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
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>
'''Examples :'''
[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>=
'''Examples :'''
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:''
<pre style="font-family:courier new;">
<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>
</pre>
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.
[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>]]
'''General'''
= 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.
'''Repeatability:'''
''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]
</div>
'''Subfield $2 – Source of term'''
'''Subfield $2 – Number source'''
In subfield $2, record " fcps " to indicate that the number comes from the PS8000 class.
'''Subfield $s – Start period and Subfield $t – End period'''
[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 =
'''Sous-zone $u – Identificateur de ressource uniforme et Sous-zone $v – Source de l'information'''
<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>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#374_Occupation|''Supplement'' <big>⮞</big>]]
= 375 Gender =
= 083 Dewey Decimal Classification Number =
'''General'''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#083_Dewey_Decimal_Classification_Number|''Supplement'' <big>⮞</big>]]
= 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>]]
= 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.
'''Subfield $s – Start period and Subfield $t – End period'''
<!--'''SARs'''
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:''
#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].
''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:
<ol>
<li type="a">initial article in subfields $a, $t, $n, and $p;</li>
<li type="a">other title information;</li>
<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>
</ol>
</li>
<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].-->
[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 =
'''''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:
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]
# Additions to the name are contained in a single set of parentheses separated by colons.
#
'''Examples:'''
# The term for the type of family is added after the name and is contained in subfield $a.
<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 $d (date) follows the term for the type of family.
#
# 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>
</div>
'''''Authorized access points for persons'''''
'''General'''
'''General'''
Use first indicator value “0” or “1” in field 100 when creating an NAR for a person.
'''Examples:'''
'''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:
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.
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the Information'''
<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:''
<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>]]
<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>
= 380 Form of work =
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>]]
= 336 Content Type =
'''General'''
Field 336 may only be used in NARs and SARs for expressions. 336 is always accompanied by a subfield $2.
'''Subfield $2 – Source of term'''
In subfield $2 give “rdacontent/fre.”
'''SARs'''
'''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''].
'''General'''
[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>]]
= 368 Other attributes of person or corporate body =
'''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.
''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:sans-serif; margin-left:85px;">
110 2# $a Freer Gallery of Art
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><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)
(''Corporate body recorded as associated group and other distinguishing characteristic of work'')</div>
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.
'''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;">
100 0# $a Alexandre $b VI, $c pape, $d 1431-1503
368 ## $d pape $s 1492 $t 1503
<br><br>
100 0# $a Jane Seymour, $c reine, épouse d'Henri VIII, roi d'Angleterre, $d 1509?-1537
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:'''
'''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.
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:''
<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
= 383 Numeric designation of musical work =
368 ## $d métropolite de Rostov
<div style="font-family:sans-serif; margin-left:85px;">
''(La première 368 renferme un terme provenant d'un vocabulaire contrôlé mais pas la seconde)'' </div>
</div>
'''General'''
'''Subfield $s – Start period and Subfield $t – End period'''
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
'''General'''
[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 =
= 385 Audience characteristics =
'''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:''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#385_Audience_Characteristics|''Supplement'' <big>⮞</big>]]
<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 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 recorded in 370:</div>
370 ## $e Washington (État) $2 lacnaf
= 386 Creator/contributor characteristics =
<div style="font-family:sans-serif">
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>
'''General'''
<div style="font-family:sans-serif">
Form of name as part of preferred name of a local place:</div>
151 ## $a Seattle (Wash.)
<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>
</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>
110 2# $a Parti libéral du Canada (Québec)
<div style="font-family:sans-serif">
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]
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
= 4XX - See From Tracings - General Information =
<div style="font-family:sans-serif">
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:sans-serif; margin-left:85px;">''(Preferred name of place)''</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
'''General'''
<div style="font-family:sans-serif">
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
<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>''
<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>
370 ## $a Italie $e Milan (Italie) $2 lacnaf
<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
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:'''
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.
<div><br> Example showing 378 without a variant for the fuller form of name:
'''<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>
</pre>
</li>
<li>Establish additional NARs for the authorized access points needed to support elements used in 4XX variant access points (e.g., parent body associated with subordinate body being established).
''<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.
<li>Use the established form of components in 4XX variant access points, except for non-Latin script variants, which may represent a mixture of scripts or may be entirely in a non-Latin script.
''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;">
'''Examples:'''
370 ## $c Première nation de Natashkuan $2 lacnaf
<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;">
</div></span>
</div>
</ul>
'''Subfield $w – Control subfield'''
'''Subfield $s – Start period and Subfield $t – End period'''
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'''
''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 =
'''SARs'''
'''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 $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.
'''General'''
'''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.
'''Subfield $w – Control subfield'''
[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'''
$w b = to indicate a reference from a later authorized access point
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).
$w nnnc = to indicate a see also reference for multiple pseudonyms (record also contains a 663 field)
''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>
</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.
''Example:''
'''General'''<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;">
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-02-15]
[2021-03-10]<!--(2021-03-02)-->
<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#372_Field_of_Activity|''Supplement'' <big>⮞</big>]]
= 510 See Also From Tracing - Corporate Name =
= 373 Associated group =
'''Généralités'''
'''General'''
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:''
<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)
= 511 See Also From Tracing - Meeting Name =
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
373 ## $a Canadiens de Montréal (Équipe de hockey) $2 lacnaf
</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
<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>
'''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.
= 530 See Also From Tracing - Uniform Title =
''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: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;">
<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>
<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.
[2021-02-15]
[2023-06-21]<!--(2023-06-21)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#551_See_Also_From_Tracing-Geographic_Name|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]]
= 64X Series Numbering Peculiarities =
= 374 Occupation =
'''General'''
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:'''
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'''
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.
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#646_Series_Classification_Practice|''Supplement'' <big>⮞</big>]]
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#374_Occupation|''Supplement'' <big>⮞</big>]]
= 663 Complex See Also Reference - Name =
= 375 Gender =
'''PFAN'''
<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>
[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>]]
= 376 Family information =
'''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.
'''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'''
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
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.
'''Examples :'''
[2021-03-10]<!--(2021-03-02)-->
<div style="padding-left:50px;">
<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'''
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]
''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;">
377 ## $a myn
<div style="font-family:courier new; margin-left:50px; 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;">
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>
</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 =
'''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.
''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.
<div style="font-family:courier new; margin-left:50px; 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;">
378 ## $q Kay Dean
</div>
'''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-02-22]<!--(2021-03-02)-->
</div>
<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>]]
= 380 Form of work =
'''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.
''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'''
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;">
100 1# $a Dickinson, Emily, $d 1830-1886. $t Because I could not stop for Death
<div style="font-family:courier new; margin-left:50px; 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;">
381 ## $a Fr. 712
<div style="font-family:sans-serif; margin-left:85px;">
''(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:85px;">
''(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
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>
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.
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.
''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;">
130 #0 $a Bible. $l Français. $s Bayard. $f 2001
381 ## $a Bayard éditions $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(Corporate body recorded as other distinguishing characteristic of expression)''</div><br>
130 #0 $a Journal of adult education (University of Zambia. Centre for Continuing Education)
373 ## $a University of Zambia. Centre for Continuing Education $2 naf
381 ## $a University of Zambia. Centre for Continuing Education $2 naf
<div style="font-family:sans-serif; margin-left:85px;">(''Author has a pseudonym used by multiple persons and individual pseudonyms'')</div>
<div style="font-family:sans-serif; margin-left:85px;">
</div>
''(Corporate body recorded as associated group and other distinguishing characteristic of work)''</div>
</div>
</div>
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.
= 665 History reference =
''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;">
130 #0 $a Ley de Enjuiciamiento Criminal para las Islas de Cuba y Puerto Rico (Cuba; Porto Rico)
370 ## $f Cuba $f Porto Rico $2 lacnaf
= 667 Nonpublic general note =
381 ## $a Cuba $a Porto Rico $2 lacnaf
<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>
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).
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
field, use the 381 field to record the other distinguishing characteristic. Optionally, also record the same information in any other appropriate 3XX field.
'''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, repeat the field. Overall best practice: repeat the field when needed for clarity.
'''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#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.
'''NARs for persons with identities not established'''<br>
'''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 =
'''Examples:'''
'''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)-->
<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;">
<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;">
<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>
</div>
'''NARs and subject usage'''
'''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 :''
<li type="a">'''Heads of state, etc.'''
<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>
</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>=
</div>
'''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;">
<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;">
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>
</div>
</li>
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>
</li>
</ol>
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>
</div>
'''Examples:'''
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;">
<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>
</div>
'''Non-Latin script reference notes'''
'''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 :''
# The date of publication.
<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)-->
</pre>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]
</ol>
= 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>
<pre style="font-family:courier new;">
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
=== Recording dates ===
<div style="font-family:sans-serif; margin-left:85px;">
''(NAR for a collection of Renaissance poetry compiled in the nineteenth century)''</div>
</div>
The 388 field may be used in conjunction with, or instead of, the 046 field. When specific date(s) of creation or origin are not known, or span a long period of time, recording textual chronological terms in the 388 field may be useful.
=== Justifying variant access points ===
''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;">
046 ## $k 13
388 1# $a Moyen Âge $2 rvm
<div style="font-family:sans-serif; margin-left:85px;">
''</div>
</div>
'''Repeatability:'''
In choosing between repeating a field and repeating a subfield: If the indicator value differs, repeat the field. If the vocabulary source differs, repeat the field. Otherwise, if the only addition to an existing field is an additional term from the same vocabulary, repeat the subfield. 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;">
388 1# $a Guerre mondiale, 1939-1945 $2 rvm
388 1# $a <span style="color:red>Occupation allemande de la France (France : 1940-1945) $2 rvmfast</span>
<div style="font-family:sans-serif; margin-left:85px;">
''(NAR with 388 fields containing terms from different vocabularies)''</div>
</div>
[2022-11-07] <!--(2022-11-04)-->
'''NARs''' <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>]]
= 4XX - See From Tracings - General Information =
'''SARs''' <br>
'''General'''
When modifying an authority record for another reason, delete any final mark of punctuation in a 4XX field unless it is a part of the data (e.g., a period in an abbreviation) or is called for by the cataloging rules (e.g., a parenthetical qualifier).
When otherwise modifying NARs or SARs that contain obsolete codes such as subfield $w position zero (0) code “d,” PFAN catalogers should upgrade the NAR to RDA.
Not all 4XX references require justification; see “[[PFAN_-_Name_Authority_Manual#Justifying_variant_access_points|Justifying variant access points]]” in the 670 section of this document.
Do not make a 4XX that normalizes to the same form as another 4XX on the same authority record or a 1XX on any name authority record. See the section “NACO normalization” in the [https://www.loc.gov/catdir/cpso/dcmz1.pdf/view DCM Z1] Introduction.
Best practice guidelines for RDA:
'''LC/NAF, OCLC and fichier interne de BAnQ'''
<ul>
<li>Record variants found in the manifestation being cataloged:
<dl>
<dd>○ Use cataloger's judgment;</dd>
<dd>○ No limitation on the number or form of references;</dd>
<dd>○ Instead of or in addition to adding variants, consider providing access by adding 37X fields.
<div><br> Example showing 378 without a variant for the fuller form of name:
<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;">
<pre style="font-family:courier new;">
100 1# $a Bucknum, David W.
378 ## $q David Walter
</div>
</div>
</dd>
</dl>
</li>
<pre style="font-family:courier new;">
<li>Establish additional NARs for the authorized access points needed to support elements used in 4XX variant access points (e.g., parent body associated with subordinate body being established).
<li>Generally provide a variant form 4XX access point for a former 1XX authorized access point, unless the former authorized access point was egregiously incorrect. See the section “[[PFAN_-_Name_Authority_Manual#4XX$w|Subfield $w – Control subfield]]” for more information.
<ol>
<li>Use the established form of components in 4XX variant access points, except for non-Latin script variants, which may represent a mixture of scripts or may be entirely in a non-Latin script.
<li>Generally, do not remove variants unless egregiously incorrect (e.g., a non-Latin script variant that does not represent the same person).
<li>If a form found on the manifestation being cataloged includes a variant form of a component of a 4XX variant access point, that form may be used in its entirety as an additional 4XX variant access point, provided that it is not divided into its component parts through the use of subfields.
<div>
''Examples:''
<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;">
<p>100 1# $a Faulkner, William, $d 1897-1962. $t Nouvelles. $k Extraits<br>
400 1# $a Faulkner, William, $d 1897-1962. $t Uncollected stories of William Faulkner<br>
430 #0 $a Uncollected stories of William Faulkner</p>
<br>
<p>
110 1# $a États-Unis. $b Bureau of Labor Statistics<br>
410 2# $a Estados Unidos de América, Buró de Estadísticas Laborales<br>
<span style="font-family:sans-serif"><em>and not</em></span><br>
410 2# $a Estados Unidos de América. $b Buró de Estadísticas Laborales</p>
<br>
<p>
110 2# $a Zhongguo yi ke da xue. $b Fu shu di 1 yi yuan<br>
410 2# $a China Medical University, First Affiliated Hospital<br>
<span style="font-family:sans-serif"><em>and not</em></span><br>
410 2# $a China Medical University. $b First Affiliated Hospital</p>
</div>
</li>
</ul>
''Note :'' S'agissant des notices bibliographiques, usage désigne les formes de noms transcrites que l'on trouve habituellement dans les mentions de responsabilité des notices bibliographiques. On peut également trouver ces formes dans d'autres parties de la notice bibliographique telles que le titre propre ou une note citée. En raison des changements apportés aux instructions de catalogage, les catalogueurs doivent être prudents lorsqu'ils prennent les informations de la mention de publication, de la mention de distribution, etc. et de la mention de collection.
When changing the form of a superordinate body, a geographic name, or a personal name in a 1XX, update all of the existing NARs that use that component in a 4XX, unless the 4XX represents the former authorized access point (e.g., $w/2=e). ''Exception:'' Do not apply this instruction in the case of migrated authority records that have not been re-evaluated.
<span id="4XX$w"></span>
'''Subfield $w – Control subfield'''
When an authorized access point for a person (100) is changed because the person has changed his or her name, record the earlier form of name in a 400 with $w nne if the variant is valid under RDA instructions.
'''Notices d'autorité de collections.''' <br>
''Examples:''
<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;">
100 0# $a François, $c pape, $d 1936-<br>
400 1# $w nne $a Bergoglio, Jorge Mario, $d 1936-
<div style="font-family:sans-serif; margin-left:85px;">
''(Name changed upon election as pope)''
</div><br>
100 1# $a Rancic, Giuliana<br>
400 1# $w nne $a DePandi, Giuliana<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(Nom changé après le mariage)''</div>
</div>
<pre style="font-family:courier new;">
<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>
</ol>
'''Autres fichiers ou catalogues'''
<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) is changed because of a change in cataloging instructions, record the earlier form in a 4XX using $w. If the variant form is a valid reference under current RDA instructions, use $w nne. If the variant form is not a valid reference under current RDA instructions, use $w nnea.
'''Bases de données toponymiques'''
''Examples:''
<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;">
130 #0 $a Bible. $p Matthieu <br>
430 #0 $w nnea $a Bible. $p N.T. $p Matthieu
<div style="font-family:sans-serif; margin-left:85px;">
''(Coded "nne" because the variant is valid in RDA)''
</div><br>
100 1# $a Smith, Jonathan Kennon Thompson, $d 1939-2014<br>
400 1# $w nne $a Smith, Jonathan Kennon
<div style="font-family:sans-serif; margin-left:85px;">
''(Coded "nne" because the variant is valid in RDA; 100 form changed based on usage and dates of birth and death added because 100 was being changed)''
</div> <br>
100 0# $a Périclès, $d environ 495 av. J.-C.-429 av. J.-C.<br>
400 0# $w nnea $a Périclès, $d ca 495-429 av. J.-C.
<div style="font-family:sans-serif; margin-left:85px;">
''(Coded "nnea" because the abbreviation "ca." is not valid for period of activity in RDA)''
</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>
<pre style="font-family:courier new;">
<!--'''SARs'''
''PFAN series practice:'' Transcription of the series statement is mandatory if applicable. Searching for series authority records, providing authorized access points for the series, and the creation and maintenance of series authority records are optional.
Variant access points may be recorded in any SAR, including those for series-like phrases.
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.
-->
[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>]]
= 5XX - See Also From Tracings - General Information =
'''Sources non bibliographiques'''
'''General'''
When otherwise modifying a NAR that contain codes that are no longer used such as subfield $w position zero (0) code “d” or “f,” PFAN catalogers should upgrade the NAR to RDA.
PFAN catalogers applying RDA instructions may use subfield $i in conjunction with subfield $w code “r” for relationship designators. When applying RDA relationship designators in 5XXs, supply terms from Appendix I, J or K; capitalize the initial letter of the term and follow the term with a colon.
For information on the use of relationship designators and/or $w codes in a specific 5XX field, see the section in this Manual for that field.
'''Subfield $w – Control subfield'''
Follow the conventions in the authority format for use of subfield $w. Do not supply subfield $w unless a value other than “n” would be appropriate in one of the positions. When supplying subfield $w,
give it as the first subfield in the field. Supply character positions preceding, but not succeeding, the value, e.g.,
<div style="margin-left:50px;"">
$w a = to indicate a reference from an earlier authorized access point
$w b = to indicate a reference from a later authorized access point
$w r = to indicate that a subfield $i or subfield $4 is used to denote relationship information
$w nnnc = to indicate a see also reference for multiple pseudonyms (record also contains a 663 field)
</div>
'''NARs'''
A see also reference tracing (5XX) must not normalize to the same as another see also reference in the same authority record, unless both 5XX fields contain a relationship designator in subfield $i, and
the texts of the relationship designators are different.
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#670_Source_Data_Found|''Supplement'' <big>⮞</big>]]
<!--'''SARs'''
''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.
'''General'''
-->
[2021-11-03]<!--(2021-11-01)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#5XX_Fields_Tracing_and_References_-_General_Information|''Supplement'' <big>⮞</big>]]
= 500 See Also From Tracing - Personal Name =
'''General'''<br>
Catalogers may use subfield $i with subfield $w coded “r” when providing relationship links between a personal name and 1) the name of another person, family, or corporate body or 2) the authorized access point for a work or expression. This technique may also be used to relate authorized access points for works and expressions containing personal names. When using a term from Appendix I, J or K in subfield $i, use a capital letter for the first letter of the term and follow the term with a colon.
''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 Yentl (Film)
500 1# $w r $i Réalisateur de cinéma : $a Streisand, Barbra
<br><br>
100 1# $a Alcott, Louisa May, $d 1832-1888. $t Little men
500 1# $w r $i Suite de : $a Alcott, Louisa May, $d 1832-1888. $t Little women
</div>
When recording pseudonymous relationships for personal names when only two authority records are involved, catalogers may either 1) use subfield $i and code “r” in subfield $w or 2) use simple see-also references. For more information on these techniques and instructions on recording multiple pseudonyms (i.e., those involving a 663 field), see the [http://www.loc.gov/catdir/cpso/pseud.pdf FAQ – LC/PCC RDA Practice for Creating NARs for Persons Who Use Pseudonyms].
100 1# $a Boyer, Frédéric, $d 1961-<br>
Catalogers are reminded that when a variant name (400) and an authorized access point (100) are in conflict an addition should be made to either the 400 or 100 to resolve the conflict (e.g., fuller form of name, date of activity, etc.); the previous practice of changing the 400 to a 500 to resolve the conflict is no longer an option. When catalogers encounter a variant form in a 500 field in the course of updating a NAR, they should resolve the conflict and change the field to a 400.
<br>
[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>]] | [[PFAN_-_Participant%27s_Manual#Cross-references_.284XX_and_5XX.29_.5BNew.5D|''Manual 4XX and 5XX'' <big>⮞</big>]]
<br>
<div style="font-family:sans-serif;">(''672 field with title proper'')</div>
= 510 See Also From Tracing - Corporate Name =
'''General'''
Follow instructions provided in the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records.
[2021-02-15]<!--(2021-02-10)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#510_See_Also_From_Tracing-Corporate_Name|''Supplement'' <big>⮞</big>]]
= 511 See Also From Tracing - Meeting Name =
'''General'''
Follow instructions provided in the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records.
See [http://original.rdatoolkit.org/lacbanqpschp11_lacbanqps11-478.html BAC-BAnQ PS 11.13.1.8] for guidance on relating authority records for ongoing conferences.
[2021-02-15]<!--(2021-02-10)-->
<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;">
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#511_See_Also_From_Tracing-Meeting_Name|''Supplement'' <big>⮞</big>]]
<br>
<div style="font-family:sans-serif;">(''Date of work'')</div>
= 530 See Also From Tracing - Uniform Title =
'''General'''
Catalogers may use subfield $i with subfield $w coded "r" when providing relationship links between authorized access points for works or expressions. When supplying RDA Appendix J terms in subfield $i, use a capital letter for the first letter of the term and follow the term with a colon.
[2021-02-15]<!--(2021-02-10)-->
[[#toc|''Retour au sommaire'' <big>⮝</big>]] | [[PFAN_-_Guide_des_autorit%C3%A9s_de_noms_-_Suppl%C3%A9ment_MARC_21#530_Rappel_de_renvoi_.C2.AB_voir_aussi_.C2.BB_-_Titre_uniforme |''Supplément'' <big>⮞</big>]]
= 551 See Also From Tracing - Geographic Name =
Do not use subfield $i with subfield $w coded “r” until relationship designators for places are developed. (Currently RDA has a placeholder for Appendix L).
[2021-02-15]<!--(2021-02-10)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#551_See_Also_From_Tracing-Geographic_Name|''Supplement'' <big>⮞</big>]]
= 64X Series Numbering Peculiarities =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#641_Series_Numbering_Peculiarities|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#672_Title_Related_to_the_Entity|''Supplement'' <big>⮞</big>]]
= 673 Title not related to the entity =
= 642 Series Numbering Example =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#642_Series_Numbering_Example|''Supplement'' <big>⮞</big>]]
= 643 Series Place and Publisher/Issuing Body =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#643_Series_Place_and_Publisher.2FIssuing_Body|''Supplement'' <big>⮞</big>]]
= 644 Series Analysis Practice =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#644_Series_Analysis_Practice|''Supplement'' <big>⮞</big>]]
= 645 Series Tracing Practice =
[in $w “#” = space input by cataloger]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#645_Series_Tracing_Practice|''Supplement'' <big>⮞</big>]]
<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;">
= 646 Series Classification Practice =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#646_Series_Classification_Practice|''Supplement'' <big>⮞</big>]]
= 663 Complex See Also Reference - Name =
==== General ====
The 663 field contains the explanatory text and authorized access points for relationships between a 100 (established name) and other 100s (established names) that cannot be adequately conveyed by one or more simple see also references generated from 500 fields.
Generally, this situation occurs when a person uses more than two identities, when more than one person shares an identity with one or more others, or when multiple persons use the same pseudonym independent of each other or as a result of some other arrangement.
The text of the 663 may be adjusted to fit extraordinary situations; however, keep the text as simple as possible, allowing the MARC fields and coding to convey the information desired.
Do not use the 663 technique to show relationships between corporate bodies or between persons and corporate bodies.
More information on creating NARs for persons with alternate identities is found in the [https://wiki.gccollab.ca/images/f/f3/FAQ_%E2%80%93_Pratique_de_LC-PCC_pour_la_cr%C3%A9ation_de_notices_d%E2%80%99autorit%C3%A9_de_nom_pour_les_personnes_qui_utilisent_des_pseudonymes.pdf FAQ – LC/PCC RDA and AACR2 practice for creating NARs for persons who use pseudonyms].
==== Only two identities ====
However, it is not always necessary to include in the 675 field every reference source consulted; use judgment in deciding what sources are important enough to retain in the permanent record.
When only two NARs are created for a person, the NARs are generally connected with 500 see also references and no 663 field. However, when one of the NARs is for a joint pseudonym or a pseudonym used by several persons working independently of each other, the 663 technique is used.
==== More than two identities - "basic" authorized access point and references ====
When more than two authorized access points are created for the same person, identify a “basic” authorized access point using the 663 field technique. This decision is based on the desire to simplify the reference structure and to assist catalogers in determining which name to use as the subject of biographical or critical works. The “basic” authorized access point should be determined by the predominantly used form of name or, lacking sufficient evidence, by choosing the real name of the person as the “basic” form.
On the authority record for the “basic” name authority record add 500 see also references with a subfield w coded “nnnc” from all other names used. Justify the 500 in 670 citations according to normal practice. Provide a 663 field listing all the other names with the following text (may be adjusted to fit the situation):
= 678 Biographical or historical data =
<div style="font-family:courier new; 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;">
'''General'''
663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b [established form of name] $b [established form of
name]
</div>
When supplying biographical or historical data in a 678 note field, construct the note in concise but complete sentences, keeping in mind that the information will be used in public displays.
On each of the other name authority records, trace a 500 see also reference with subfield $w coded “nnnc” from the “basic” name, justifying that reference in a 670 citation, according to normal practice. Other names may be mentioned in the 670 if it is convenient to do so. Provide a 663 field with the following or similar text (may be adjusted to fit the situation):
<div style="font-family:courier new; 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;">
663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b [established form of name chosen as the basic heading]
</div>
When the author uses another new name, create a new name authority record for that name and also add it to the reference structure and 663 listing on the authority record for the “basic” name. References to the new name in the 500 and 663 fields are only added to the “basic” NAR.
''Examples :''
<!--<div style="padding-left:50px;">-->
<div style="font-family:courier new; margin-left:0px; 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">"Basic" NAR:</div>
100 1# $a Harris, John, $d 1916-1991
500 1# $w nnnc $a Hennessy, Max, $d 1916-1991
500 1# $w nnnc $a Hebden, Mark, $d 1916-1991
663 ## $a Pour les œuvres de cette personnes écrites sous d'autres noms, chercher aussi sous : $b Hebden, Mark, 1916-1991 $b Hennessy, Max, 1916-1991
</div>
<div style="font-family:courier new; margin-left:0px; 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 for first 500 on "basic" NAR:</div>
100 1# $a Hennessy, Max, $d 1916-1991
500 1# $w nnnc $a Harris, John, $d 1916-1991
663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b Harris, John, 1916-1991
</div>
<div style="font-family:courier new; margin-left:0px; 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 for second 500 on "basic" NAR:</div>
100 1# $a Hebden, Mark, $d 1916-1991
500 1# $w nnnc $a Harris, John, $d 1916-1991
663 ## $a Les œuvres de cette personne sont identifiées par le nom utilisé dans le document. Pour une liste d'autres noms utilisés par cette personne, chercher aussi sous : $b Harris, John, 1916-1991
</div>
<!--</div>-->
==== Joint pseudonyms ====
A joint pseudonym represents one identity used by two or more persons working in collaboration with each other. If a person uses a joint pseudonym and another name (as found in the catalog), the “basic” authorized access point technique is used.
''Examples :''
<!--<div style="padding-left:50px;">-->
<div style="font-family:courier new; margin-left:0px; 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 for joint pseudonym:</div>
100 1# $a Phillips, Mark
500 1# $w nnnc $a Garrett, Randall
500 1# $w nnnc $a Janifer, Laurence M.
663 ## $a Pseudonyme conjoint de Randall Garrett et Laurence M. Janifer. Pour les œuvres de ces personnes écrites sous leurs propres noms, chercher aussi sous : $b Garrett, Randell $b Janifer, Laurence M.
</div>
<div style="font-family:courier new; padding-right:25px; margin-left:0px; margin-bottom:20px; 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 for first 500 on joint pseudonym NAR:</div>
100 1# $a Garrett, Randall
500 1# $w nnnc $a Phillips, Mark
663 ## $a Pour les œuvres de cette personne écrites en collaboration avec Laurence M. Janifer, chercher aussi sous : $b Phillips, Mark
</div>
<div style="font-family:courier new; padding-right:25px; margin-left:0px; margin-bottom:20px; 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 for second 500 on joint pseudonym NAR: </div>
100 1# $a Janifer, Laurence M.
500 1# $w nnnc $a Phillips, Mark
663 ## $a Pour les œuvres de cette personne écrites en collaboration avec Randall Garrett, chercher aussi sous : $b Phillips, Mark
</div>
==== Pseudonyms used by multiple persons ====
When multiple persons working independently of each other use the same pseudonym and one or more other names (as found in the catalog), the “basic” authorized access point technique is used.
''Examples :''
<!--<div style="padding-left:50px;">-->
<div style="font-family:courier new; margin-left:0px; 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 for pseudonym used by multiple persons:</div>
100 1# $a Robeson, Kenneth
500 1# $w nnnc $a Dent, Lester, $d 1904-1959
500 1# $w nnnc $a Goulart, Ron, 1933-
[…]
663 ## $a Pseudonyme utilisé par plusieurs personnes qui écrivent individuellement. Pour les œuvres de ces personnes écrites sous leurs propres noms ou d'autres noms, chercher aussi sous : $b Dent, Lester, 1904-1959 $b Goulart, Ron, 1933- […]
</div>
<div style="font-family:courier new; margin-left:0px; 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 for first 500 on pseudonym used by multiple persons NAR:</div>
100 1# $a Dent, Lester, $d 1904-1959
500 1# $w nnnc $a Robeson, Kenneth
663 ## $a Pour les œuvres de cette personne écrites sous un autre nom, chercher aussi sous : $b Robeson, Kenneth
</div>
<div style="font-family:courier new; margin-left:0px; 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 for second 500 on pseudonym used by multiple persons NAR: </div>
100 1# $a Goulart, Ron, ‡d 1933-
500 1# $w nnnc $a Robeson, Kenneth
500 1# $w nnnc $a Silva, Joseph, $d 1933-
[…]
663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b Robeson, Kenneth $b Silva, Joseph,1933- […]
<div style="font-family:sans-serif; margin-left:85px;">(''Author has a pseudonym used by multiple persons and individual pseudonyms'')</div>
</div>
<!--</div>-->
[2021-03-10]<!--(2021-03-04)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#663_Complex_See_Also_Reference-Name|''Supplement'' <big>⮞</big>]]
= 667 Nonpublic general note =
==== General ====
Give information of permanent value and general interest that would be useful also to PFAN institutions and outside of PFAN. A representative listing of notes is given below. Generally, wording is recommended but not prescriptive unless specified in the instructions. The separate 667 fields may be given in any order.
''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;">
667 ## $a N'est pas la même personne [ou œuvre] que : [name or title, Canadiana number].
667 ## $a Ne peut être identifié comme étant : [name or title, Canadiana number].
667 ## $a Réexaminer avant de réutiliser.
667 ## $a Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
<br>
<div style="font-family:sans-serif; margin-left:85px;">
''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use OCLC record)''</div>
667 ## $a Codée "provisoire" car [reason for coding].
667 ## $a Date de naissance supprimée de toutes les zones suite à la demande de l'auteur, [date updated].
667 ## $a Pour les œuvres parues avant/après [date].
<br>
<div style="font-family:sans-serif; margin-left:85px;">
(''Used for official language changes'')</div>
</div>
See Appendice 1 in this manual for information and instructions about 667 fields added to authority records as part of a special project.
==== NARs for persons with identities not established ====
When a person uses two or more identities in manifestations, name authority records may be created for each identity. In the interest of efficiency, catalogers may use a 667 field to list pseudonyms not found in publications instead of creating NARs for these unused pseudonyms. In this case, list the unused pseudonyms in a 667 field following the phrase: “Pseudonymes non trouvés dans les œuvres publiées.”
''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;">
667 ## $a Pseudonymes non trouvés dans les œuvres publiées : Miz Scarlett, SCC et Stevenopolis.
</div>
This note may also be added to an NAR for a person who has multiple NARs for multiple identities when some of the pseudonyms are not found in publications. In this case, list only the unused pseudonyms in the 667 field, and follow appropriate instructions for the other pseudonyms.
''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 Gorey, Edward, $d 1925-2000
500 1# $w nnnc $a Dowdy, Regera, $d 1925-2000
500 1# $w nnnc $a Mude, O., $d 1925-2000
663 ## $a Pour les œuvres de cette personne écrites sous d'autres noms, chercher aussi sous : $b Dowdy, Regera, 1925-2000 […]
667 ## $a Pseudonymes non trouvés dans les œuvres publiées : Drew Dogyear, Wardore Edgy,
[…]
</div>
More information on creating NARs for persons with alternate identities is available in the manual, 663 section, and the [https://www.loc.gov/aba/pcc/naco/ LC/PCC Practice for Creating NARs for Persons who use Pseudonyms].
==== NARs for series of conferences, etc. (ÉP de BAC-BAnQ 11.13.1.8.2) ====
Add a 667 field on the NAR for the collective conference when there are authority records for both collective and individual instances of an ongoing conference.
''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;">
110 2# $a Veterinary Orthopedic Society. $b Annual Conference
667 ## $a Voir aussi les points d'accès connexes pour les occurrences individuelles de cette conférence, qui comprennent de l'information spécifique sur le numéro, la date ou le lieu de la conférence individuelle.
</div>
==== NARs and subject usage ====
Apply these instructions when creating new NARs and revising existing NARs.
<div style="margin-left:16px; text-indent:-16px;">1) Add notes indicating subject cataloging usage when an authorized access point is not appropriate for use as a subject heading for these situations:</div>
<ol>
<li type="a">'''Heads of state, etc.'''<br>
This instruction applies to NARS for corporate bodies representing the office when the name of the incumbent is included as part of the authorized access point for the corporate body. See [http://original.rdatoolkit.org/rdachp11-fr_rda11-2653.html RDA 11.2.2.18 (Government Officials)] and [http://original.rdatoolkit.org/rdachp11-fr_rda11-3233.html RDA 11.2.2.26 (Religious Officials)] for instructions on the corporate bodies. Use this 667 note on the NAR for the corporate body to indicate subject cataloging usage:
<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;">
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous [personal name heading].
</div>
Assign value “n” in 008/11 and value “b” in 008/15.
''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;">
008/11 = n
008/15 = b
110 1# $a États-Unis. $b Président (1923-1929 : Coolidge)
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Coolidge, Calvin, 1872-1933.
</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;">
008/11 = n
008/15 = b
110 2# $a Église catholique. $b Pape (1503-1513 : Jules II)
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur cette personne se trouvent sous Jules II, pape, 1443-1513.
</div>
See also [[PFAN_-_Name_Authority_Manual#008.2F11_Subject_heading_system.2Fthesaurus|008/11]] and [[PFAN_-_Name_Authority_Manual#008.2F15_Heading_use-subject_added_entry|008/15]] in this manual.
</li>
<li type="a">'''Earlier/later linear jurisdictional name changes'''<br>
The "politique d'indexation du RVM" is to assign as a subject access point or as a geographic subdivision only the latest name of a political jurisdiction that has had one or more earlier names, as long
as the territorial identity remains essentially unchanged (see "Guide pratique du Répertoire de vedettes-matière de l'Université Laval", 5.14.3.1). When creating a NAR with an earlier/later authorized access point for a place in in this situation, catalogers must add a 667 subject usage note to the authority record with the earlier place name and adjust the appropriate 008 fields (008/11 and 008/15).<br>
''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;">
008/11 = n
008/15 = b
151 ## $a Ceylan
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Sri Lanka.
</div>
</li>
<li type="a">'''NARs for families'''<br>
Authorized access points for families are not valid for subject use. In an NAR for a family, 008/11 should be set to value “n” and 008/15 should be set to “b.” Per LAC-BAnQ PS 10.0, when creating an NAR
for a family add this 667 field noting subject usage:
<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;">
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière; utiliser une vedette de nom de famille provenant du RVM.
</div>
</li>
<li type="a">'''NARs for fictitious characters'''<br>
Authorized access points for families are not valid for subject use. In an NAR for a family, 008/11 should be set to value “n” and 008/15 should be set to “b.” Per LAC-BAnQ PS 9.0, when creating an NAR
for a family add this 667 field noting subject usage:
<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;">
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière; utiliser une vedette de personnage fictif provenant du RVM.</div>
</li>
</ol>
<div style="margin-left:16px; text-indent:-16px;">2) Add this note to a name authority record for a city section indicating that it is not appropriate for use as a geographic subdivision (see SHM H 835 for more information):</div>
<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;">
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme subdivision géographique.
</div>
''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;">
151 ## $a Hollywood (Los Angeles, Calif.)
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme subdivision géographique.
</div>
==== Non-Latin script reference notes ====
In an authority record that contains a non-Latin script variant access point, use the 667 field with a note stating: “Le renvoi en écriture non latine n'a pas été évalué.” If there are multiple non-Latin script variant access points, use a note stating: “Les renvois en écriture non latine n'ont pas été évalués.” Assign 008/29 value “b” to indicate that the variant access point is not evaluated.
''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;">
008/29 = b
100 1# $a Moroz, Valentin, $d 1936-
400 1# $a Мороз, В. Я. $q (Валентин Якович), $d 1936-
400 1# $a Мороз, Валентин Якович, $d 1936-
667 ## $a Les renvois en écriture non latine n'ont pas été évalués.
</div>
==== Duplicates ====
Add the following note to a name authority record that has been reported for deletion:
<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;">
667 ## $a Notice doublon, signalée pour suppression car remplacée par [Canadiana number from the record to keep<span style="color:red>]</span> ([date]).
</div>
[2022-11-10] <!--(2021-03-25)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#667_Nonpublic_General_Note|''Supplement'' <big>⮞</big>]]
= 670 Sources found =
<!--''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.
-->
=== Introduction===
The purpose of this field is to record information about the name or title represented in the 1XX field. It includes facts that contribute to the identification of the entity, that justify the choice of the name
or title and any additional elements used to construct the authorized access point (1XX). The information also justifies, as needed, variant forms of the name or title (4XX), other identifying elements (046, 3XX,
and 678), and clarifies relationships between the 1XX and other entities in the file.
<ol>'''Functions of the 670 field:'''
* To record information, from sources (e.g., books, phone calls, websites), in support of the choice and form of the authorized access point, variants, and other identifying elements
* To store information that may be used to break a conflict later
* To record information on relationships between entities (e.g., a person is the author of a work, a corporate body was absorbed by another corporate body)
* To identify a person with works in diverse subject areas or of diverse forms
* To identify different individuals whose access points must remain identical for now (i.e., undifferentiated personal names)
* To clarify whether different forms of a name or of a title are simply variations or reflect a change in the name or title
* To record research required by the current guidelines
* To facilitate authority and bibliographic file maintenance, i.e., the information in 670 fields aids in making decisions about duplicate authorized access points and misattributions
* To support machine manipulation based on algorithms using information in the 670
</ol>
Generally, the first 670 field cites the resource for which the authority record is being established, i.e., the resource being cataloged. If the resource being cataloged or consulted provides no information to
justify the authorized access point, variants, or other elements recorded in the NAR, see the 675 section of this Manual for instructions on citing the resource in a 675 field.
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.
<ol>'''Best practices for 670 fields:'''
* In subfield $b, summarize and edit information found as needed to avoid extraneous or repetitive information.
* Avoid citing subjective information or information that is of dubious value in identifying an entity within a bibliographic context.
* Exercise caution when recording information about living persons that may be private or controversial in nature.
</ol>
670 fields in existing NARs may not conform to these guidelines. For example, 670 fields in older NARs may lack subfield $b with justifying information. 670 fields in NARs that were part of a special project may not conform to these guidelines and/or may contain information that seems unusual or incorrect.
''Note:'' The examples given throughout the following text have various conventions in regard to punctuation and style. These conventions are not prescriptive and should be considered as best practices to facilitate the exchange of information in a shared database environment. Catalogers are expected to use judgment and common sense. Punctuation and style need not be consistent from record to record as long as the information is clear and accurate.
=== Format of 670 fields ===
'''General'''
With the exception of the eszett (ß or ſʒ) and the euro sign (€), all characters found in the [http://www.loc.gov/marc/specifications/specchartables.html MARC code table] are valid for use in authority records contributed to the Canadiana Authority File ([http://original.rdatoolkit.org/lcpschp1_lcps1-39.html voir LC-PCC PS pour 1.4]). When pasting data from a website into a 670 field, verify that all characters are valid for use in the record. Some non-valid characters resemble those that are valid. For example, the invalid en dash (–) resembles the valid hyphenminus (-).
If a substitution for a symbol that cannot be reproduced is given in brackets (see [http://original.rdatoolkit.org/lacbanqpschp1_lacbanqps1-574.html LAC-BAnQ PS for 1.7.5] et [http://original.rdatoolkit.org/lcpschp1_lcps1-747.html LC-PCC PS for 1.7.5]), an explanation of that interpolation may also be provided.
''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;">
670 ## $a Poch, Dina K. I [love] my in-laws, 2007 : $b page de titre (I [love] my in-laws; "[love]" est représenté par un symbole de cœur sur la page de titre)
</div>
Data must be given in romanized form. Normally it is understood that the cataloger has provided the romanization; therefore, when transcribing romanization found in the source, add after it the bracketed
phrase ['''forme romanisée''']. In such languages as Arabic and Hebrew, where vowels are commonly omitted from the orthography of texts, the cataloger supplies the missing vowels when transcribing data. When
transcribing text that does include the vowels, add after it in brackets ['''vocalisé'''] or ['''en partie vocalisé'''] as appropriate.
If a cataloger chooses to provide nonroman script variant access points, the 670 $b should contain both the nonroman script transcription(s) found in the source, and the systematically romanized form(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;">
670 ## $a Moskovskie matematičeskie olimpiady 1993-2005 g., 2006 : $b page de titre (Р.М. Федоров = R.M. Fedorov)
</div>
When authority records are created using automated authority generation programs, additional information may be included. This data may also be formatted in a different way than instructed in this document. Generally, this data should be retained as generated to maintain the cost effectiveness of this process unless the data is confusing or causes validation errors. The exceptions to this are names and
titles for which NARs are created. Follow the instructions in those sections for recording this data.
'''Subfield $a – Source citation'''
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 date of publication.
<ol>''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;">
670 ## $a Barlow, Nadine G. Mars, 2008 : $b page de titre ([data])
<br>
670 ## $a Socialism (Routledge (Firme)), 2003 : $b page de titre ([data])
</div>
</ol>
Also see the guidelines below for specific categories:
* ''Multipart monographs.'' If the part is the first part, give the date of publication as an open date.
* ''Serials other than monographic series.'' Generally, use a chronological designation instead of a publication date. If there is no designation date, use the numeric designation and the date of publication. Indicate, following the designation statement, if a “surrogate” was used.
<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;">
670 ## $a The Verdict, February 1975 : $b page de titre ([data])
<br>
<span style="font-family:sans-serif"><em>not</em></span><br>
670 ## $a The Verdict, vol. 2, no. 1 (February 1975) : $b page de titre ([data])
<br><br>
670 ## $a Studies in Confederate history, No. 1 (1966), substitut : $b couverture ([data])
<br>
<span style="font-family:sans-serif"><em>not</em></span><br>
670 ## $a Studies in Confederate history, 1966, substitut : $b couverture ([data])
</div>
</ol>
* ''Integrating resources.'' Apply the instructions at [http://original.rdatoolkit.org/rdachp2-fr_rda2-9147.html RDA 2.2.2.4.2] for source of the title proper of a website. Identify the iteration from which information was taken (e.g., “viewed on”dates for updating websites, update number or release number for updating loose-leafs).
<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;">
670 ## $a Internet Broadway database, consulté le 21 janvier 2003 : $b about IBDB (League of American Theatres and Producers)
</div>
</ol>
'''Subfield $b – Information found'''
A 670 field should include the following data in subfield $b:
# The specific location(s) of the information found. For multipart resources with numbered parts, provide the designation of the part and the location within the part (e.g., v. 6, page 10; map recto, label). Abbreviations may be used (e.g., t.p., v. 6).
# Information found. Following the location, cite the information found there, enclosed in parentheses. As appropriate, give multiple occurrences of information from the same source following the location of the information.
<ol>
''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;">
670 ## $a The complete guide to creating enduring festivals, 2015 : $b page de titre (Dr. Ros Derrett, OAM) page xi (Roslyn Derrett)
<br>
670 ## $a Da real world, 1999 : $b conteneur (Beyoncé)
<br>
670 ## $a The World Book encyclopedia, 2010 : $b v. 17, p. 106 (Sand, George ; 1804-1876; nom de plume de Amantine-Lucile-Aurore Dupin)
</div>
</ol>
Also see the guidelines below for specific categories:
* '''CIP.''' If the authorized access point is built from Cataloguing in Publication data, include "CIP" in the location statement (e.g., formulaire du CIP de BAC, page de titre du CIP).
<ol>
<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 The greenhouse approach, 2019 : $b page de titre du CIP (Chitra Anand) formulaire du CIP de BAC (Canadienne)</div>
</ol>
* '''Internet resources.''' For websites, provide the name of the location within the website if appropriate (e.g., about us; history, timeline; government, executive branch).
<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="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>
</ol>
* '''Multiple locations within a resource.'''
<ol>
'''CIP et ressource publiée.''' When adding new information to a 670 field created for a CIP, indicate that the new information is from the published resource.
<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="text-indent:-85px;">
670 ## $a Les salades de Mandy, 2020 : $b formulaire du CIP de BAC (Amanda Wolfe; Canadienne) page de titre (Mandy Wolfe) page 3 (copropriétaire des restaurants Mandy's)</div>
<div style="text-indent:-85px; padding-top:1.3em;">
670 ## $a Comment se fixer des buts et les atteindre, 2021 : $b formulaire du CIP de BAC (Jack Ensign Addington) épreuves du CIP (avocat, pasteur et pionnier de la pensée positive; décédé en 1998) page de titre (Jack Ensign Addington)</div>
<div style="text-indent:-85px; padding-top:1.3em;">
670 ## $a La maternité en toute sérénité, 2021 : $b formulaire du CIP de BAC (Valériane Labroche; Canadienne) dossier du CIP (réside à Montréal; originaire de la France) page de titre (Valériane Labroche) page 3 de la couverture (elle travaille en jeu vidéo en tant que concept artist et directrice artistique, tout en continuant de faire de la BD)</div>
</div>
'''NARs.''' For NARs, generally, use “etc.” to avoid giving more than two locations or a sequence of locations (e.g., p. 316, etc., for sequence p. 316-325, 329-331).
<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 Drevon, André. Alice Milliat, 2005 : $b page de titre (Alice Milliat) p. 9, etc. (née Alice Joséphine Marie Million le 5 mai 1884 à Nantes; morte le 19 mai 1957; athlète féminine)
</div>
<!--'''SARs.''' For SARs, always give each location separately.
''PFAN series practice:'' In post-cataloging authority work without the piece in hand, use the location “ressource non disponible.” If the piece is examined again and the authority record is updated, it is allowable to edit the corresponding 670 field to provide a location and additional forms of series titles as needed.
<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 From child to adult, 1970 : $b ressource non disponible (American Museum sourcebooks in anthropology)-->
</ol>
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of the information'''
Follow the instructions from the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
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. <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:''
<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; 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>
=== Recording names and titles ===
Record names or series titles used in the authorized access point or variant access points in full, as they appear in the source, without abbreviation by the cataloger.
When preparing an authority record for the text of a law or a subject compilation of laws, if a source being cited contains an official short title or citation title, cite that title, preceded by the term
“citation title” and its exact location.
''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;">
670 ## $a Workers' compensation law of the state of North Carolina, c1980 : $b page de titre (Workers' compensation law of the state of North Carolina) titre de référence, p. 49 (The North Carolina Workers' Compensation Act)
</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 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
subfield $b may be omitted, provided no important information is lost.
If information about an earlier or later name or title is found in the same source as the name or title in the authorized access point, give all the information in the 670 field. Do not separate the
information about the earlier or later name or title in order to give it in a 675 field.
''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;">
670 ## $a Strafvollzug, 1985 : $b page de titre (Rechtsgeschichte) p. 2 (Suite de : Veröffentlichungen / Justizministerium Nordrhein-Westfalen)
</div>
=== Recording dates ===
To facilitate international contribution and use of authority records, when recording dates, generally use the spelled out or [https://www.noslangues-ourlanguages.gc.ca/fr/cles-de-la-redaction/mois#2 abbreviated] forms for months. (For dates recorded using automated authority generation programs, see the [[PFAN_-_Name_Authority_Manual#Format_of_670_fields|Format of 670 fields]] section of this document.) Do not change the style of dates in existing records. As a best practice, if a date is not included in subfield $d of the 100 field, consider adding a 046 field if dates are available.
=== Justifying variant access points ===
Justify names or titles given as variant access points by information cited from sources. However, justification is not required in the following cases:
# Variant access points made on the basis of the cataloger's awareness of different romanizations or orthographies;
# A variant title derived from the resource being cataloged, from other resources cataloged under the same access point, or from information in standard reference sources;
# References for authorized access points of corporate bodies reflecting changes due to national orthographic reform, changes in names due to an official language change, or changes involving only a parent body to which the body being established is subordinate.
# Optional references from AACR2 or pre-AACR 2 forms on SARs and on retrospective NARs.
=== Justifying other elements ===
Information recorded in the 046, 3XX, or 678 field of the authority record should generally be justified unless it is otherwise obvious from information recorded in subfield $a of a 670 citation or it can
be easily inferred from other identifying elements recorded, including the preferred name.
For the 046 field and many of the 3XX fields, a subfield $u or subfield $v recorded in the same field may be used instead of or in addition to a 670. See the 046 section of this document for guidelines
on subfield $u and subfield $v.
=== Recording other data ===
'''NARs''' <br>
Use judgment to determine how much data to record in the authority record. Do not abbreviate or translate attributes such as title of the person ([http://original.rdatoolkit.org/rdachp9-fr_rda9-4630.html RDA 9.4]) that appear in conjunction with personal names in statements of responsibility and that potentially could be used as part of the access point. Other data may be abbreviated or summarized. Generally informally translate other data from foreign languages into English, paraphrasing or summarizing as convenient.
<!--'''SARs''' <br>
Use judgment to determine how much data other than forms of the title/phrase to record in the permanent authority record. Numbering and names of issuing bodies are not required but may be given.
-->
=== Special types of citations ===
The most commonly occurring citations are listed below. If these are not appropriate, devise others as needed.
'''Canadiana'''
When converting information found in obsolete or non-active MARC fields (e.g., 664, 665, 666) into a 670 note, cite Canadiana in a citation such as those provided in the examples below:
<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 Information convertie à partir d'une zone 665 dans cette notice, [date of conversion] $b ([data converted from 665 field])
<br>
670 ## $a Information de la zone 665 anciennement dans cette notice ([data moved from 665 field])
</div>
'''LC/NAF, OCLC and fichier interne de BAnQ [BAnQ internal file]'''
Cite these files in zone 670 as follows:
<div style="font-family: courier new; text-indent: -85px; line-height: 1.4; border: 1px solid #eaecf0; background-color: #f8f9fa; padding: 10px 25px 10px 100px;">
670 ## $a LC/NAF, [date of the search] $b (point d'accès : [data]; variantes : [data])<span id="^1"></span>[[#LC/NAF|<sup>[1]</sup>]]
<p>670 ## $a OCLC, [date of the search] $b (point d'accès : [data]; usage: [data])</p>
<p>670 ## $a Fichier interne de BAnQ, [date of the search] $b (point d'accès : [data]; variantes : [data])</p>
</div>
''NARs''. Give the date of the search, using month names or abbreviations. In parentheses, prefaced by the label '''point d'accès :''' or '''points d'accès :''', give the access point (or access points) found, even if it is the same as the current authorized access point. If it is judged useful to mention one or more variants found in an authority record, give them with the label '''variante :''' or '''variantes :'''
If different forms of the name appear in the bibliographic records, record the access point and also any forms found, including usage identical to the authorized access point. Separate the access point from the other forms, and preface the other forms with an appropriate label, e.g., '''usage :'''<span id="^2"></span>[[#Usage|<sup>[2]</sup>]], '''forme non transcrite :''' or '''formes non transcrites :'''<span id="^3"></span>[[#Forme_non_transcrite|<sup>[3]</sup>]].
Do not normally cite specific bibliographic records or the exact location of the variations found.
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="text-indent:-85px;">
670 ## $a OCLC, 7 août 2020 $b (points d'accès : Riva, J.; Riva, J. (John), 1929- ; Riva, John; Riva, John, 1929- ; Riva, John F.; Riva, John Fioretto Valder; usage : John Riva [forme prédominante]; J. Riva; John F. Riva)
</div>
<div style="text-indent:-85px;">
670 ## $a LC/NAF, 7 janvier 2020 $b (point d'accès : Schumann, Clara, 1819-1896; variantes : Shuman, Klara, 1819-1896; Shūman, Kurara, 1819-1896; Vik, Klara, 1819-1896; Wieck-Schumann, Clara, 1819-1896)
</div>
</div>
<!--''SARs.''. Give the date of the search, using month abbreviations, followed by the citation of the bibliographic record. In parentheses give the series statement found in that record.-->
<hr />
<span id="LC/NAF"></span><small>1. [[#^1|^]] LC/NAF has been cited previously under other names, e.g., Base de données LC/NACO and Fichier de LC/NACO.</small>
<br>
<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>
<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>
'''Citing other files or catalogs.'''
If an access point is found in a manual catalog or online database, use judgment in creating a 670 citation. Begin the 670 field with a designation of the catalog/database in which these other bibliographic records were found. There is no prescribed formulation of such citations; examples are listed below:
<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 NUC pre-56 $b ([data])
670 ## $a Catalogue de BAnQ, , [date] $b ([data])
670 ## $a BnF dans VIAF, [date] $b ([data])
670 ## $a Autorités BnF, [date] $b ([data])
670 ## $a SUDOC, [date] $b ([data])
670 ## $a Fichier ISNI de BAnQ, [date] $b ([data])
670 ## $a Advitam, [date] $b ([data])
</div>
'''Geographical Names Database'''
Provide the name of the database and the date searched in subfield $a. In subfield $b provide names given for the entity, feature designation or class (e.g., ADM1, PPL, civil) coordinates, and name of larger place if appropriate. (Other relevant information may also be provided.)Variant names (including non-roman script names) may be given in a single listing as shown below. If possible, use the degree sign (not
superscript zero) to show degrees, use the modifier letter prime for minutes and the modifer letter double prime for seconds.
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="text-indent:-85px;">
670 ## $a Base de données toponymiques du Canada, consultée le 4 décembre 2020 $b (nom : Avonmore; lieu : Stormont; province : Ontario; terme concis : UNP-Lieu non organisé; terme générique : localité; latitude - longitude : 45° 10ʹ 17ʺ N, 74° 58ʹ 2ʺ W; 45.17152, -74.96713)
</div>
<div style="text-indent:-85px;">
670 ## $a Banque de noms de lieux du Québec, consultée le 3 septembre 2020 $b (Rouville; type d'entité : municipalité régionale de comté; établie en janvier 1982, la MRC de Rouville a succédé à l'ancienne municipalité du comté de Rouville d'où elle tire son nom; coordonnées : latitude nord 45° 26ʹ 00ʺ, longitude ouest 73° 03ʹ 00ʺ; coordonnées décimales : -73.05, 45.43333)
</div>
<div style="text-indent:-85px;">
670 ## $a GNIS, consulté le 5 mai 2016 $b (Allegany County; civil, 39°37ʹ17ʺN 078°41ʹ56ʺW, situé au Maryland; variante : Alligany County)
</div>
<div style="text-indent:-85px;">
670 ## $a GEOnet, consulté le 12 avril 2014 $b (Bellinzona [forme approuvée]; PPLA à Ticino, Suisse, 46°11ʹ43ʺN, 009°01ʹ22ʺE; il existe aussi un district du même nom à Ticino)
</div>
<div style="text-indent:-85px;">
670 ## $a GEOnet, consulté le 4 mai 2016 $b (Taitung [forme conventionnelle], Taitung County [forme conventionnelle], Taidong [forme approuvée], Taidong Xian [forme approuvée]; ADM1 à Taiwan, 22°53ʹ01ʺN 121°02ʹ54ʺE; variantes : Taidong Sian; T'ai-tung; T'aitung Hsien; écriture non latine : 臺東縣; 臺東)
</div>
</div>
'''Non-bibliographic sources'''
Give the non-bibliographic source, the date, and the information. The source can be given specifically (« Lettre de l'auteur » , « Appel téléphonique à l'éditeur » , etc.) or in general terms (« Information de l'auteur » , « Information de l'éditeur » , etc.). When noting a specific source, it isn't necessary to show how information was received, e.g, that letter was received via FAX rather than via mail. When a telephone call to a publisher/agency/organization is cited, usually give the name of the group called, rather than the title or name of the person contacted.
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="text-indent:-85px;">
670 ## $a Appel téléphonique à H. Jones, 31 janvier 1992 $b (Harry Jones est le vrai nom de Lionel Jones)
</div>
<div style="text-indent:-85px;">
670 ## $a Lettre de l'auteur, 29 mai 1994 $b (la date de naissance correcte pour ______________ est le 14 octobre 1950)
</div>
<div style="text-indent:-85px;">
670 ## $a Information de l'éditeur, 6 février 1991 $b (le deuxième prénom de James Allan est Stephen, pas Steven)
</div>
<div style="text-indent:-85px;">
670 ## $a Courriel de l'éditeur, 6 avril 2016 $b (__________)
</div>
</div>
<!--'''Citations for republication SARs.'''
If an SAR is for a republication only, begin the 670 with the term for the type of republication and a slash. Do not include a 670 for a republication if the SAR covers both the original and one or more republications. Do not add additional 670 fields for other types of republications cataloged later. (See 64X Series Treatment, Republications for more information about republications.)
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a Édition en gros caractères/La diligence du fou, c1989 : $b page de titre du CIP (Un roman de l'Ouest d'Evans)
</div>
-->
'''Citations for undifferentiated NARs.'''
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]].
[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>]]
= 672 Title related to the entity =
'''General'''
The 672 field may be used to record a title that is related to the entity represented by the 100, 110, 111, or 151 in the name authority record.
For example, in an authority record for a corporate body, 672 fields may be used to record titles for which the corporate body is a creator, issuing body, or subject. The primary purpose of the 672 field is to document that there is a relationship between the 1XX entity and the title recorded in the 672 field.
Use of the 672 field does not negate the need to use the 670 field for the title for which the authority record is being created, nor to use the 670 fields to justify information recorded in the 1XX and 4XX such as preferred and variant forms of name.
New 672 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 672 fields when inputting new 672 fields.
Non-Latin script elements should be given in romanized form.
A title recorded in a 672 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 672 field.
''Examples:''
<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;">
100 1# $a Boyer, Frédéric, $d 1961-<br>
672 #3 $a La consolation<br>
672 #0 $a Yeux noirs
<br>
<div style="font-family:sans-serif;">''(672 fields with titles proper)''</div>
<br>
100 1# $a Boyer, Frédéric
672 #0 $a Cervantes
<br>
<div style="font-family:sans-serif;">''(672 field with title proper)''</div>
<br>
111 2# $a Concile du Vatican $n (2e : $d 1962-1965 : $c Basilica di San Pietro in Vaticano)
672 #0 $a Constitutio de sacra liturgia
<br>
<div style="font-family:sans-serif;">''(672 field with preferred title)''</div>
<br>
151 ## $a Espagne
672 #0 $a Llei d'enjudiciament civil i normes complementàries
<br>
<div style="font-family:sans-serif;">''(672 field with variant title for the work associated with the Catalan expression of the work and date of expression)''</div>
</div>
'''Subfield $b – Remainder of title'''
When recording a title proper, subfield $b may be used to record the other title information or parallel title proper to eliminate confusion for titles needing further identification.
''Examples:''
<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;">
672 #3 $a La rivière $b initiations outaouaises
<br>
<div style="font-family:sans-serif;">''(Subfield $b contains other title information)''</div>
<br>
672 #4 $a Las estrellas $b Stars
<br>
<div style="font-family:sans-serif;">''(Subfield $b contains parallel title proper)''</div>
</div>
'''Subfield $f – Date'''
Subfield $f is used to record a date appropriate to the entity recorded in $a (e.g., use date of work for a preferred title and date of publication for a title proper). Do not use brackets in $f when recording a supplied date of publication or production. Do not give a date of distribution, date of manufacture, or copyright date in $f.
''Examples:''
<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;">
<div style="font-family:sans-serif;">672 for work:</div>
672 #0 $a Amor en los tiempos del cólera $f 1985
<br>
<div style="font-family:sans-serif;">''(Date of work)''</div>
<br>
<div style="font-family:sans-serif;">672 for expression:</div>
672 #2 $a L'amour aux temps du choléra $f 1987
<br>
<div style="font-family:sans-serif;">''(Date of French expression of Amor en los tiempos del cólera)''</div>
<br>
<div style="font-family:sans-serif;">672 for manifestation:</div>
672 #0 $a Miłość w czasach zarazy $f 2005
<br>
<div style="font-family:sans-serif;">''(Date of publication of manifestation of Polish expression of Amor en los tiempos del cólera)''</div>
</div>
'''Subfield $w – Bibliographic record control number'''
Subfield $w is used to record bibliographic record control numbers (e.g., 001, 010, and 016 fields in bibliographic records). It is recommended that catalogers provide $w when readily available. Subfield $w should be repeated for each instance of a separate control number (e.g., an LCCN and an OCLC record number should be provided in separate subfields). For further instructions on inputting record control numbers, see the subfield $w section within the CONSER Editing Guide (CEG) – Section E.
MARC 21 Format for Serials as Applied within CONSER – Variable Data Fields – 76X-78X Linking Entries – Linking Entry Fields General Information.
''Note:'' subfield $w should only be used with titles for the manifestation.
''Example:''
[in $w “#” = space input by cataloger]
<div style="font-family:courier new; padding-left:75px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; text-indent:-60px; border:1px solid #eaecf0; background-color:#f8f9fa;">
672 #0 $a Bread and other bakery products industry $w (DLC)###88646267 $w (OCoLC)3774505 $w (CaOONL)84079116XE
</div>
[2020-12-14]<!--(2020-11-26)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#672_Title_Related_to_the_Entity|''Supplement'' <big>⮞</big>]]
= 673 Title not related to the entity =
'''General'''
The 673 field may be used to record a title that is not related to the entity represented by the 100, 110, 111, or 151 in the name authority record. For example, in an authority record for a person, the 673 may be used to record the titles of works written by a different person with a similar name. The primary purpose of the 673 field is to document that there is no relationship between the 1XX entity and the title recorded in the 673 field.
Use of the 673 field does not negate the need to use the 675 field as described in the [[PFAN_-_Name_Authority_Manual#675_Sources_not_found|675 section]] of this Manual.
New 673 fields may be added after existing ones to record additional titles associated with the entity. Do not routinely delete or change existing 673 fields when inputting new 673 fields.
Non-Latin script elements should be given in romanized form.
A title recorded in a 673 field in subfield $a may be a title proper, title proper of series, preferred title, etc. Titles should be recorded following the appropriate RDA and LAC-BAnQ PS instructions for that element. Apply the same instructions on non-filing characters in the 245 field to record the number of non-filing characters in the second indicator of the 673 field. For specific subfields in the 673 field, apply the same instructions given in the [[PFAN - Name Authority Manual#672 Title related to the entity|672 section]] of this Manual.
''Examples:''
[in $w “#” = space input by cataloger]
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-left:100px; padding-top:10px; padding-right:20px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Boyer, Frédéric, $d 1961-
67<span style="color:red">3</span> #0 $a Cervantes $f 1977
<br>
<div style="font-family:sans-serif;">''(Title proper associated with different Frédéric Boyer)''</div>
</div>
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-left:100px; padding-top:10px; padding-right:20px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
110 2# $a National Gallery of Art (É.-U.)
673 #0 $a Paintings and drawings on the backs of National Gallery pictures $w (DLC)### 47008205 $w (OCoLC)1654530
<br>
<div style="font-family:sans-serif;">''(Title proper associated with the National Gallery in London)''</div>
</div>
BUT NOT
<div style="font-family:courier new; margin-bottom:20px; margin-left:0px; padding-left:15px; padding-top:10px; padding-right:20px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
110 2# $a National Gallery of Art (É.-U.)
673 #4 $a Impressed by light : $b British photographs from paper negatives, 1840-1860
<br>
<div style="font-family:sans-serif;">''(Although the National of Art is not the creator, it is the publisher so this title should be record in a 672)''</div>
</div>
[2021-02-25]<!--(2020-11-26)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#673_Title_Not_Related_to_the_Entity|''Supplement'' <big>⮞</big>]]
= 675 Sources not found =
<!--''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.-->
In April 2012 this field was redefined as: “Citation for a consulted source in which no information is found related in any manner to the entity represented by the authority record or related entities.” PFAN catalogers are not required to change any existing 675 fields simply to meet this new definition.
When creating a new NAR always cite the resource being cataloged in the 675 field if the item being cataloged provides no information related in any manner to the entity represented in the authority record. Also cite in the 675 field other sources consulted that contain no information, when that very lack of information is considered worth recording for future users of the authority record.
''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;">
675 ## $a Oxford classical dictionary, 1996
675 ## $a GEOnet, consulté le 2 avril 2014
</div>
However, it is not always necessary to include in the 675 field every reference source consulted; use judgment in deciding what sources are important enough to retain in the permanent record.
[2021-11-03]<!--(2021-11-01)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#675_Source_Data_Not_Found|''Supplement'' <big>⮞</big>]]
= 678 Biographical or historical data =
'''General'''
When supplying biographical or historical data in a 678 note field, construct the note in concise but complete sentences, keeping in mind that the information will be used in public displays.
''Examples:''
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
678 0# $a Joseph Smith, Jr. (1805-1844) était un prophète mormon et le fondateur de l'Église de Jésus-Christ des saints des derniers jours.
</div>
678 1# $a L'Organisation du traité de l'Atlantique Nord (OTAN) est une alliance politique et militaire créée par la signature du Traité de l'Atlantique Nord, le 4 avril 1949. Elle regroupe des pays membres d'Amérique du Nord et d'Europe. Depuis 1999, plusieurs pays anciennement membres du Pacte de Varsovie ont rejoint l'OTAN, y compris la Hongrie, la Bulgarie et la Roumanie. D'autres pays non-membres participent aux programmes de l'OTAN tels que le Partenariat pour la paix.
In anticipation of LAC building the file in WMS and the batch addition of authority records from other institutions, the contents of all 665 fields in LAC and BAnQ records have been moved to 678 field. The original 665 field may have contained instructions on the access point(s) to be used as author and subject heading :
''Example:''
<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;">
151 ## $a Cascapédia (Québec)
<div style="padding-left:85px; margin-top:0px; padding-top:0px; padding-right: 20px; text-indent:-85px;">
678 1# $a Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules. Comme auteur, on utilise : Cascapédia (Québec) ; Cascapédia-Saint-Jules (Québec) ; Grande-Cascapédia (Cascapédia-Saint-Jules, Québec) ; Saint-Jules (Cascapédia-Saint-Jules, Québec). Comme vedette-matière, on utilise Cascapédia-Saint-Jules (Québec).
</div>
</div>
Delete these instructions in 678 field if they have been retained. Consider adding a 667 field as a subject heading if applicable.
''Example:''
<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;">
151 ## $a Cascapédia (Québec)
<div style="padding-left:85px; margin-top:0px; padding-top:0px; padding-right: 20px; text-indent:-85px;">
667 ## $a UTILISATION COMME VEDETTE-MATIÈRE : Ce point d'accès ne peut pas être employé comme vedette-matière. Les œuvres sur ce lieu se trouvent sous Cascapédia-Saint-Jules (Québec).
678 1# $a Saint-Jules et Grande-Cascapédia fusionnent le 2 juin 1999 pour former Cascapédia. Cascapédia devient le 26 juin 2000 Cascapédia-Saint-Jules.
</div>
</div>
'''Justification of field 678'''
Generally, a 678 field must be justified by a 670 field. If it is not justified and its contents are appropriate for a biographical or historical note, retain the field and add a 670 note citing the internal file of the institution that provided 678 field as follows :
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a Fichier interne de [ [[PFAN_-_Francophone_Name_Authority_Program#Participating_Libraries|abréviation de la bibliothèque participante]] ], [date de consultation de Canadiana] …
</div>
''Example :''
<div style="font-family:courier new; padding-left:100px; margin-top:0px; padding-top:10px; padding-right:25px; padding-bottom:10px; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a Fichier interne de BAC, 29 octobre 2020 $b (établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail)
678 1# $a Établie en 1940, la Commission du salaire minimum devient le 16 avril 1980 la Commission des normes du travail.
</div>
If the record has been modified after being migrated, the record history must be consulted to determine who originally added zone 678.
''Example :''
<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;">
<div style="font-family:sans-serif;">Existing Field 678 which will be deleted as the content is not appropriate for a biographical note.</div>
678 1# $a Né le 6 juin 1973.
<div style="font-family:sans-serif;">670 field added:</div>
670 ## $a Fichier interne de l'ULaval, 29 octobre 2020 $b (né le 6 juin 1973)
</div>
'''Repeatability:'''
Do not repeat this field.
[2020-12-14]<!--(2020-11-26)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#678_Biographical_or_Historical_Data|''Supplement'' <big>⮞</big>]]
= 7XX Heading linking entries =
''Note:'' This section does not apply to the 781 field used in 151 name authority records to provide geographic subdivision information. See Manual, [[PFAN_-_Name_Authority_Manual#781_Subdivision_linking_entry|781 section]], for instructions for that field.
'''General'''
The use of an established heading linking entry 7XX field in an NAR or SAR is limited to recording the authorized access point from a national bibliography or in a separate national authority file or a separate equivalence.
The form of heading in a 7XX field may match the 1XX form or a 4XX form in the same authority record. This is appropriate when the 7XX field form represents a form found in a different authority file than Canadiana.
'''Examples:'''
''Example:''
<pre style="font-family:courier new; padding-left:75px; text-indent:-60px;">
<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 Dion, Céline
700 10 $a Dion, Céline $0 (DLC)n 87834212
</div>
</div>
The source of the heading in the 7XX field may be specified using either second indicator value “7” with subfield $2 or a second indicator value that specifies the source. For access points coming from the LC/NAF file, prefer the second indicator with the value "0".
[2021-03-17]<!--(2021-02-18)-->
<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;">
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
<div style="padding-left:60px; margin-top:0px; padding-top:0px; padding-right: 20px; text-indent:-60px;">
</div>
</div>
'''Example:'''
= 781 Subdivision linking entry =
''PFAN optional practice:'' For a geographic name heading that may also be used as a geographic subdivision, determine the form in which the heading is to be used as a geographic subdivision following the guidelines in instruction sheet [https://www.loc.gov/aba/publications/FreeSHM/H0830.pdf H 830 of the ''Subject Headings Manual'']. Enter the text of the geographic subdivision form in a 781 field with second indicator 0. For a geographic heading that is used directly, such as a country, enter the data in a single $z subfield. For a geographic heading that is used indirectly through a larger geographic entity, such as a city, enter the data in two successive $z subfields. Use no other subfields. Make no changes to values in bytes of the 008.
'''Justification of field 678'''
''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;">
151 ## $a France
781 #6 $z France
<br><br>
151 ## $a Paris (France)
781 #6 $z France $z Paris
<br><br>
</div>
</div>
151 ## $a Lycie
781 #6 $z Turquie $z Lycie
781 #6 $z Turquie $z Lycie
<br><br>
151 ## $a Sydney (N.-G. du S.)
151 ## $a Sydney (N.-G. du S.)
781 #6 $z Australie $z Sydney (N.-G. du S.)
781 #6 $z Australie $z Sydney (N.-G. du S.)
<br><br>
151 ## $a León (Espagne : Province)
151 ## $a León (Espagne : Province)
781 #6 $z Espagne $z León (Province)
781 #6 $z Espagne $z León (Province)
</pre>
</div>
Do not add a 781 field to a record for a geographic name heading that is not appropriate for use as a subject added entry (008/15 value Ab@), such as the earlier name of a jurisdiction that has undergone a linear name change, for example, '''Ceylon'''.
Do not add a 781 field to a record for a geographic name heading that is not appropriate for use as a subject added entry (008/15 value Ab@), such as the earlier name of a jurisdiction that has undergone a linear name change, for example, '''Ceylon'''.
Follow these guidelines for newly-created authority records. Add a 781 field to an existing record when making any other change to it. If revising an existing record that contains a 667 field subject cataloging usage note indicating the proper geographic subdivision form, delete the 667 field and replace it with a 781 field.
Follow these guidelines for newly-created authority records. Add a 781 field to an existing record when making any other change to it. If revising an existing record that contains a 667 field subject cataloging usage note indicating the proper geographic subdivision form, delete the 667 field and replace it with a 781 field.
[2020-12-16]
[2021-03-11]<!--(2021-03-05)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#781_Subdivision_Heading_Linking_Entry-Geographic_Subdivision|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#781_Subdivision_Heading_Linking_Entry-Geographic_Subdivision|''Supplement'' <big>⮞</big>]]
= Appendix 1: Undifferentiated entities =
= Appendix 1: Undifferentiated entities =
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
= Appendix 2: Special projects =
This appendix presents information regarding some special projects involving authority records created or modified in the Canadiana authority file. The records created or modified within the context of these special projects may include some fields or some values not normally attributed according to current cataloguing policies.
Instructions regarding changes to these records are given here in order to indicate whether these fields and values are to be kept or not.
=== Project 1. Records created or revised as part of the UQAM records revision project ===
<ol>
'''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>
When added to Canadiana, these new records contained the following elements: <br>
* In the Leader/17, the value was "o" (Incomplete authority record).
* The following 667 note was added: NOTICE EN COURS DE RÉVISION (UQAM).<br>
<br>
'''B) Instructions for revision of the record'''<br>
These records may be modified, like any other name authority records, according to current cataloguing policies.
When cataloguers update these records, they should:
* Change the value of position Leader/17 to "n" (full record);
* Delete field 667 "NOTICE EN COURS DE RÉVISION (UQAM)";
* Evaluate the record as they would evaluate any batch-loaded record. However, as the record is being revised, the authorized access point may be modified, if it does not follow the current PFAN practices (for instance, birth or death dates may be added, if available and if omitted from the access point).
</ol>
=== Project 2. Records created and revised as part of the Universities Mentoring Project ===
<ol>
'''A) General Information'''<br>
This mentoring project <span style="color:red>that, as of February,</span> allows university libraries to create name authority records that are revised by another university. Authority records created or modified by <span style="color:red>mentored libraries</span> are revised by library technicians <span style="color:red>at the mentoring university.</span> <br>
When added to Canadiana, these new records contained the following elements: <br>
* In the Leader/17, the value was "o" (Incomplete authority record).
* The following 667 note was added: NOTICE EN COURS DE RÉVISION (PROJET DE MENTORAT [abbreviation, e.g. UdeS, ÉTS, UQTR<span style="color:red>, etc.</span>]). <br>
<br>
'''B) Instructions for revision of the record''' <br>
These records should not be modified.<br>
</ol>
[2022-07-15] <!--(2022-07-15)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
<br>
<br>
[[Category:PFAN]]
[[Category:PFAN]]
