NACO Updates Since May 2020 2021 CEAL Cataloging

NACO Updates Since May 2020 2021 CEAL Cataloging Workshop, March 16, 2021 Shi Deng, UC San Diego Library, with Jessalyn Zoom, Library of Congress Hideyuki Morimoto, Columbia University

Documentation covered: • NACO Advisory Group “At‐a‐Glance” Sheets (since May 2020) • NACO Documentation & Update at PCC website • Descriptive Cataloging Manual Section Z 1 and LC Guidelines Supplement (August 2020, October 2020, February 2021) • OCLC‐MARC Authority Update (World. Cat Validation Release Notes (August 2020, October 2020, February 2021) • Other Updates: PCC Wikidata Pilot • Not Covered: RDA & LC‐PCC PS—See the RDA Update from Glenn 2

NACO Advisory Group Updates since May 2020 https: //www. loc. gov/aba/pcc/naco/NACOAdvisory. Group. html • PCC CCT (Conventional Collective Title) Feasibility Study (August 2020) • Constructing AAPs for cancelled and online conferences (September 2020) 3

Constructing AAPs for cancelled and online conferences (Sept 2020) https: //www. loc. gov/aba/pcc/naco/documents/Constructing. AAPs. Cancelled. Online. Conferences. pdf • Guidance below focuses on applying RDA 11. 3. 2. 2 Recording location of Conference, Etc. • Cancelled conferences: Do not record a location • Numbered conferences: Clinical Nutrition and Research Symposium $n (20 th : $d 2020) • Unnumbered conferences: SEAALL Annual Meeting $d (2020) • Online conferences: “Record Online as a location for conference, etc. , that was held online. ” • International Conference on Technologies and Applications for Fuel Cell, Plug‐In Hybrid, and Electric Vehicles $d (2018 : $c Online) • Verfassungsblog (Symposium) $d (2015 : $c Online) • Hybrid conference: “do not record ‘Online’ as a location but instead limit the location to the physical location(s)” 4

PCC CCT Feasibility Study (August 2020) https: //www. loc. gov/aba/pcc/naco/NACOAdvisory. Group. html • Starting August 10, 2020, PCC catalogers describing incomplete collections of literary forms by one agent will not apply the Alternative in RDA 6. 2. 2. 10. 3, Other Compilations of Two or More Works (by One Agent), to use a conventional collective title for the form, followed by Selections, as the preferred title for the collection. • Instead, PCC catalogers will apply RDA 6. 2. 2. 4 when describing incomplete collections of literary forms by one agent: • For works created after 1500, choose as a preferred title for work the title or form of title in the original language by which the work is commonly identified either through use in manifestations embodying the work or in reference sources. 5

PCC CCT Feasibility Study (August 2020) https: //www. loc. gov/aba/pcc/naco/NACOAdvisory. Group. html • See Feasibility Study FAQ for details and examples • See Adam Schiff’s presentation for details and examples (below from page 11) 6

PCC CCT Feasibility Study (August 2020) https: //www. loc. gov/aba/pcc/naco/NACOAdvisory. Group. html • A five‐month feasibility study from August to December 2020 • At the end of the Feasibility Study, the SCS will make an assessment on: • the impact of the policy change on legacy data, including existing authorized conventional collective titles for incomplete collections of literary forms by one agent • the treatment of translations • bibliographic file maintenance (BFM) • any unexpected or unforeseen cataloging situations that arise during the Feasibility Study • the number of resources cataloged in the Feasibility Study • literary forms that are not listed in RDA 6. 2. 2. 10. 2 • other issues that arise in the Feasibility Study • A form was used to record each cataloger’s work during the Feasibility Study. • A Feasibility Study FAQ was provided to anyone who participated 7

NACO Documentation & Updates at PCC website https: //www. loc. gov/aba/pcc/naco/doc-updates. html • Or on NACO landing page: Most recent documents on top https: //www. loc. gov/aba/pcc/na co/ • NACO 024 Best Practices Guidelines (Nov. 2020) • Working with “undifferentiated” CCT work and expression authority records: FAQ (Oct. 2020) • NACO Participant Manual, 4 th edition (July 2020) 8

“Undifferentiated” CCT work and expression authority records https: //www. loc. gov/aba/pcc/rda/PCC%20 Post%20 RDA%20 Test%20 Guidelines. html • Many CCT NARs representing a group of different compilations by the same author under the same AAP • Whether these NARs re‐coded RDA or not, NACO catalogers are encouraged to create differentiated work or expression authorized access points for one or more of the compilations represented by the conventional collective title 9

“Undifferentiated” CCT work and expression authority records (cont’d) https: //www. loc. gov/aba/pcc/rda/PCC%20 Post%20 RDA%20 Test%20 Guidelines. html • FAQ provided guidance on optionally creating differentiated work or expression authorized access points for one or more of the compilations represented by the authority record, with many examples on • AAP (+when & how to add a qualifier) • Attributes • Relationships • Webinar 6 a: CJK Materials: Identifying Works and Expressions (Recording) and (PPT) (2017) also have good CJK examples. 10

“Undifferentiated” CCT work and expression authority records (cont’d) https: //www. loc. gov/aba/pcc/rda/PCC%20 Post%20 RDA%20 Test%20 Guidelines. html • How do I create an authorized access point for an expression of "selections"? • Beginning with the form you have worked out for the work‐level authorized access point, add expression‐level elements (content type, date of expression, language of expression, other distinguishing characteristic of expression). 130 _0 Aesop's fables. $k Selections (Dodsley). $l German 130 _0 Aesop's fables. $k Selections (Thuswaldner). $l German not 130 _0 Aesop's fables. $k Selections. $l German $s (Dodsley) 130 _0 Aesop's fables. $k Selections. $l German $s (Thuswaldner) Remember: these are two different collections, so a qualifier is needed at the work level 100 1_ Ban uelos, Juan, $d 1932‐ 2017. $t Poems. $k Selections (Nudo de tres vientos). $l French not 100 1_ Ban uelos, Juan, $d 1932‐ 2017. $t Poems. $k Selections. $l French $s (Roy) A translation by Franc oise Roy 100 1_ Beckett, Samuel, $d 1906‐ 1989. $t Correspondence. $k Selections (Craig). $l French not 100 1_ Beckett, Samuel, $d 1906‐ 1989. $t Correspondence. $k Selections. $l French $s (Craig) A translation by George Craig (also editor of the “selection”) 11

“Undifferentiated” CCT work and expression authority records (cont’d) https: //www. loc. gov/aba/pcc/rda/PCC%20 Post%20 RDA%20 Test%20 Guidelines. html • FAQ also provided guidance on adding 667 cataloger’s note information to these “undifferentiated” CCT authority records with usage procedures, and information on reporting records for deletion • If an “undifferentiated” representing more than one compilations, or selections, add: 667 __ Do not use. Represents more than one compilation of works [or expressions]. Do not add to this record. Instead, create new name authority records for distinct compilations. or 667 __ Do not use. Represents more than one compilation of works [or expressions]. Reported for deletion. Or 667 __ Do not use. Represents more than one distinctive selection of works. Reported for deletion. • For new records created (split from an “undifferentiated” CCT record), copy “your” 670 over and add: 667 __ Previously represented on name authority record [LCCN] 12

DCM Z 1: 008/32 for undifferentiated names New instruction added (February 2021) on Records coded as undifferentiated that actually represent only one identity When found, NACO catalogers: • Add a 667 field to the undifferentiated NAR indicating that it has been reported for deletion: 667 ## $a Undifferentiated name record represents a single identity; reported for deletion. • Report the undifferentiated NAR for deletion to naco@loc. gov. • LC will create a new replacement NAR and delete the old NAR. In the new NAR, LC will add a 667 note and add the LCCN of the deleted NAR in field 010 subfield $z. 13

DCM Z 1: 024 Other Standard Identifier Instruction updated (February 2021) DCM Z 1: • Removed instructions about moratorium and added link to NACO best practices. • Follow the guidelines in NACO Best Practices for the 024 Field posted at: https: //www. loc. gov/aba/pcc/naco/documents/NACO‐ 024‐Best‐ Practices. pdf. • 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. LC Guidelines Supplement: • Removed instructions about moratorium for NACO participants 14

NACO 024 Best Practices Guidelines https: //www. loc. gov/aba/pcc/naco/documents/NACO-024 -Best-Practices. pdf • 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. • 024 fields may be added in any order, adding new ones after existing ones, according to the needs of the community or institution • Record URIs from vocabularies that provide additional information rather than repeating information that is already present in other 024 fields whenever possible • Generally, if a $1 contains a URI known to be mapped in a widely used service (e. g. VIAF, Wikidata), additional URI(s) that are also found in those services need not be added • If both an authority URI and a RWO URI are given from one source, include both subfield $0 and subfield $1 in the same 024 field • When there is an “equivalence” conflict, exercise cataloger's judgment in deciding which NACO record(s) should include an 024 field to the vocabulary • Between first indicator 7 or 8, there is preference for the source to be specified in subfield $2 (first indicator = 7) for ease of identification 024 7# Q 550288 $2 wikidata $1 http: //www. wikidata. org/entity/Q 550288 024 8# $1 http: //www. wikidata. org/entity/Q 550288 15

NACO 024 Best Practices Guidelines (cont’d) https: //www. loc. gov/aba/pcc/naco/documents/NACO-024 -Best-Practices. pdf • Recommend that catalogers use the following sources, considering them a “core” group of PCC‐sanctioned vocabularies (see examples listed in the link above) • • • Personal names: Wikidata, ISNI, ORCID, VIAF, ULAN Corporate names: Wikidata, ISNI, VIAF Works/expressions: Wikidata, VIAF, Music. Brainz, BBC Things, DBpedia, FAST Place names: Wikidata, Geo. Names, TGN Family names: VIAF, Wikidata, CERL, ULAN • 667 note: 667 URIs added to this record for the PCC URI MARC Pilot. Please do not remove or edit the URIs. • As of October 15, 2020, over 6, 000 NACO records have this 667 note • They were part of pilot project, if encountered, do not delete • If not presented, please do not add 16

DCM Z 1: 388 Time period of creation DCM Z 1: New instruction added; LC supplement updated accordingly (August 2020) • LC/PCC catalogers may use this field to record the time period of creation or origin of a work or expression. The name of the time period may specify or imply a place for which the time period is relevant. It may also specify the name of an event. • Prefer a controlled vocabulary, such as LCSH or FAST, with the source in $2. Capitalize the first term in each subfield $a. 388 1# $a Han Dynasty (China) $2 fast • For compilation, 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”). 388 1# $a Renaissance $2 lcsh 388 2# $a Nineteenth century $2 lcsh (NAR for a collection of Renaissance poetry compiled in the nineteenth century) 17

DCM Z 1: 388 Time period of creation (cont’d) DCM Z 1: New instruction added; LC supplement updated accordingly (August 2020) • The 388 field may be used in conjunction with, or instead of, the 046 field. 046 ## $k 13 388 1# $a Middle Ages $2 lcsh (NAR for an anonymous fourteenth‐century work) • Repeatability: • If the indicator value differs, repeat the field. • If the vocabulary source differs, repeat the field. • 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. 388 1# $a World War, 1939‐ 1945 $2 lcsh 388 1# $a German Occupation of France (1940‐ 1945) $2 fast (NAR with 388 fields containing terms from different vocabularies) 18

DCM Z 1: 678 Biography or Historical Data New instruction added (August 2020) on repeatability • Do not repeat this field 19

DCM Z 1: Appendix I. Ambiguous Entities New Instruction added (February 2021) on Canadian First Nation entity names • 2. 9 Indian tribes … In April 2015, it was determined that all Canadian First Nation entity names should also be tagged 151 to align with the instructions for U. S. tribal entities. 20

OCLC‐MARC Authority Update Since May 2020 • Part of OCLC World. Cat Validation Release Notes https: //help. oclc. org/Metadata_Services/World. Share_Record_Manager/W orld. Cat_Validation_release_notes_and_known_issues • Changes made according to MARC 21 Authority Data Updates • Changes made to the OCLC‐MARC Authority validation rule set • NACO catalogers should follow PCC instruction on implementation of any changes, for example • August 2020 updates included changes made to 883 field on metadata provenance • No instruction in DCM Z 1; LC guidelines indicated NACO do not use this field • Changes relevant to NACO catalogers: • 5 XX $i changed to not repeatable • 043 changed to repeatable 21

PCC Wikidata Pilot Project https: //www. wikidata. org/wiki/Wikidata: Wiki. Project_PCC_Wikidata_Pilot • Wikidata • Is free and open knowledge base • Can be read and edited by both humans and machines • acts as central storage for the structured data of its Wikimedia sister projects including Wikipedia, Wikivoyage, Wiktionary, Wikisource, and others • Every structured data has ID number starts with Q. • CEAL: Q 89387012; CTP: Q 89386078 • Everyone can create an account to contribute • A powerful tool for low‐barrier identity management in library community • PCC Wikidata Pilot Project • Facilitates a NACO‐Lite approach that would lower the barrier to authority creation and maintenance by PCC members • Started August/September 2020, has over 70 institutions participating 22

Thank you! 23