WorldCat Validation release notes, September 2022

OCLC-MARC Validations of New MARC Codes Announced May-August 2022

You may now use all new MARC Codes announced by the Library of Congress in the following LC Technical Notices:

• Technical Notice (June 1, 2022)
• Technical Notice (June 14, 2022)
• Technical Notice (June 22, 2022)
• Technical Notice (June 28, 2022)
• Technical Notice (July 12, 2022)
• Technical Notice (August 16, 2022)
• Technical Notice (August 24, 2022)

MARC 21 Bibliographic Update No. 34 (announced July 2022)

You may now begin to use the following changes to Bibliographic elements implemented as part of OCLC-MARC Bibliographic Update for September 2022, based on the MARC 21 Bibliographic format changes announced in MARC 21 Bibliographic Update No. 34 (July 2022):

• In existing Bibliographic field 340 (Physical Medium):
  • The field definition and scope have been redescribed to reduce redundancies related to other fields 34X
  • Existing subfield $f has been renamed from Production Rate/Ratio to Reduction Ratio Value and its definition has been narrowed in scope
  • New subfield $q (Reduction Ratio Designator) has been defined
• In existing Bibliographic field 382 (Medium of Performance):
  • Existing First Indicator (Display Constant Controller) has two new values defined:
    • 2 - Medium of performance of musical content of representative expression
    • 3 - Partial medium of performance of musical content of representative expression
  • New subfield $7 (Data Provenance) has been defined
• In existing Bibliographic field 384 (Key):
  • Existing First Indicator (Key Type) has one new value defined:
    • 2 - Key of representative expression
  • New subfield $7 (Data Provenance) has been defined
• New Bibliographic field 387 (Representative Expression Characteristics) has been defined.
• In existing Bibliographic field 507:
  • The field has been renamed from Scale Note for Graphic Material to Scale Note for Visual Materials
  • The field definition and scope have been redescribed to allow for its use with non-cartographic scale content
• New Bibliographic field 788 (Parallel Description in Another Language of Cataloging) has been defined
• In existing Bibliographic field 856 (Electronic Location and Access):
  • Five new subfields have been defined:
    • Subfield $e (Data Provenance)
    • Subfield $l (letter “el”) (Standardized Information Governing Access)
    • Subfield $n (Terms Governing Access)
    • Subfield $r (Standardized Information Governing Use and Reproduction)
    • Subfield $t (Terms Governing Use and Reproduction)
