1,990
edits
Changes
Jump to navigation
Jump to search
Line 161:
Line 161: − + Line 173:
Line 173: − + Line 182:
Line 182: + − <span style="color:red">If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use record number.</span> Line 305:
Line 305: + + Line 330:
Line 332: − + − <span style="color:red">If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number.</span><br>+ − [2021-03-25]<!--(2021-03-25)--> − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F32 Undifferentiated personal name|''Supplement'' <big>⮞</big>]] − + + − + − + − '''Provisional''' (008/33 value “c”) records:+ − <div style="margin-left:25px; margin-bottom:25px;">+ − '''General'''<br> − <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>+ − '''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> − <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> − − </div> − − + − + + + + − + − + − + − + − + + + + + + + + + + − + + + + − ''PFAN series practice:'' Transcription of the series statement is mandatory if applicable. Searching for series authority records, tracing the series, and the creation and maintenance of series authority records+ − are optional.+ − 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 ==+ − + − 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-03-09]<!--(2021-03-04)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#008.2F39_Cataloging_source|''Supplement'' <big>⮞</big>]]+ − + − 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. + − + − Do not “reuse” a Canadiana number. Once an authority record has been created for a given entity, and once a Canadiana number has been attributed, do not change the data in this authority record to describe a DIFFERENT entity. For instance, do not change the authority record for “Dupont, Jean” to transform it into an authority record describing “Tremblay, Marie” (except if the person’s name has changed). + + + + + + + − <ol>'''PFAN'''+ − <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> − '''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>+ + − + − + − + − + + + + − 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:+ − − − 667 $a Version imprimée : ISSN YYYY-ZZZZ − 667 $a Version en ligne : ISSN YYYY-ZZZZ+ − − 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-03-09] <!--(2021-03-03)-->+ − + + + + + + + − + − + − 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.+ − [2021-03-09]<!--(2021-03-04)-->+ − + + + − = 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).+ + − <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+ − + − :'''Decimal degrees''': record in the form hddd.dddddd (hemisphere-degrees.decimal degrees) − <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+ − </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) − <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>+ − <div style="font-family:sans-serif; margin-left:50px;">''(Example without the optional plus sign)''</div> − </div> − :'''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). − <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>+ − + − 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> − '''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 [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. + − − − 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. + − _____+ + + − + − [2021-03-09]<!--(2021-03-08)-->+ − + + − + − + + − 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 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]. + − ''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)+ − </div>+ − <div style="margin-top:25px;"> − 046 ## $k 1981 $2 edtf − 100 1# $a Allende, Isabel. $t Casa de los espíritus+ + − + − </div> − </div> − 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 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. + + + + + − '''Subfield $s – Start period, and $t – End period'''+ − For instructions on using $s and $t for start and end periods in fields 368, and 370-376, see the instructions provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field. + + − '''Subfield $u – Uniform Resource Identifier and Subfield and Subfield $v – Source of information'''+ − The following represents PFAN practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670: + − <ol> − <li>670s must be used to support information used as part of a heading in 1XX and 4XX fields.</li> − <li>For fields 046, 368, 370-378, and 381:+ − <ol> − <li type="a">use of $v is optional if the same information/source is already cited in the 670</li> − <li type="a">use $v if the information/source is not cited in a 670</li>+ − + − + − + − − 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). + − + + + + + − If the information was derived from a tangible source (e.g., a print book, removable digital media) subfield $v should contain sufficient information for a cataloger to find the item cited in a catalog+ − or bibliographic database. This can usually be limited to title proper and imprint or date. If that combination is not unique, the title citation may be preceded by the creator’s name − '''For online resources:'''+ − Provide information sufficient to find the resource via a search engine. Include either title and publication date (if it is a formally-published resource, such as an e-book) or a suitable description of the+ − document and date accessed (for a less formal resource). Optionally include subfield $u. − ''Example:''+ − + − 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+ − + − [2021-02-19]<!--(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>]]+ + − + + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#053_LC_Classification_Number|''Supplement'' <big>⮞</big>]]+ − = 055 Library and Archives Canada Call Number =+ + + − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#055_Library_and_Archives_Canada_Call_Number|''Supplement'' <big>⮞</big>]]+ − + + + − <br>[[#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>]]+ + + − + + + − + − + − '''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.+ − + − 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.+ + − + + + − + + + − + − # − #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]. + + − + + − <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 type="a">other title information;</li>+ − + − <li type="a">parallel title(s);</li>+ − + − <li type="a">numeric/chronological designations.</li>+ − </ol> − </li> − + − − 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-03-09]<!--(2021-03-03)-->+ − + + − = 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:+ − # 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:'' − <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> − 100 3# $a Jones (Famille : $d 1801-1950 : $c New York, N.Y. : $g Jones, Samuel, 1830-1899) − </div> + − '''''Authorized access points for persons'''''+ − 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.+ − <ol>'''Example:''' + − <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> − 100 0# $a Élisabeth $b Ire, $c reine d'Angleterre, $d 1533-1603 $c (Esprit) − </div></ol> − 2) Generally add subfield $c before subfield $q when also adding words, numerals, etc. indicating relationship. (See [http://original.rdatoolkit.org/rdachp9-fr_rda9-2234.html/view RDA 9.2.2.9.5] for treatment of Portuguese names)+ − <ol>''Example:'' − <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> − 100 1# $a McCauley, Robert H., $c Jr. $q (Robert Henry), $d 1913-1979 − </div> − BUT + − <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> − 100 0# $a M. Alicia $q (Mary Alicia), $c Sister, S.C.N. − </div></ol> − 3) For exceptional situations, such as when subfield $a contains only a surname or only a forename or the name includes a prefix, etc. consult [http://original.rdatoolkit.org/lcpschp1_lcps1-224.html LC-PCC PS 1.7.1].+ + + + + + + − [2021-02-19]<!--(2020-12-08)--> − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#100_Heading-Personal_Name|''Supplement'' <big>⮞</big>]] − = 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.” + − '''Subfield $a – Content type term'''+ − Use terms from [http://original.rdatoolkit.org/rdachp6-fr_rda6-3421.html/view RDA 6.9.1.3]. The list of terms is also available in the [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].+ − '''Subfield $b – Content type code'''+ + + − If giving subfield $b instead of/or in addition to subfield $a, use the code from the MARC format [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].+ + − [2021-02-15]<!--(2021-02-15)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#336_Content_Type|''Supplement'' <big>⮞</big>]] − = 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:''+ + + + + + + + + + + + + + + + − 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> − + + + + − 368 ## $c Personnage du cycle arthurien+ − <br><br> − 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+ − </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.+ − + − <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+ − + − 100 1# $a Walsh, Joseph-Alexis, $c vicomte, $d 1782-1860+ − 368 ## $d vicomte+ − </div> − '''Repeatability:'''+ − In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.+ − ''Example:''+ − + − 368 ## $c Saints $2 rvmgd − + − + − ''(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 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+ + − [2021-03-09]<!--(2021-03-02)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#368_Other_Attributes_of_Person_or_Corporate_Body|''Supplement'' <big>⮞</big>]] − = 370 Associated place =+ + − '''General'''+ − 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:''+ − <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> − + − 370 ## $e Washington (État) $2 lacnaf + + + − <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> − <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">+ − Form of name as part of preferred name of a local place:</div>+ − 151 ## $a Rimouski (Québec)+ − </div><br>+ − + − <div style="font-family:sans-serif"> − Geographic name in Canadiana : </div> − 151 ## $a Congo (République démocratique) − <div style="font-family:sans-serif; margin-left:85px;">''(Authorized access point for the place includes an other designation)''</div> − <br> − <div style="font-family:sans-serif"> − Authorized access point recorded in 370:</div> − 370 ## $c Congo (République démocratique) $2 lacnaf − <div style="font-family:sans-serif">+ − 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> − − <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> − − <div style="font-family:sans-serif"> − Authorized access point recorded in 370:</div> − 370 ## $e Lubumbashi (Congo) $2 lacnaf − <div style="font-family:sans-serif">+ − 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 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. − 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.+ + + − + − + + + + + + + + + − + − + − + − + + − ''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.+ − [2021-03-10]<!--(2021-03-03)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#370_Associated_Place|''Supplement'' <big>⮞</big>]] − = 371 Address =+ − + − + − 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 should contain only an e-mail address. Do not add an internet address for the 1XX in this field.+ − + − + − + − Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.+ + + + + + + + + − '''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''+ + + − Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.+ + + + + + + + + + + + + − [2021-03-10]<!--(2021-03-02)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#371_Address|''Supplement'' <big>⮞</big>]]+ − + − = 372 Field of activity =+ + + + + + + + + + − + + + + + + + + + + + + + + − 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).+ − + − + − + − 372 ## $a Japon--Histoire $2 rvm+ − + + − + + + + + − ''Example:''+ − Authorized access point in Canadiana:+ − + − 130 #0 $a Bible. $p Nouveau Testament+ − </div>+ − Field of activity in 372:+ − − 372## $a Bible. Nouveau Testament $2 lacnaf − − + + + − 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 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. + + − + − 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)-->+ − + + + + − = 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. − + − + − 110 2# $a Canadiens de Montréal (Équipe de hockey)+ + + + + + + + + + + − <div style="font-family:sans-serif;">Authorized access point in 373:</div>+ − 373 ## $a Canadiens de Montréal (Équipe de hockey) $2 lacnaf − </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> − + − In choosing between repeating a field and repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.+ + + − ''Examples:''+ − <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 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-03-10]<!--(2021-03-02)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]] − − = 374 Occupation = − '''General''' − − 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. Line 1,241:
Line 1,257: − + − + − '''PFAN''' − When recording a term indicating gender, prefer the terns ''masculin'' and ''féminin''. For these terms, do not capitalize or indicate the source of the term in the $2 subfield. If neither of these terms is appropriate or sufficiently precise, record an appropriate term or phrase preferably using a controlled vocabulary, such as the RVMGD or the [https://www.btb.termiumplus.gc.ca/publications/diversite-diversity-eng.html ''Gender and sexual diversity glossary''], recording the source in subfield 2. For consistency, capitalize the first term in each subfield $a for terms other than ''masculin'' and ''féminin''. When terms are not taken from a controlled vocabulary, use the singular form. Use terms rather than ISO 5218 codes.+ − '''Repeatability:'''+ − − In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the corresponding subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity. − 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 + + + + + + + − + − Codes from the [http://www.loc.gov/standards/sourcelist/gender.html Gender Source Codes] list may be recorded in subfield $2 for the 375 field.+ + − + + + − Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.+ + + + + + − ______+ − + − 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.+ − + − − − − = 376 Family information = + − + − vocabulary, use a singular form. − + + + + − 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.+ + + − + + + − 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.+ + + − + − Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.+ − + + + + − Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.+ − [2021-03-10]<!--(2021-03-02)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#376_Family_Information|''Supplement'' <big>⮞</big>]]+ − + + + − '''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'''+ + − + − ''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 − 377 #7 $a acr $2 iso639-3+ − + − − − [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.+ − 378 ## $q Kay Dean+ − </div> − − − + − + − + + − 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.+ − + − + − + − 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> − '''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-02-22]<!--(2021-02-19)-->+ − <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 − 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> − 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. − + − <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;"> − ''(Corporate body recorded as associated group and other distinguishing characteristic of work)''</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.+ − ''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> − </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. + + + − + + − 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. − + − Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field. + − [2021-03-10]<!--(2021-03-02)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#381_Other_Distinguishing_Characteristics_of_Work_or_Expression|''Supplement'' <big>⮞</big>]]+ + − = 382 Medium of performance =+ + − '''General'''+ − Record the medium of performance using thesaurus terms from "Moyens d'exécution en musique du RVM (RVMMEM)". Record the medium of performance by applying the instructions at [http://original.rdatoolkit.org/rdachp6-fr_rda6-4362.html RDA 6.15.1.3–6.15.1.6], the associated LAC-BAnQ PSs. ''Note:'' The 382 field may also be used in authority records for expressions.+ + − '''Repeatability:'''+ − If the vocabulary source differs, repeat the field. If considered important for identification and access, provide an additional 382 that does not apply these guidelines.+ + − [2021-03-10]<!--(2021-02-19)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#382_Medium_of_Performance|''Supplement'' <big>⮞</big>]] − = 383 Numeric designation of musical work =+ − + + − Best practice: Encode when available. Create separate 383 fields for different numbering schemes associated with a single work. + − − [2021-02-22]<!--(2021-02-19)--> − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#383_Numeric_Designation_of_Musical_Work|''Supplement'' <big>⮞</big>]] − − = 384 Key = − 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 =+ − + + + − PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.+ − [2021-02-22]<!--(2021-02-19)--> − <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 = − '''General'''+ − PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.+ − [2021-02-21]<!--(2021-02-19)-->+ − <br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]+ − = 4XX - See From Tracings - General Information =+ − + + + + − 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:+ + − <ul>+ − + − <dl>+ − <dd>○ Use cataloger's judgment;</dd> − <dd>○ No limitation on the number or form of references;</dd> − − <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;"> − 100 1# $a Bucknum, David W. − 378 ## $q David Walter+ − + − + − </dd> − − </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).+ − <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.+ + + + − <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> − + − <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> − 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.+ + + + − + − + − 100 0# $a François, $c pape, $d 1936-<br>+ − 400 1# $w nne $a Bergoglio, Jorge Mario, $d 1936-+ + + + + + − + − </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> − + + + + − 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-03-10] <!--(2021-03-03)-->+ − <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., − + − $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> − + + − 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. − + − ''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-03-10]<!--(2021-03-03)-->+ − <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>]] − + + + − '''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 :''+ − + − 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]. + − + − 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.+ − [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>]] − + + + − '''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 =+ + − + − 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)-->+ − <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>]] − = 530 See Also From Tracing - Uniform Title = − 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.+ − + + − [[#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>]] − + − 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>]] − + + + + − <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#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 =+ − + + + − = 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 ==== + − 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.+ − − − 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.+ − ''Examples :''+ − + − + − + + + − + + + − 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 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> − + − + + + + + + + + + + + + + + + + + + + + + − 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.+ − + − + − <!--<div style="padding-left:50px;">-->+ − + − + − + − + − + − 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 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 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+ − + + + − + − 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 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+ − − − <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 =+ − + + + − 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].+ − + − − − 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.”+ − ''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.+ − + − − 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> − + − <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.+ − + − + − 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.+ + + − </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:+ − − − 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> − + + + + + + − 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. − − ''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.+ − + − ==== 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.+ − + − + − 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.+ + − + + + + + + + + − 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 ([date])].+ + − [2021-03-25] <!--(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>]] − + + − ''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. − + − * 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 − − 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. + − + + + + − === 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) − 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) − 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''.+ − + + + + − + − + − 670 ## $a Barlow, Nadine G. Mars, 2008 : $b page de titre ([data]) − − 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>+ − + − 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]) + + + − <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).+ − + − + − 670 ## $a Internet Broadway database, consulté le 21 janvier 2003 : $b about IBDB (League of American Theatres and Producers)+ − </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é)+ − + + + − 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 style="text-indent:-85px;">+ − − <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) − </div> Line 2,287:
Line 2,552: − + Line 2,341:
Line 2,606: − + − − + Line 2,383:
Line 2,647: − + Line 2,455:
Line 2,719: − + Line 2,462:
Line 2,726: − + − + Line 2,614:
Line 2,878: − + Line 2,629:
Line 2,893: − + Line 2,785:
Line 3,049: − + − + − +
PFAN - Name Authority Manual (view source)
Revision as of 12:08, 18 January 2023
, 12:08, 18 January 2023→670 Sources found
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 name record:
* Always create a new name authority record for that person, with distinguishing information, and add an indication that the person was formerly on an undifferentiated record (see "[[PFAN_-_Name_Authority_Manual#667_notes_on_records_for_identities_previously_on_undifferentiated_records|667 notes on records for identities previously on undifferentiated records]]" below). If an authority record already exists for that person with the 667 note "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" <span style="color:red">and coded "a" in field 008/32</span>, use that notice as the "new record".
* Always create a new name authority record for that person, with distinguishing information, and add an indication that the person was formerly on an undifferentiated record (see "[[PFAN_-_Name_Authority_Manual#667_notes_on_records_for_identities_previously_on_undifferentiated_records|667 notes on records for identities previously on undifferentiated records]]" below). If an authority record already exists for that person with the 667 note "CETTE NOTICE VERSÉE EN LOT DOIT ÊTRE ÉVALUÉE AVANT D'ÊTRE UTILISÉE, POUR S'ASSURER QU'ELLE RÉPONDE AUX NORMES DU PFAN" and coded "a" in field 008/32, use that notice as the "new record".
* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
* Transfer the citation 670 pertaining to that person from the undifferentiated name record to the new name authority record and edit as necessary.
* 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".
* 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".
<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 ») <span style="color:red">and coded "a" in field 008/32</span>, 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:
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;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
667 ## Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
667 ## Anciennement incluse dans une notice de nom indifférenciée : [Canadiana number of undifferentiated name record].
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number.)''</div>
</div>
</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>
<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>
</ul>
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
008/32 = b
008/32 = b
<span style="color:red>016 ## $a 0000X0000F</span>
100 1# $a Bowman, Anne
100 1# $a Bowman, Anne
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
667 ## $a Anciennement incluse dans une notice d'autorité de nom indifférenciée : [Canadiana number of undifferentiated name record].
667 ## $a Anciennement incluse dans une notice d'autorité de nom indifférenciée : [Canadiana number of undifferentiated name record].
<div style="font-family:sans-serif; margin-left:50px;">''(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use the OCLC record number.)''</div>
</div>
</div>
<br>
== 008/33 Level of establishment ==
==== <span style="color:red">Records coded as undifferentiated that actually represent only one identity</span> ====
<span style="color:red">Occasionally an existing record will be coded undifferentiated, but new research indicates that in fact the record represents only one identity.
'''NARS'''
''<span style="color:red">Example :</span>''<br>
<div style="margin-left:25px; margin-bottom:25px;">
<span style="color:red"><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
667 ## $a Cas possible d'homonymie avec l'autrice et illustratrice de : Le cadeau de Kato, 2016 (Claire Lemieux)
670 ## $a Ds: Bouchard, J. Espace mathématique 1 (illustratrice)
</div>
In this situation, do the following:
<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;">
<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>
667 ## $a Notice d'autorité de nom indifférenciée représentant une seule identité; signalée pour suppression. </li>
</ol>
</div>
<div style="margin-left:25px; margin-bottom:25px;">
<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>
'''Preliminary''' (008/33 value “d”) records:<br>
<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 record number..)''</div></li>
<div style="margin-left:25px; margin-bottom:25px;">
<li>Add in 016 field subfield $z the Canadiana number of the undifferentiated name authority record to be deleted, if any.</li>
<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>
<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>
<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>
<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>
</div>
Suggested generic message:
</div>
<div style="padding-left:50px; width:500px;">
<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>
La notice doit être vue par un catalogueur.<br>
Notice à conserver :<br>
Notice à conserver :<br>
Notice à supprimer : <br>
</div>
</div>
<!--'''SARs'''
BAC cataloguer: Delete the undifferentiated authority record.
</ul>
<br>
''Example of an undifferentiated record that represents a single identity''
<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
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
''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.
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)
<!--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). -->
</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">Undifferentiated authority record after disambiguation :</div>
= 016 National Bibliographic Agency Control Number =
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
'''Duplicates'''
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)
[...]
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>
[2021-03-02]<!--(2021-03-02)-->
[2022-02-09]<!--(2022-02-09)-->
<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>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement#008.2F32 Undifferentiated personal name|''Supplement'' <big>⮞</big>]]
= 022 International Standard Serial Number =
== 008/33 Level of establishment ==
''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.
'''NARS'''
<div style="margin-left:25px; margin-bottom:25px;">
'''Provisional''' (008/33 value “c”) records:
<div style="margin-left:25px; margin-bottom:25px;">
'''General'''<br>
'''General'''<br>
<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; padding-right:25px; padding-left:15px; padding-top:10px; padding-bottom:10px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
'''Special administrative regions of Hong Kong and Macau'''<br>
</div>
<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>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#022_International_Standard_Serial_Number|''Supplement'' <big>⮞</big>]]
<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>
= 024 Other standard identifier =
<div style="margin-left:25px; margin-bottom:25px;">
'''General'''<br>
'''Preliminary''' (008/33 value “d”) records:<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>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#024_Other_Standard_Identifier|''Supplement'' <big>⮞</big>]]
</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.
'''Recording coordinates for countries, states, counties'''<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). -->
[2021-11-03]<!--(2021-10-20)-->
</div>
<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).
<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>
<div style="font-family:sans-serif; margin-left:50px;">''(Example showing decimal degrees)''</div>
______<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>
<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>
[2022-01-26]<!--(2022-01-26)-->
<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:
<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”).
'''Subfield $d – Modifying agency'''<br>
[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>]]
'''Subfield $e – Description conventions'''<br>
= 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.
[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 =
'''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.
'''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).
:'''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
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#042_Authentication_Code|''Supplement'' <big>⮞</big>]]
</div>
:'''Decimal degrees''': record in the form hddd.dddddd (hemisphere-degrees.decimal degrees)
= 046 Special coded dates =
<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
'''General'''
</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)
<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>
<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.
034 ## $d 079.533265 $e 086.216635 $f -012.583377 $g -020.419532<br>
<div style="font-family:sans-serif; margin-left:50px;">''(Example without the optional plus sign)''</div>
</div>
:'''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;">
<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;">
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).
<div style="margin-top:25px;">
<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>
</div>
<div style="margin-top:25px;">
'''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''].
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)
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 $2 – Source of date scheme'''
'''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.
_____
<li type="a">use of $u is optional, and should always be preceded by $v</li>
'''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).
</ol>
[2021-03-09]<!--(2021-03-08)-->
</li>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#042_Authentication_Code|''Supplement'' <big>⮞</big>]]
</ol>
'''Subfield $v – Source of information'''
= 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).
<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.
'''For tangibles sources:'''
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].
''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)
<div style="margin-top:25px;">
<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 -0199~ $2 edtf
100 0# $a Hellanicus $c (Grammairien), $d environ 200 av. J.-C.
670 ## $a Capitalismo de laçeos, 2011 : $b page de titre (Sérgio G. Lazzarini)
670 ## $a Brill's new Pauly, consulté le 2 août 2011 $b (Hellanicus; grammairien d'Alexandrie; environ 200 av. J.-C.)
</div>
</div>
<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)
</div>
= 053 LC classification number =
<div style="margin-top:25px;">
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)
</div>
</div>
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).
= 065 Other Classification Number =
''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 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.
'''Subfield $2 – Source of date scheme'''
Always add subfield $2 edtf except after a century.
'''Subfield $s – Start period, and $t – End period'''
For instructions on using $s and $t for start and end periods in fields 368, and 370-376, see the instructions provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''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>
= 087 Government Document Classification Number =
<li>For fields 046, 368, 370-378, and 381:
<ol>
<li type="a">use of $v is optional if the same information/source is already cited in the 670</li>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#087_Government_Document_Classification_Number|''Supplement'' <big>⮞</big>]]
<li type="a">use $v if the information/source is not cited in a 670</li>
= 1XX Headings - General Information =
<li type="a">use of $u is optional, and should always be preceded by $v</li>
</ol>
</li>
</ol>
Use a 670 field if needed to justify information recorded in other fields for which subfields $u and/or $v are not defined or defined differently.
'''Subfield $v – Source of information'''
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).
'''SARs'''
'''For tangibles sources:'''
If the information was derived from a tangible source (e.g., a print book, removable digital media) subfield $v should contain sufficient information for a cataloger to find the item cited in a catalog
or bibliographic database. This can usually be limited to title proper and imprint or date. If that combination is not unique, the title citation may be preceded by the creator’s name
For the title proper of a multipart monograph, consult [http://original.rdatoolkit.org/rdachp2-fr_rda2-2781.html/view RDA 2.1.2.3].
'''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.
''Choosing a monographic series title proper:''
''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.
#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].
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>
''Establishing an SAR access point:''
[2022-11-10]<!--(2022-11-10)-->
<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 =
<li>Exclude from the authorized access point the following information included in the series statement in the bibliographic record for the component part:
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#050_Library_of_Congress_Call_Number|''Supplement'' <big>⮞</big>]]
<ol>
<li type="a">initial article in subfields $a, $t, $n, and $p;</li>
= 053 LC classification number =
<li type="a">statement of responsibility;</li>
<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 =
<li type="a">ISSN;</li>
<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 =
<li>Add a parenthetical qualifier(s) if appropriate according to the guidelines in LAC-BAnQ PS 6.27.1.9.</li>
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#065_Other_Classification_Number|''Supplement'' <big>⮞</big>]]
</ol>
= 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>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN - Name Authority Manual - MARC 21 Supplement|''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 =
'''General'''
'''General'''
PFAN catalogers should consult the [https://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html PCC Post RDA Test Guidelines] for instructions on using RDA and/or AACR2 in new and existing authority records.
When modifying an authority record for any reason, delete a final mark of punctuation in the 1XX field unless it is a part of the data (e.g., a period in an abbreviation) or is called for by the cataloging
instructions (e.g., a parenthetical qualifier).
Note: in order to minimize the impact of database maintenance with associated bibliographic records and/or related authority records, catalogers are urged to refrain from making unnecessary changes to 1XXs.
<!--'''SARs'''
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:
# 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:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 3# $a Jones (Famille : $d 1801-1950 : $c New York, N.Y. : $g Jones, Samuel, 1830-1899)
</div>
'''''Authorized access points for persons'''''
'''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.
100 0# $a Palamède $c (Personnage du cycle arthurien)
<ol>'''Example:'''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 0# $a Élisabeth $b Ire, $c reine d'Angleterre, $d 1533-1603 $c (Esprit)
</div></ol>
2) Generally add subfield $c before subfield $q when also adding words, numerals, etc. indicating relationship. (See [http://original.rdatoolkit.org/rdachp9-fr_rda9-2234.html/view RDA 9.2.2.9.5] for treatment of Portuguese names)
<ol>''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a McCauley, Robert H., $c Jr. $q (Robert Henry), $d 1913-1979
</div>
BUT
<br><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;">
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.
''Examples:''
'''Subfield $2 – Source of term'''
In subfield $2 give “rdacontent/fre.”
'''Subfield $a – Content type term'''
Use terms from [http://original.rdatoolkit.org/rdachp6-fr_rda6-3421.html/view RDA 6.9.1.3]. The list of terms is also available in the [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].
'''Subfield $b – Content type code'''
If giving subfield $b instead of/or in addition to subfield $a, use the code from the MARC format [http://www.loc.gov/standards/valuelist/rdacontent.html ''Term and Code List for RDA Content Types''].
[2021-02-15]<!--(2021-02-15)-->
<br><br>
<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: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 Freer Gallery of Art
368 ## $d métropolite de Rostov
368 ## $a Musées d'art $2 rvm
<div style="font-family:sans-serif; margin-left:85px;">
<br><br>
</div>
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)
<div style="font-family:sans-serif">Authorized access point recorded in 370:</div>
368 ## $c Rigdonites
<br><br>
110 2# $a Indiana (Cuirassé : BB-50)
368 ## $a Cuirassés $2 rvm
368 ## $c BB-50
</div>
Do not record professions or occupations in subfield $c (Other designation). Profession or occupation may be recorded in field [[PFAN_-_Name_Authority_Manual#374_Occupation|374]].
Record titles of royalty, nobility or religious rank ([http://original.rdatoolkit.org/rdachp9-fr_rda9-4646.html RDA 9.4.1.4–9.4.1.8]) in subfield $d in the form used in the authorized or variant access points.
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; 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 0# $a Alexandre $b VI, $c pape, $d 1431-1503
368 ## $d pape $s 1492 $t 1503
<br><br>
<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>
</div><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:'''
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
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.
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
<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>
'''Subfield $s – Start period and Subfield $t – End period'''
'''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.
Follow the instructions given in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions given in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
Follow the instructions given in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field
'''SARs'''
[2021-03-09]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#368_Other_Attributes_of_Person_or_Corporate_Body|''Supplement'' <big>⮞</big>]]
= 370 Associated place =
'''General'''
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.
'''General'''
''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: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
<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>
'''Subfield $m – Electronic mail address'''
<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;">
'''Subfield $s – Start period and Subfield $t – End period'''
''(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">
Form of name as part of preferred name of a local place:</div>
151 ## $a Rimouski (Québec)
</div><br>
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif">
Geographic name in Canadiana : </div>
151 ## $a Congo (République démocratique)
<div style="font-family:sans-serif; margin-left:85px;">''(Authorized access point for the place includes an other designation)''</div>
<br>
<div style="font-family:sans-serif">
Authorized access point recorded in 370:</div>
370 ## $c Congo (République démocratique) $2 lacnaf
<div style="font-family:sans-serif">
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>
''Example:''
</div><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;">
<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">
</div>
Other place name in Canadiana :</div>
110 2# $a Auschwitz (Camp de concentration)
If using an entity from Canadiana for field of activity, remove any subfield coding not authorized for use in the 372 field.
<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>''
<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;">
<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>
<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>
'''Repeatability:'''
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.
''Example:''
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.
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
'''<span style="color:red>Subfield $c – Associated country</span>'''
<span style="color:red>Generally, do not use subfield $c to record places that are not sovereign entities. Such places may be recorded in subfield $f or other subfields as appropriate.</span>
''<span style="color:red>Example:</span>''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#372_Field_of_Activity|''Supplement'' <big>⮞</big>]]
<span style="color:red><div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
370 ## $c France $f Martinique $2 lacnaf
<div style="font-family:sans-serif; margin-left:85px;">
''(Martinique is an overseas department of France)''</div></div><br>
However, if a sovereign entity has (or previously had) one or more constituent countries, any of the constituent countries associated with the 1XX may optionally be recorded in subfield $c in addition to, or instead of, the larger sovereign entity.
''Examples:''
''Examples:''
<div style="font-family:courier new; margin-bottom:20px; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:sans-serif;">Corporate name in Canadiana:</div>
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.
<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;">
''Example :''
<div style="font-family:sans-serif;">Corporate name in Canadiana:</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;">
370 ## $c Première nation de Natashkuan $2 lacnaf
</div></span>
'''Repeatability:'''
'''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.
</div>
-->
[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 =
'''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'''
'''Subfield $s – Start period and Subfield $t – End period'''
[2021-03-10]<!--(2021-03-02)-->
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#374_Occupation|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#371_Address|''Supplement'' <big>⮞</big>]]
= 375 Gender =
= 372 Field of activity =
'''General'''
'''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:''
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
372 ## $a Japon--Histoire $2 rvm
</div>
If using an entity from Canadiana for field of activity, remove any subfield coding not authorized for use in the 372 field.
''Example:''
Authorized access point in Canadiana:
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
130 #0 $a Bible. $p Nouveau Testament
</div>
Field of activity in 372:
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
372## $a Bible. Nouveau Testament $2 lacnaf
</div>
</div>
'''Subfield $2 – Source of term'''
'''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 $s – Start period and Subfield $t – End period'''
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
372 ## $a Poésie $2 rvm
372 ## $a Brasserie artisanale
<div style="font-family:sans-serif; margin-left:85px;">
(''372 fields with a term from RVM and a non-controlled vocabulary term'')</div>
</div>
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
'''LAC :'''
'''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#372_Field_of_Activity|''Supplement'' <big>⮞</big>]]
[2021-03-12]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#375_.E2.80.93_Gender_.28R.29|''Participant's Manual'' <big>⮞</big>]]
= 373 Associated group =
'''General'''
'''General'''
Prefer controlled vocabulary, such as RVMGD or RVM, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled
Prefer 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.
'''Repeatability:'''
''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)
<div style="font-family:sans-serif;">Authorized access point in 373:</div>
373 ## $a Canadiens de Montréal (Équipe de hockey) $2 lacnaf
</div>
'''Subfield $b – Name of prominent member'''
<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>
'''Subfield $s – Start''' period and Subfield $t – End period
'''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.
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
''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>
= 377 Associated language =
<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 $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]
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
<div style="font-family:sans-serif; margin-left:0px;text-indent:0px">
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#373_Associated_Group|''Supplement'' <big>⮞</big>]]
''(ISO 639-3 code for Achi (acr); assigned a collective code (myn) for Mayan languages in the MARC Code List for Languages)''</div>
</div>
= 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'''
'''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.
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)-->
[2021-03-10]<!--(2021-03-02)-->
<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>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#374_Occupation|''Supplement'' <big>⮞</big>]]
= 380 Form of work =
= 375 Gender =
'''PFAN'''
'''General'''
'''General'''
When recording a term indicating gender, prefer the terns ''masculin'' and ''féminin''. For these terms, do not capitalize or indicate the source of the term in the $2 subfield. If neither of these terms is appropriate or sufficiently precise, record an appropriate term or phrase preferably using a controlled vocabulary, such as the RVMGD or the [https://www.btb.termiumplus.gc.ca/publications/diversite-diversity-eng.html ''Gender and sexual diversity glossary''], recording the source in subfield 2. For consistency, capitalize the first term in each subfield $a for terms other than ''masculin'' and ''féminin''. When terms are not taken from a controlled vocabulary, use the singular form. Use terms rather than ISO 5218 codes.
'''Repeatability:'''
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, repeat the field. Overall best practice: repeat the field when needed for clarity.
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the corresponding subfield. If the vocabulary source differs, or if another associated element differs (such as a range of dates), repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples:''
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; 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
100 1# $a Lenoir, Axelle, $d 1979-
375 ## $a Transgenres $2 rvmgd
375 ## $a féminin $s 2018
375 ## $a masculin $s 1979 $t 2018
</div>
'''Subfield $2 – Source of term'''
Codes from the [http://www.loc.gov/standards/sourcelist/gender.html Gender Source Codes] list may be recorded in subfield $2 for the 375 field.
'''Subfield $s – Start period and Subfield $t – End period'''
Follow the instructions in the Manual for subfield $s and subfield $t provided in the [[PFAN_-_Name_Authority_Manual#373_Associated_group|373]] field.
______
'''LAC :'''
Do not record gender. ''Exception:'' When information has changed over the course of a person's life. Follow PFAN instructions.
Do not delete gender information recorded by other organizations.
[2021-03-12]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#375_Gender|''Supplement'' <big>⮞</big>]] | [[PFAN_-_Participant%27s_Manual#375_.E2.80.93_Gender_.28R.29|''Participant's Manual'' <big>⮞</big>]]
= 376 Family information =
'''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.
''Examples:''
'''Subfield $u - Uniform Resource Identifier and Subfield $v - Source of information'''
Follow the instructions in the Manual for subfield $u and subfield $v provided in the [[PFAN_-_Name_Authority_Manual#046_Special_coded_dates|046]] field.
[2021-03-10]<!--(2021-03-02)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#376_Family_Information|''Supplement'' <big>⮞</big>]]
= 377 Associated language =
'''General'''
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
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>
'''Repeatability:'''
[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 =
'''Subfield $u – Uniform Resource Identifier and Subfield $v – Source of information'''
'''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.
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.
'''General'''
[2021-02-22]<!--(2021-03-02)-->
<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'''
'''General'''
Prefer a controlled vocabulary, such as RVM or RVMGF, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a. When terms do not come from a controlled vocabulary, use a singular form.
'''Repeatability:'''
In choosing between repeating a field vs. repeating a subfield: If the only addition to an existing field is an additional term from the same vocabulary, repeat the affected subfield. If the vocabulary source differs, repeat the field. Overall best practice: repeat the field when needed for clarity.
'''General'''
''Examples:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
100 1# $a Picasso, Pablo, $d 1881-1973. $t Gertrude Stein
380 ## $a Portraits $a Peintures $2 rvmgf
100 1# $a Shakespeare, William, $d 1564-1616. $t Hamlet
380 ## $a Tragédies $2 rvmgf
380 ## $a Tragédie $2 rvm
</div>
<!--'''SARs'''
'''General'''
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
381 ## $a Fr. 712
<li>Record variants found in the manifestation being cataloged:
<div style="font-family:sans-serif; margin-left:85px;">
''(Franklin number recorded as other distinguishing characteristic of work)''</div> <br>
<dd>○ Instead of or in addition to adding variants, consider providing access by adding 37X fields.
130 #0 $a Bible. $p Psaumes. $l Anglais. $s New American. $f 1991
381 ## $a New American
</div>
<div style="font-family:sans-serif; margin-left:85px;">
</div>
''(Version recorded as other distinguishing characteristic of expression)''</div> <br>
</dl>
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:''
''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: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;">
''(Corporate body recorded as associated group and other distinguishing characteristic of work)''</div>
</div>
''Examples:''
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.
<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;">
''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;">
<div style="font-family:sans-serif; margin-left:85px;">
''(Name changed upon election as pope)''
''(Places used as other distinguishing characteristic of a legal work; recorded in 370 and 381 fields)''</div>
</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).
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.
'''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.
'''SARs'''
'''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.
'''General'''
'''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 =
'''Subfield $w – Control subfield'''
'''General'''
Best practice: Encode when available. Create separate 383 fields for different numbering schemes associated with a single work.
<div style="margin-left:50px;"">
[2021-02-22]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#383_Numeric_Designation_of_Musical_Work|''Supplement'' <big>⮞</big>]]
= 384 Key =
'''General'''
Best practice: Encode when available for works. In case of doubt, do not encode. Do not encode for expressions.
'''NARs'''
[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 =
'''SARs'''
'''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].
= 500 See Also From Tracing - Personal Name =
''Examples :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
385 ## $a Préadolescents $2 rvmgd
385 ## $a Familles de militaires $2 rvmt
385 ## $a Élève-maître $2 unescot
385 ## $a Acheteurs potentiels de logement
<div style="font-family: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:60px;">
''(Uncontrolled term)''</div>
</div>
'''Repeatability:'''
In choosing between repeating a field and repeating subfield $a: If the vocabulary source differs or if some terms come from a controlled vocabulary and others are uncontrolled, repeat the field. Otherwise, if the only addition to an existing field is an additional term from the same vocabulary, either repeat subfield $a or repeat the field. Overall best practice: repeat the field when needed for clarity.
''Examples :''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
385 ## $a Anglophones $2 rvmgd
385 ## $a Commerçants $2 rvm
<div style="font-family:sans-serif; margin-left:60px;">
''(Terms from different controlled vocabularies)''</div><br>
385 ## $a Créolophones à base française
= 510 See Also From Tracing - Corporate Name =
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>
'''General'''
'''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 =
'''General'''
'''General'''
PFAN catalogers may use this field but are encouraged to wait until best practice guidelines are developed by the PFAN.
[2021-02-15]<!--(2021-02-10)-->
[2021-02-21]<!--(2021-02-19)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#386_Creator.2FContributor_Characteristics|''Supplement'' <big>⮞</big>]]
= 551 See Also From Tracing - Geographic Name =
= 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.
= 64X Series Numbering Peculiarities =
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
= 642 Series Numbering Example =
388 1# $a <span style="color:red>Rébellion des Patriotes (Canada : 1837-1838) $2 rvmfast</span>
</div>
If using an RVM subject heading string, replace the subfield coding for the subdivision(s) with two hyphens and close up the spaces between the main heading and subdivision(s).
''Example:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Crises économiques--1929 $2 rvm
</div>
For compilations, the field may be used to record the time period of creation or origin of the works/expressions contained within the compilation, considered collectively (using first indicator value “1”). It may also be used to record the time period of creation or origin of the compilation itself (using first indicator value “2”).
''Examples:''
<div style="font-family:courier new; margin-left:0px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
388 1# $a Renaissance $2 rvm
388 2# $a Dix-neuvième siècle $2 rvm
<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: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.
''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)-->
[[#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 =
==== More than two identities - "basic" authorized access point and references ====
'''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:
<ul>
<!--<div style="padding-left:50px;">-->
<li>Record variants found in the manifestation being cataloged:
<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;">
<dl>
<div style="font-family:sans-serif">"Basic" NAR:</div>
<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.
100 1# $a Harris, John, $d 1916-1991
<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;">
100 1# $a Bucknum, David W.
378 ## $q David Walter
</div>
</div>
</div>
</dd>
</dl>
</li>
<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;">
<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.
<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).
<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;">
<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 style="font-family:sans-serif">NAR for second 500 on "basic" NAR:</div>
<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>
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.
''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-
''Examples :''
<div style="font-family:sans-serif; margin-left:85px;">
''(Name changed upon election as pope)''
<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><br>
<div style="font-family:sans-serif;">NAR for joint pseudonym:</div>
100 1# $a Rancic, Giuliana<br>
400 1# $w nne $a DePandi, Giuliana<br>
100 1# $a Phillips, Mark
<div style="font-family:sans-serif; margin-left:85px;">
''(Nom changé après le mariage)''</div>
</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>
</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;">
<!--'''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.
</div>
-->
[2021-11-03] <!--(2021-11-01)-->
<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>]]
==== Pseudonyms used by multiple persons ====
= 5XX - See Also From Tracings - General Information =
'''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;"">
</div>
$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)
663 ## $a Pour les œuvres de cette personne écrites sous un autre nom, chercher aussi sous : $b Robeson, Kenneth
</div>
</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.
<!--'''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-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.
==== General ====
''Examples :''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
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].
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.
[2021-03-10]<!--(2021-03-04)-->
<br>
<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>]]
<div style="font-family:sans-serif; margin-left:85px;">
''<span style="color:red">(If the undifferentiated name record does not have a Canadiana number other than 0000X0000E, use OCLC record)</span>''</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>]]
==== NARs for persons with identities not established ====
= 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)-->
<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>]]
= 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 =
''Example:''
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#641_Series_Numbering_Peculiarities|''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;">
= 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 =
<ol>
<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>]]
''Examples:''
= 645 Series Tracing Practice =
<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#645_Series_Tracing_Practice|''Supplement'' <big>⮞</big>]]
= 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 ====
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>
</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 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>
</div>
<li type="a">'''NARs for fictitious characters'''<br>
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>
<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>
<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
''Example:''
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 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>
<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>
<!--</div>-->
==== Duplicates ====
==== 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>
= 670 Sources found =
<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>
<ol>'''Functions of the 670 field:'''
<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>
</ol>
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.
''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.
''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>
<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>
<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-
[…]
# The date of publication.
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>-->
<ol>''Examples:''
[2021-03-10]<!--(2021-03-04)-->
<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;">
<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>
= 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; 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;">
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>
<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].
<ol>
<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;">
<div style="font-family:sans-serif; margin-left:85px;">
(''Used for official language changes'')</div>
</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:''
<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;">
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>
</div>
</ol>
==== NARs and subject usage ====
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).
Apply these instructions when creating new NARs and revising existing NARs.
<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;">
<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>
670 ## $a The greenhouse approach, 2019 : $b page de titre du CIP (Chitra Anand) formulaire du CIP de BAC (Canadienne)</div>
</ol>
<ol>
<li type="a">'''Heads of state, etc.'''<br>
* '''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>
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; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a Site Web de l'organisme, consulté le 16 août 2019 : $b page d'accueil (Carrefour jeunesse-emploi Drummond; CJE Drummond) À propos (ouvre ses portes en novembre 1998; organisme sans but lucratif) Nous joindre (749, boul. Mercure Drummondville (Québec) J2B 3K6; cjed@cgocable.ca)
<div style="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>
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].
</ol>
</div>
* '''Multiple locations within a resource.'''
<ol>
Assign value “n” in 008/11 and value “b” in 008/15.
'''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.
''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;">
<span style="color:red>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)</span></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;">
<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)-->
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>
</ol>
</ol>
''Example:''
''Example:''
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
<div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; text-indent:-85px; line-height:1.4; border:1px solid #eaecf0; background-color:#f8f9fa;">
670 ## $a British Oceanographic Data Centre, consulté le 23 novembre 2009 : $b About us (British Oceanographic Data Centre, National Environment Research Council; 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/]
670 ## $a British Oceanographic Data Centre, consulté le 23 novembre 2009 : $b About us (British Oceanographic Data Centre, National Environment Research Council; le BODC est un organisme national chargé de la gestion et de la diffusion des données relatives au milieu marin) $u http ://www.bodc.ac.uk/
</div>
</div>
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.
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>
'''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.
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 ===
=== Special types of citations ===
</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.
<!--''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 />
<hr />
</div>
</div>
'''Citations for republication SARs.'''
<!--'''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.)
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.)
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)
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>
</div>
-->
'''Citations for undifferentiated NARs.'''
'''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]].
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]].
[2021-04-20]<!--(2021-04-20)-->
[2023-01-18]<!--(2023-01-18)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#670_Source_Data_Found|''Supplement'' <big>⮞</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#670_Source_Data_Found|''Supplement'' <big>⮞</big>]]
= 675 Sources not found =
= 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.
<!--''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.
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.
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.
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-03-10]<!--(2021-03-03)-->
[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>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]] | [[PFAN_-_Name_Authority_Manual_-_MARC_21_Supplement#675_Source_Data_Not_Found|''Supplement'' <big>⮞</big>]]
<ol>
<ol>
'''A) General Information'''<br>
'''A) General Information'''<br>
This mentoring project, going from mid-February to early June 2021, allows four university libraries to create name authority records that are revised by another university. The authority records created or modified by Polytechnique and ÉTS are revised by library technicians from Université de Montréal, and those created or modified by Université de Sherbrooke and UQTR are revised by library technicians from Université Laval. <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>
When added to Canadiana, these new records contained the following elements: <br>
* In the Leader/17, the value was "o" (Incomplete authority record).
* In the Leader/17, the value was "o" (Incomplete authority record).
* The following 667 note was added: NOTICE EN COURS DE RÉVISION (PROJET DE MENTORAT [abbreviation, e.g. UdeS, PolyMtl, ÉTS or UQTR]). <br>
* 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>
<br>
'''B) Instructions for revision of the record''' <br>
'''B) Instructions for revision of the record''' <br>
These records should not be modified.<br>
These records should not be modified.<br>
</ol>
</ol>
[2021-08-31] <!--(2021-04-19)-->
[2022-07-15] <!--(2022-07-15)-->
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
<br>[[#toc|''Return to Table of Contents'' <big>⮝</big>]]
