[DCRM-L] OCLC update: Distribution of the Library of Congress Name Authority File

[James,Kate]

Hello, I am distributing this message on behalf of my colleague. Please excuse cross-postings.

Greetings, all,

Throughout July, we shared that OCLC is working closely with the Library of Congress during their system migration, and we continued to update NACO contributors among the OCLC community with key information. We're pleased to share that OCLC has started loading the updated Name Authority File (LCNAF) as planned.

Reminders:

  *   As previously communicated, new or edited records cannot be submitted via OCLC's Connexion and WorldShare Record Manager applications until 19 August, unless otherwise notified.
  *   Please note, the value of the 005 field will represent the date an authority record was loaded into their new system. Folio.

New information:

  *   Field 375 has been removed in all existing Library of Congress Name Authority Records (NARs) to reflect current LC-PCC policy in recording gender. Please refrain from adding field 375 to avoid record rejection.
  *   Library of Congress authority data now uses Unicode format. Continue to follow NACO policies regarding the use of certain characters such as the Eszett and Euro until further notice. While LC/NACO authority records will no longer be guaranteed to be MARC-8 compatible, records will need to be UTF-8 compatible.
  *   The Unicode format affects OCLC's validation process. OCLC will address validation issues in an upcoming system release. For now, please be aware of the following changes:
     *   Connexion Client display: Some CJK characters may display as individual radicals or syllable components rather than as composed characters. As long as the characters you enter have the appropriate Unicode codepoints, this display difference should not affect functionality.  Versions 2.63 and 3.1 do have some differences related to character display, even though the characters are the same behind the scenes. Please reference the updated FAQ for visual examples.
     *   Validation in Record Manager: if a record contains a decomposed character that is identified as an "invalid character", you may not be able to complete a final action on the record.  Should you encounter this issue:
        *   You will need to complete your work using Connexion until changes are made in an upcoming system install,
        *   Another option, should it be needed prior to the install, is to send a message to authfile at oclc.org<mailto:authfile at oclc.org>, and OCLC staff will work with you to execute the final action and ensure your MARC Organization code is added in the 040 field.

For more information about the impact on OCLC users, please refer to our updated FAQ: https://help.oclc.org/Metadata_Services/Authority_records/Library_of_Congress_FOLIO_Migration_FAQ_for_OCLC_NACO_Users

We thank you for your cooperation and will continue to update the OCLC community with important information. If you have any questions for OCLC, please contact Becky Dean (deanr at oclc.org<mailto:deanr at oclc.org>).

In case you missed it, the Library of Congress shared the following information earlier this week:

  1.  All new and/or modified MARC fields and subfields in the authority format will now be available for use, following the LC Guidelines<https://www.loc.gov/aba/publications/FreeDCM/DCM/ZAU.pdf>. DCM Z1 and the LC Guidelines will be updated around the end of August to reflect the new fields and subfields that are now available.
  2.  The improvements in the speed of processing means that the update cycle should now only take about 24 hours.
  3.  All 375 fields in personal name records have been removed. Please note that if anyone adds a 375 to a name authority will have their record rejected through the validation process of distribution.
  4.  Full Unicode implementation is now possible. The PCC Policy Committee is in the process of looking at the policy changes that are now possible due to this system change. In other words, don't suddenly start adding any and all scripts! All current policies regarding characters and scripts remain in effect. But the technical barrier to changing the policies is now gone. As decisions are made on what changes NACO wishes to implement, NACO will make announcements and update the documentation as quickly as possible.
  5.  Batch changes to family name NARs to allow them to be used as access points will now be considerably easier and should happen shortly after the re-start.
  6.  We have finally been able to convert all RDA-eligible AACR2 NACO records to RDA (i.e. 008/10=z; 040 $e rda).


Kate

Kate James  (she/her/hers)
OCLC * Program Coordinator- Metadata Engagement, Global Product Management
6565 Kilgour Place, Dublin, Ohio, 43017  United States
[cid:image001.png at 01DC0D17.6F427EF0]<https://help.oclc.org/WorldCat/Metadata_Quality/AskQC>
OCLC.org<https://www.oclc.org/en/home.html>* Twitter<http://twitter.com/oclc> * Facebook<http://www.facebook.com/pages/OCLC/20530435726> * YouTube <http://www.youtube.com/OCLCvideo> * LinkedIn<https://www.linkedin.com/company/oclc>* Instagram<https://www.instagram.com/oclc_global/> *Next blog<http://www.oclc.org/blog/main/>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20250814/8b8ad9ad/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 15635 bytes
Desc: image001.png
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20250814/8b8ad9ad/attachment-0001.png>