NACO Updates Since March 2019 2020 CEAL Cataloging

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

Documentation covered: • NACO Advisory Group “At-a-Glance” Sheets • NACO Documentation & Update at PCC website • Descriptive Cataloging Manual Section Z 1 and LC Guidelines Supplement (August 2019, February 2020, April 2020) • OCLC-MARC Format Update 2019 (TB 269 & World. Cat Validation Release Notes, May 2019, Nov. 2019, March 2020) • Other Updates: PCC Transitioning to Identity Management • Not Covered: RDA & LC-PCC PS—See the RDA 3 R Update from Chew 2

NACO Advisory Group “At-a-Glance” Sheets • NACO Advisory Group, announced August 1, 2019 on PCCLIST • https: //www. loc. gov/aba/pcc/naco/NACOAdvisory. Group. html • monitors PCC listserv discussion of NACO-related topics, and provides input when a NACO-related topic appears to be unresolved, unanswered, or ambiguously answered, in routine PCC listserv discussion • may refer to existing NACO documentation, refer to a NACO best practice, or indicate that the topic may need additional investigation and policy discussion. • NACO Advisory Group "At-a-Glance" Sheets • Fuller Form of Name (February 2020): example • 100 1# ǂa Arundal, Philip H. ǂq (Philip Howard) • 378 ## ǂq Philip Howard • Instruction is meant to augment existing documentation in RDA 9. 5. 1. 1 and Module 2 of the NACO training 3

NACO Documentation & Updates at PCC website • https: //www. loc. gov/aba/pcc/naco/doc-updates. html 4

DCM Z 1 : 008/33 on Provisional Records Added Instruction to DCM Z 1 (February 2020) Special administrative regions of Hong Kong and Macau 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 RDA 11. 2. 2. 5. 2 and its related policy statement for instructions on choosing the language of the preferred name. Please note that this policy for provisional status does not apply to non-government bodies. Background: https: //www. loc. gov/catdir/cpso/hongkong. html 5