• The following new Data Provenance Subfields have been defined in the respective Bibliographic fields:
  • Subfield $7 (Data Provenance):
    • 041 (Language Code)
    • 082 (Dewey Decimal Classification Number)
    • 083 (Additional Dewey Decimal Classification Number)
    • 084 (Other Classification Number)
    • 100 (Main Entry-Personal Name)
    • 110 (Main Entry-Corporate Name)
    • 111 (Main Entry-Meeting Name)
    • 130 (Main Entry-Uniform Title)
    • 210 (Abbreviated Title)
    • 240 (Uniform Title)
    • 245 (Title Statement)
    • 246 (Varying Form of Title)
    • 247 (Former Title)
    • 250 (Edition Statement)
    • 255 (Cartographic Mathematical Data)
    • 256 (Computer File Characteristics)
    • 264 (Production, Publication, Distribution, Manufacture, and Copyright Notice)
    • 300 (Physical Description)
    • 335 (Extension Plan)
    • 336 (Content Type)
    • 348 (Notated Music Characteristics)
    • 370 (Associated Place)
    • 377 (Associated Language)
    • 380 (Form of Work)
    • 381 (Other Distinguishing Characteristics of Work or Expression)
    • 382 (Medium of Performance)
    • 383 (Numeric Designation of Musical Work)
    • 384 (Key)
    • 385 (Audience Characteristics)
    • 386 (Creator/Contributor Characteristics)
    • 387 (Representative Expression Characteristics)
    • 388 (Time Period of Creation)
    • 490 (Series Statement)
    • 500 (General Note)
    • 501 (With Note)
    • 502 (Dissertation Note)
    • 505 (Formatted Contents Note)
    • 508 (Creation/Production Credits Note)
    • 515 (Numbering Peculiarities Note)
    • 510 (Citation/References Note)
    • 518 (Date/Time and Place of an Event Note)
    • 520 (Summary, etc.)
    • 546 (Language Note)
    • 550 (Issuing Body Note)
    • 555 (Cumulative Index/Finding Aids Note)
    • 583 (Action Note)
    • 600 (Subject Added Entry-Personal Name)
    • 610 (Subject Added Entry-Corporate Name)
    • 611 (Subject Added Entry-Meeting Name)
    • 630 (Subject Added Entry-Uniform Title)
    • 648 (Subject Added Entry-Chronological Term)
    • 650 (Subject Added Entry-Topical Term)
    • 651 (Subject Added Entry-Geographic Name)
    • 653 (Index Term-Uncontrolled)
    • 655 (Index Term-Genre/Form)
    • 700 (Added Entry-Personal Name)
    • 710 (Added Entry-Corporate Name)
    • 711 (Added Entry-Meeting Name)
    • 751 (Added Entry-Geographic Name)
  • Subfield $e (Data Provenance):
    • 856 (Electronic Location and Access)
  • Subfield $l (letter “el”) (Data Provenance):
    • 760 (Main Series Entry)
    • 762 (Subseries Entry)
    • 765 (Original Language Entry)
    • 767 (Translation Entry)
    • 770 (Supplement/Special Issue Entry)
    • 772 (Supplement Parent Entry)
    • 773 (Host Item Entry)
    • 774 (Constituent Unit Entry)
    • 775 (Other Edition Entry)
    • 776 (Additional Physical Form Entry)
    • 777 (Issued With Entry)
    • 780 (Preceding Entry)
    • 785 (Succeeding Entry)
    • 786 (Data Source Entry)
    • 787 (Other Relationship Entry)
    • 788 (Parallel Description in Another Language of Cataloging)
  • Subfield $y (Data Provenance):
    • 533 (Reproduction Note)
    • 800 (Series Added Entry-Personal Name)
    • 810 (Series Added Entry-Corporate Name)
    • 811 (Series Added Entry-Meeting Name)
    • 830 (Series Added Entry-Uniform Title)

MARC 21 Authority Update No. 34 (Announced July 2022) to the Validation Rule Set that Includes All Valid Elements of MARC 21 Authority Format

You may now begin to use the following changes to Authority elements implemented as part of OCLC-MARC Authority Update for September 2022, based on the MARC 21 Authority format changes announced in MARC 21 Authority Update No. 34 (July 2022).

 Note: These changes apply only to the OCLC-MARC Authority validation rule set that includes all valid elements of MARC 21 Authority Format and cannot be used in the LC/NACO Authority File.

• In existing Authority field 373 (Associated Group):
  • New subfield $i (Relationship Information) has been defined
  • New subfield $4 (Relationship) has been defined
  • New subfield $7 (Data Provenance) has been defined
• In existing Authority field 382 (Medium of Performance):
  • Existing First Indicator (Display Constant Controller) has two new values defined:
    • 2 - Medium of performance of musical content of representative expression
    • 3 - Partial medium of performance of musical content of representative expression
  • New subfield $7 (Data Provenance) has been defined
• In existing Authority field 384 (Key):
  • Existing First Indicator (Key Type) has one new value defined:
    • 2 - Key of representative expression
  • New subfield $7 (Data Provenance) has been defined
• New Authority field 387 (Representative Expression Characteristics) has been defined
• In existing Authority field 856 (Electronic Location and Access):
  • Five new subfields have been defined:
    • Subfield $e (Data Provenance)
    • Subfield $l (letter “el”) (Standardized Information Governing Access)
    • Subfield $n (Terms Governing Access)
    • Subfield $r (Standardized Information Governing Use and Reproduction)
    • Subfield $t (Terms Governing Use and Reproduction)
