[Archivesspace_Users_Group] Speaking of MARCXML punctuation

Thu Apr 18 12:52:23 EDT 2019

Since the PCC is starting their two phase implementation of the new policy regarding limited use of ISBD punctuation in bibliographic records, which option for ISBD punctuation will ArchivesSpace follow?  Is it possible to have a configuration setting so that we can choose to determine our preference?

For those who are unfamiliar with the decision regarding ISBD punctuation, I’ve copied the announcement(s) below.

--Miloche

••••••••••••••••••••••••••••••
Miloche Kottman
Head of Cataloging & Archival Processing
University of Kansas Libraries
Lawrence, KS 66045
mkottman at ku.edu<mailto:mkottman at ku.edu>
785-864-3916

Xiaoli Li xlli at ucdavis.edu via<https://support.google.com/mail/answer/1311182?hl=en> kansas.onmicrosoft.com

Apr 2, 2019, 11:04 AM

to PCCLIST

PCC colleagues,

Last December, I announced the new policy regarding limited use of ISBD punctuation in bibliographic records. Since then, we have been working on the implementation plan. The complexity of implementing all three options outlined in that email (dated 12/12/2018 and included below) at the same time presents more challenges than we anticipated. In addition, there are issues pertinent to access point fields that require more discussion. We believe we should move forward but need to do so in a way that is manageable and will allow us to achieve some consistency. After considering all the possibilities, we have revised the policy which to address punctuation in descriptive fields only. The revised policy will be implemented in phases:

Phase 1: Beginning April 8, 2019, PCC libraries will have two options regarding inclusion of terminal periods when newly authenticating bibliographic records:

a.       Continue current practice (fully punctuated); code Leader/18=i

b.       Omit terminal period in any descriptive field*; code Leader/18=i

*Exception: terminal periods integral to the data (e.g., recorded as part of abbreviations, initials, etc.) should not be omitted.

Special Note: when updating an existing PCC record, catalogers should follow the punctuation pattern already established in that record.

The guidelines for Phase 1 and a spreadsheet containing all MARC fields that are affected by the new policy are attached to this email. Both documents have also been posted on the PCC website:

  *   Guidelines: http://www.loc.gov/aba/pcc/documents/guidelines-terminal-periods.pdf<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2Fguidelines-terminal-periods.pdf&data=02%7C01%7Cmkottman%40KU.EDU%7Cb34fc0cb398f42c588c808d6b784e9ac%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636898178926315861&sdata=TFFIiTGcCPJhdT2X8h%2BZXNnA9CiUwYkocbrZB2cINt8%3D&reserved=0>

  *    Spreadsheet: http://www.loc.gov/aba/pcc/documents/final_punctuation_all_MARC_field.xlsx<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2Ffinal_punctuation_all_MARC_field.xlsx&data=02%7C01%7Cmkottman%40KU.EDU%7Cb34fc0cb398f42c588c808d6b784e9ac%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636898178926315861&sdata=AkyMo3xU8BdbNz1ML%2FAbKebd3ZIukQ7XZ0zY6BiHAio%3D&reserved=0>

Phase 2: [Implementation date to be determined.] PCC libraries may begin to omit ISBD punctuation between subfields and terminal period of any descriptive field as long as Leader/18 is coded as “c”.

The implementation date for Phase 2 will depend on the following:

a.       Completion of style guidelines containing instructions and examples

b.       Completion of specifications for and availability of tools for automatically removing or adding punctuation (e.g., macros for OCLC Connexion Client, etc.)

Following these two phases, the Policy Committee will review the pros and cons of omitting final punctuation in access point fields.

The work on the limited use of the ISBD punctuation in PCC records began in March 2011. It took many groups’ work to get us to where we are now. I want to take this opportunity to express my sincere appreciation to anyone who has helped to make this happen.

Please let me know if you have any questions.

Xiaoli Li
PCC Chair
Head of Content Support Services
UC Davis Library
(530) 752-6735

Xiaoli Li xlli at ucdavis.edu via<https://support.google.com/mail/answer/1311182?hl=en> kansas.onmicrosoft.com

Dec 12, 2018, 2:20 PM

to PCCLIST

PCC colleagues,

At its recent meeting<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2FPoCo-2018%2FPoCo-Agenda-2018.pdf&data=02%7C01%7Cmkottman%40KU.EDU%7C35d0897ae6e542b2260e08d6606f3b8c%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636802428193869196&sdata=%2BR8PADLqQSmFUghu%2BDm6tBeBqKvbEw1k8XZOrmaBMKs%3D&reserved=0>, the PCC Policy Committee reaffirmed its decision to allow bibliographic records with limited ISBD punctuation to be treated as full-level PCC copy. This decision comes after reviewing feedback from test participants who evaluated three test sets of records provided by Library of Congress, the National Library of Medicine, and OCLC. For more information about the test, please read the message below or click here<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2Ftest-records-punctuation.html&data=02%7C01%7Cmkottman%40KU.EDU%7C35d0897ae6e542b2260e08d6606f3b8c%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C1%7C636802428193879200&sdata=R02GG%2BOgroC5XeUuLaWPTa7sFKqv%2BFtxoi7ZIxXJOFY%3D&reserved=0>.

Beginning in spring 2019, PCC libraries will have three options to handle ISBD punctuation when authenticating new records:

  1.  Continue current practice
  2.  Omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) “i”
  3.  Omit ISBD punctuation between subfields of descriptive fields and omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) “c”
* Exception: Terminal periods integral to the data (e.g., recorded as part of abbreviations, initials, etc.) should not be omitted.

Options 2 and 3 are optional, not mandatory. However, creating records with limited punctuation is expected to save time for catalogers, simplify training of new catalogers, make it easier to map data to and from other formats, and allow for an easier transition to linked data or vice versa (e.g., mapping BIBFRAME to MARC).

To facilitate the implementation, PCC will:

  1.  Develop and maintain style guidelines for records with limited punctuation;
  2.  Provide adequate training resources for catalogers and revise PCC documentation to update policies and include examples with limited punctuation;
  3.  Request that LC Network Development and MARC Standards Office and bibliographic utilities revise MARC 21 documentation to include examples with limited punctuation;
  4.  Work with bibliographic utilities and other interested parties to develop tools and specifications to automate the process of removal or reinsertion of punctuation;
  5.  Encourage vendors, bibliographic utilities, etc., to explore functionality to index and display records with limited punctuation as defined by the PCC;
  6.  Encourage vendors, bibliographic utilities, etc., to explore functionality to allow their users to easily add or remove punctuation as needed.
The Policy Committee is in the process of developing a detailed implementation plan which will include the aforementioned style guidelines. I will share more information with you as it becomes available. In the meantime, if you have questions, suggestions, or comments, please feel free to contact me.

Sincerely,

Xiaoli Li
PCC Chair
Head of Content Support Services
UC Davis Library
(530) 752-6735

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190418/8809c7dd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 43 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20190418/8809c7dd/attachment.gif>