DCM Z 1 : 008/33 on Provisional Records (2) --Updating Existing Records: Hong Kong c references 410 1 Hong Kong (China). $b Beijing Office 670 Its website, [date] $b (Beijing Office, …. 1. Change 008/33 (Auth status) from “a” to “c” 2. When found English form [i. e. from its website], add 670 3. Add 410 1 Hong Kong (China). ǂb Beijing Office 4. Add other 410 as needed 5. Add 046 & 3 XX when applicable 6. Change in 667“reference” to “references” 6

DCM Z 1 : 008/33 on Provisional Records (3) --Updating Existing Records: Macau c z ǂe rda ǂw r ǂi Predecessor: 1. Change 008/33 (Auth status) from “a” to “c” 2. Change 008/10 (Rules) from “c” to “z” 3. Add 040 $e rda if the heading is RDA compatible 4. Add 046 & 3 XX when applicable 5. Add RD in 510 7

DCM Z 1 and LC Guidelines Supplement: 024 • Added Instruction to both DCM Z 1 and LC Guidelines Supplement (August 2019) “Until further notice, do not use this field. As of September 2018, there is a moratorium on adding this field in authority records (see http: //www. loc. gov/aba/pcc/naco/documents/024 -moratorium. pdf). An announcement will be made when catalogers may use this field again. ” • TBD: Upcoming new instruction for PCC URI in MARC Pilot participants • Use of the 024 field in NACO authority records to end the temporary moratorium on adding 024 fields 8

DCM Z 1: 368 on Preferring Singular Form of Uncontrolled Terms Added instruction to DCM Z 1 (April 2020)— 368 Other Attributes of Person or Corporate Body • When terms in subfields $a and $b do not come from a controlled vocabulary, use a singular form. 110 2# ǂa Church of Christ (Rigdonites) 368 ## ǂc Rigdonites The general instruction: 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. 110 2# ǂa Freer Gallery of Art 368 ## ǂa Art museums (institutions) ǂ2 aat 9

DCM Z 1: 382 on Following MLA’s Best Practices • Added Instruction to both DCM Z 1 and LC Guidelines Supplement (April 2020)— 382 Medium of Performance Record the medium of performance using terms from the Library of Congress Medium of Performance Thesaurus for Music (LCMPT), accessible via Classification Web or LC Linked Data Service, when possible. Record the medium of performance by applying the instructions at RDA 6. 15. 1. 3– 6. 15. 1. 6, the associated LC-PCC PSs, and the Music Library Association’s “Best Practices for Using LCMPT” available at: http: //cmc. blog. musiclibraryassoc. org/documents/best-practices-for-usinglcmpt/. Note that the examples in this last document are formatted as bibliographic record fields, with a second indicator value of “ 1”; in authority records, the second indicator should be left blank. • Removed instructions to both DCM Z 1 and LC Guidelines Supplement on some subfields 10

DCM Z 1: 510, 511 on Adding RD New Instruction to DCM Z 1 510, 511 (August 2019) “Follow instructions provided in the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records (http: //www. loc. gov/aba/pcc/rda/PCC%20 RDA%20 guidelines/PCC%20 SCS%20 SCT%20 R elationship%20 Designators%20 in%20 NACO%20 Authority%20 Records-2018 -11. docx). ” • PCC Guidelines for the Application of Relationship Designators in NACO Authority Records: Guideline 11: Corporate Bodies (on Sequential Relationships) • Related corporate body is a core element for LC and PCC for sequential relationships with immediately preceding and immediately succeeding corporate bodies. See LCPCC PS 32. 1. • The former practice of using subfield $w values “a” (earlier name) or “b” (later name) to show chronological relationships between corporate bodies has been discontinued. Use relationship designators in $i and $w with value “r. ” Record the reciprocal relationship in the corresponding authority record following Guideline 9. 11

DCM Z 1: 510, 511 on Adding RD (2) For earlier/later names, please start to use $w r $i [RD] before $a 1102 Hua bei dian li lian he gong si 4102 华北电力联合公司 5102 ǂw r ǂi Successor: ǂa Hua bei dian li ji tuan gong si 1102 Hua bei dian li ji tuan gong si 4102 华北电力集团公司 5102 ǂw r ǂi Predecessor: ǂa Hua bei dian li lian he gong si 5102 ǂw r ǂi Successor: ǂa Hua bei dian wang you xian gong si 1102 Hua bei dian wang you xian gong si 4102 华北电网有限公司 5102 ǂw r ǂi Predecessor: ǂa Hua bei dian li ji tuan gong si Update the records with $w values “a” (earlier name) or “b” (later name) when encountered. 12

DCM Z 1 and LC Guidelines Supplement: $h in 1 XX & 4 XX; $4 in 4 XX • Removed instruction from both DCM Z 1 and LC Guidelines Supplement on $h (April 2020) • DCM Z 1 1 XX, 4 XX: Removed note on pending status regarding use of subfield $h “Medium”. • LC Guidelines Supplement 100, 111, 130, 400, 411, 430, 500, 511, 530: Removed requirement to consult before using subfield $h (NACO and LC Names/Series sections). 100 1_ Bach, Johann Sebastian, ǂd 1685 -1750. ǂt Suites, ǂm lute, ǂn BWV 996, ǂr E minor. ǂh Tactile notated music 100 0_ Homer. ǂt Iliad. ǂl English. ǂh Spoken word ǂs (Molina) • Added instruction to LC Guidelines Supplement on $4 (April 2020) • Do not use $4 (relationship) in 400, 481, 482, 485, 510, 13

DCM Z 1: 667 on Recording Series Subtitle Added Instruction to DCM Z 1 667 page 5 (February 2020) • If the subtitle could be interpreted as the title proper of the series or as a subseries, note the subtitle in a 667 field, record it in a 670 field, and give it as a 4 XX variant access point. 667 ## $a Subtitle: [title of subtitle] 14

OCLC-MARC Authority Update 2019: Part One • OCLC Technical Bulletin 269 oc. lc/tb 269 • Based on MARC 21 Format for Authority Data Update 27 (November 2018) • 055 Library and Archives Canada Call Number (R): • Revised the field definition and scope • Added new subfield: $2 Number source • Subfield ‡ 6 (Linkage (NR))-no changes have been implemented yet • Redefined the subfield: Scope of ‡ 6 broadened to allow for the recording of script identification codes taken from ISO 15924. • OCLC World. Cat Validation Release Notes (May 2019) Note: Name Authority Cooperative (NACO) participants should not use the authority format changes in Authority Record Changes at this time. The Library of Congress and OCLC will announce the implementation of these elements for use in name and subject authority records at a future date. 15

OCLC-MARC Authority Update 2019: Part Two • Based on MARC 21 Format for Authority Data Update 28 (May 2019) • 024 Other Standard Identifier (R) • • Revised the field definition and scope Newly defined $0 Authority Record Control Number or Standard Number Newly defined $1 Real World Object URI Renamed $2 from Source of number or code to Source • OCLC World. Cat Validation Release Notes (November 2019) Note: [TBD based URI Pilot] Name Authority Cooperative (NACO) participants should not use the authority format changes in Authority Record Changes at this time. The Library of Congress and OCLC will announce the implementation of these elements for use in name and subject authority records at a future date. 16

OCLC World. Cat Validation Release Notes (March 2020) Release newly validated MARC authority elements: • $c "Location of Meeting, " has changed to repeatable in X 10 & X 11 • $d “Date of Meeting, ” is now “Date of Meeting or Treaty Signing, ” and repeatable in X 11 • $h “Medium, ” has now been implemented in X 00, X 11, X 30 • $s “Version, ” has changed to repeatable in X 00, X 11, X 30 • In 043, new repeatable subfield $c “ISO code” • In 382, new repeatable subfield $e, “Number of Ensembles of the Same Type, ” new nonrepeatable subfield $r, “Total Number of Individuals Performing Alongside Ensembles, " and new nonrepeatable subfield $t, “Total Number of Ensembles” have been defined for use by NACO-Music Project participants only. Additionally, subfield $r, previously “Total Number of Performers, ” has been redefined to its current name “Total Number of Individuals Performing Alongside Ensembles” 17

From last year: OCLC NACO functionality in Record Manager You. Tube training video: https: //www. youtube. com/watch? v=2 PLr. U 1 nl. Ka. I • OCLC announced in May 2018 that NACO catalogers now have a choice to create/update NACO records on World. Share Record Manager • New features in Record Manager include: • Support of roles and permissions for NACO participants and LAC users • Ability to create, add, derive, edit, and replace both LC/NACO Name Authority records and Canadiana Name Authority records • Duplicate Detection upon adding or replacing authority records • Support for linking authority records • Online Saved – In Progress File and ability to save and lock authority records • Support of the “submit for review” workflow for LC/NACO Name Authority file records • The ability to make changes to an authority record after contribution up until the daily distribution (rather than having it locked until it comes back from LC) • No macro can pull non-Latin data yet, may save in Connexion and retrieve in Record Manager 18

OCLC NACO functionality in Record Manager OCLC Update at PCC Op. Co Meeting, May 21, 2020: • Macro-like functionality to generate authority records: • Similar to the generate authority record macro in Connexion • Includes generate non-Latin data, such as 400 non-Latin form for personal name pull from the parallel field. • May 30: First release for personal names • TBD: Later release for non-personal names Yay ! • Watch the release of meeting recordings to hear more about the details. • Please see OCLC Record Manager release notes 19

PCC Transitioning to Identity Management URIs in MARC Pilot https: //www. loc. gov/aba/pcc/pilots/URIs-in-MARC-Pilot. html • URI (Uniform Resource Identifier) • A string of characters that unambiguously identifies a particular resource. A URI can be specified in the form of a URL or a URN –Wikipedia • URIs in MARC Pilot https: //wiki. lyrasis. org/display/pccidmgt/URIs+in+MARC+Pilot • Started Dec. 2019, A multi-insititution pilot to test and develop best practices on adding subfield $0 and subfield $1 data in bibliographic records and in authority records. • Use of the 024 field in NACO authority records to end the temporary moratorium on adding 024 fields [TBD] 0247 Q 10902263 ǂ2 wikidata ǂ1 https: //www. wikidata. org/entity/Q 10902263 1102 Beijing Shi di san shi yi zhong xue 4102 北京市第三十一中学 667 URIs added to this record for the PCC URI MARC Pilot. Please do not remove or edit the URIs. 20

PCC Transitioning to Identity Management PCC ISNI Pilot Project • ISNI (International Standard Name Identifier): http: //www. isni. org/ • A 16 -digit number which uniquely identifies people who contributors to creative works and those active in their distribution. • ISNI for CEAL: 0000 0001 2104 844 X • A ISNI database started in 2011, can be searched: http: //www. isni. org/search • PCC is one of Data Contributors • PCC ISNI Pilot Project: https: //wiki. lyrasis. org/display/PCCISNI/PCC+ISNI+Pilot+Home • 2017 -2018: A Multi-Institution Pilot, began in Fall 2017, partnership with the ISNI International Agency • April 2019 -: LD 4 P ISNI Initiative, part of Linked Data for Production: Pathway to Implementation (LD 4 P 2) 21

PCC Transitioning to Identity Management LD 4 P 2 Wikidata Affinity Group • Wikidata: https: //www. wikidata. org/wiki/Wikidata: Main_Page • A central knowledge base (storage) for the structured & linked data hosted by the Wikimedia Foundation • A powerful tool for low-barrier identity management in library community • Offer SPARQL query service • Every structured data has ID number starts with Q. • CEAL: Q 89387012; CTP: Q 89386078 • Everyone can create an account to contribute • Wikidata Affinity Group https: //wiki. lyrasis. org/display/LD 4 P 2/LD 4 -Wikidata+Affinity+Group • Part of the Linked Data for Production: Pathway to Implementation (LD 4 P 2) • Provides training/demos (PPTs and recorded meetings/presentations) to help understand how libraries can contribute to and leverage Wikidata as a platform for publishing, linking, and enriching library linked data. 22

Thank you! 23