• The following new Data Provenance Subfields have been defined in the respective Authority fields:
  • Subfield $7 (Data Provenance):
    • 024 (Other Standard Identifier)
    • 034 (Coded Cartographic Mathematical Data)
    • 043 (Geographic Area Code)
    • 065 (Other Classification Number)
    • 100 (Heading-Personal Name)
    • 110 (Heading-Corporate Name)
    • 111 (Heading-Meeting Name)
    • 130 (Heading-Uniform Title)
    • 147 (Heading-Named Event)
    • 148 (Heading-Chronological Term)
    • 150 (Heading-Topical Term)
    • 151 (Heading-Geographic Name)
    • 155 (Heading-Genre/Form Term)
    • 162 (Heading-Medium of Performance Term)
    • 180 (Heading-General Subdivision)
    • 181 (Heading-Geographic Subdivision)
    • 182 (Heading-Chronological Subdivision)
    • 185 (Heading-Form Subdivision)
    • 260 (Complex See Reference-Subject)
    • 335 (Extension Plan)
    • 336 (Content Type)
    • 348 (Format of Notated Music)
    • 360 (Complex See Also Reference-Subject)
    • 368 (Other Attributes of Person or Corporate Body)
    • 370 (Associated Place)
    • 371 (Address)
    • 372 (Field of Activity)
    • 373 (Associated Group)
    • 374 (Occupation)
    • 375 (Gender)
    • 376 (Family Information)
    • 377 (Associated Language)
    • 378 (Fuller Form of Personal Name)
    • 380 (Form of Work)
    • 381 (Other Distinguishing Characteristics of Work or Expression)
    • 382 (Medium of Performance)
    • 383 (Numeric Designation of Musical Work)
    • 384 (Key)
    • 385 (Audience Characteristics)
    • 386 (Creator/Contributor Characteristics)
    • 388 (Time Period of Creation)
    • 400 (See From Tracing-Personal Name)
    • 410 (See From Tracing-Corporate Name)
    • 411 (See From Tracing-Meeting Name)
    • 430 (See From Tracing-Uniform Title)
    • 447 (See From Tracing-Named Event)
    • 448 (See From Tracing-Chronological Term)
    • 450 (See From Tracing-Topical Term)
    • 451 (See From Tracing-Geographic Name)
    • 455 (See From Tracing-Genre/Form Term)
    • 462 (See From Tracing-Medium of Performance Term)
    • 480 (See From Tracing-General Subdivision)
    • 481 (See From Tracing-Geographic Subdivision)
    • 482 (See From Tracing-Chronological Subdivision)
    • 485 (See From Tracing-Form Subdivision)
    • 500 (See Also From Tracing-Personal Name)
    • 510 (See Also From Tracing-Corporate Name)
    • 511 (See Also From Tracing-Meeting Name)
    • 530 (See Also From Tracing-Uniform Title)
    • 547 (See Also From Tracing-Named Event)
    • 548 (See Also From Tracing-Chronological Term)
    • 550 (See Also From Tracing-Topical Term)
    • 551 (See Also From Tracing-Geographic Name)
    • 555 (See Also From Tracing-Genre/Form Term)
    • 562 (See Also From Tracing-Medium of Performance Term)
    • 580 (See Also From Tracing-General Subdivision)
    • 581 (See Also From Tracing-Geographic Subdivision)
    • 582 (See Also From Tracing-Chronological Subdivision)
    • 585 (See Also From Tracing-Form Subdivision)
    • 670 (Source Data Found)
    • 672 (Title Related to the Entity)
    • 675 (Source Data Not Found)
    • 677 (Definition)
    • 678 (Biographical or Historical Data)
    • 680 (Public General Note)
    • 700 (Established Heading Linking Entry-Personal Name)
    • 710 (Established Heading Linking Entry-Corporate Name)
    • 711 (Established Heading Linking Entry-Meeting Name)
    • 730 (Established Heading Linking Entry-Uniform Title)
    • 747 (Established Heading Linking Entry-Named Event)
    • 748 (Established Heading Linking Entry-Chronological Term)
    • 750 (Established Heading Linking Entry-Topical Term)
    • 751 (Established Heading Linking Entry-Geographic Name)
    • 755 (Established Heading Linking Entry-Genre/Form Term)
    • 762 (Established Heading Linking Entry-Medium of Performance Term)
    • 780 (Subdivision Linking Entry-General Subdivision)
    • 781 (Subdivision Linking Entry-Geographic Subdivision)
    • 782 (Subdivision Linking Entry-Chronological Subdivision)
    • 785 (Subdivision Linking Entry-Form Subdivision)
    • 788 (Complex Linking Entry Data)
• Subfield $e (Data Provenance):
  • 856 (Electronic Location and Access)

•  Caution: Name Authority Cooperative (NACO) participants cannot use these authority format changes in the LC/NACO Authority File at this time. The Library of Congress and OCLC will announce the implementation of these elements for use in name and subject authority records in the LC/NACO Authority File at a future date.

MARC 21 Holdings Update No. 34 (Announced July 2022)

You may now begin to use the following changes to Holding  elements implemented as part of OCLC-MARC Holdings Update for September 2022, based on the MARC 21 Holdings format changes announced in MARC 21 Holdings Update No. 34 (July 2022):

• In existing Holdings field 856 (Electronic Location and Access):
  • Four new subfields have been defined:
    • Subfield $l (letter “el”) (Standardized Information Governing Access)
    • Subfield $n (Terms Governing Access)
    • Subfield $r (Standardized Information Governing Use and Reproduction)
    • Subfield $t (Terms Governing Use and Reproduction)

OCLC Encoding Level K Now Invalid in WorldCat

OCLC continues work on moving toward the use of the standard numeric MARC 21 Encoding Levels in Leader/17 and away from the OCLC-defined alphabetic Encoding Levels. In early 2021, OCLC began to convert the nearly 26 million WorldCat Encoding Level K records to the standard MARC values blank, 7, or 3, as appropriate according to algorithmic determinations of record fullness. In August 2022, we announced that all of the approximately 25.6 million K-level records had been converted With the completion of this phase, OCLC has now made Encoding Level value K invalid in WorldCat.

Beginning in February 2022, OCLC began converting the roughly 40 million Encoding Level I records in the same manner and have now completed about 17 million. Beginning in mid-2022, OCLC began converting the approximately 350 million Encoding Level M records and have completed about 3 million. To preserve the historical metadata that identifies Encoding Level M records as having been batch loaded, OCLC has been adding field 936 with the designation BATCHLOAD to these formerly M-level records.

When entering original cataloging records into WorldCat, all OCLC participants are encouraged to create records using the appropriate MARC 21 Encoding Levels: value blank for full level, value 7 for minimal level, or value 3 for abbreviated level. Please follow the definitions, restrictions, and requirements outlined in BFAS Chapter 2.4, “Full, Minimal, and Abbreviated-Level Cataloging” and the page for Encoding Level. For further information on the rationale behind these changes, please see “Updates on OCLC Encoding Levels,” the June 2020 Virtual AskQC Office Hours presentation slides, WebEx recordings, and Q&A, all available on the Previous AskQC Office Hours page.

Correction of Validation Relationships in Bibliographic Field 382

In Bibliographic field 382 (Medium of Performance), if subfield $e (Number of ensembles of the same type) is present, then either subfield $a (Medium of performance) or subfield $p (Alternative medium of performance) must be present.

Unicode Characters Valid in Additional Local Holdings Record (LHR) Subfields

Unicode characters are now valid in the following Local Holdings Record (LHR) subfields:

• Subfield $2 in LHR fields 017, 024, 337, 338, 347, 506, 583, 845, 852, 853, 854, 855, 856, 866, 867, 868
• Subfield $b in LHR field 014
• Subfields $s and $t in LHR field 852
• Subfield $u in LHR fields 506, 538, 561, 563, 583, 845, 852, 856, 883, 884
• Subfields $y and $z in LHR field 022
• Subfield $z in LHR field 020

Correction of Validation for Authority Fields 080, 082, and 083

In all OCLC-MARC Authority rule sets, field 080 subfield $2 will now accept correctly formatted edition identifiers, and fields 082 and 083 subfield $2 will now accept correctly formatted edition information.

Correction of Validation for Bibliographic Field 046

In Bibliographic field 046, the validation relationships among subfields $a (Type of date code), $b (Date 1, B.C.E. date),$d (Date 2, B.C.E. date), and $e (Date 2, C.E. date) have been corrected.

Correction of Validation for Subfield $2 in Bibliographic and Local Holdings Records (LHRs)

Validation relationships related to subfield $2 have been corrected in:

• Bibliographic fields 083, 340, 341, 342, 344, 345, 346, 347, 567, and 852
• Local Holdings Record fields 347, 852, 853, 854, and 855

Virtual AskQC office hours

Join OCLC Metadata Quality staff to discuss WorldCat quality issues and cataloging questions. Visit AskQC for information about upcoming office hours, previous office hour recordings, and supporting materials.

Support website(s)

• OCLC Connexion
• WorldShare Record Manager
• WorldShare Collection Manager
• OCLC Community Center
• Cataloging documentation
• Contact OCLC Support