In January 2017, MARCIVE announced Comprehensive Notification Service, or CNS. This was spearheaded by our former Director of Bibliographic and Authority Services, Mary Mastraccio, after years of identifying deficiencies in maintaining only the authority files for libraries.  This has been a challenging undertaking; involving most staff members and partner libraries.  We have received great feedback from customers that we used to create additional options to make the service as flexible and user-friendly as possible.

Fun CNS Facts (as of December 2019):

•  We have 45+ customers
•  Roughly half of the libraries are academics and half publics, plus 3 school libraries, and a government library
• 13 different library systems are represented
• Semi-annually update frequency is the most popular one, followed by yearly update
• The smallest backfile had 36,021 bib records, and the largest to date had 5,904,972 initial bib records

MARCIVE receives commonly-asked questions and has created a FAQ sheet to be provided to new CNS customers.  A question that cannot readily be answered is how many records your library will receive at an update.  Since CNS has three scheduling options:  annually, semi-annually and quarterly, the amount of records that reflect changes naturally goes up the more time has passed. But other cataloging updates from PCC (Program for Cooperative Cataloging), large changes from the Library of Congress (RDA changes, for example), or changes to profile specifications (e.g. examining FAST terms), or MARCIVE upgrades (like fine-tuning our genre processing) can have an impact.  Broadly speaking, a CNS customer can expect to receive 5-15% changed bib records with each scheduled update.

The most exciting aspect of Comprehensive Notification Service is the ability for libraries to receive bibliographic record updates as a subscription, ensuring the catalog is always as current as possible. Another important thing to note is the flexibility in choosing options.  For example, your library may not be interested in adding identifiers to the records currently (Subfield 0 URI or control number), but can choose to add the option at a later update, without having to plan or allocate funding for a stand-alone catalog enhancement.

Just signed up for CNS and have questions?  Start here with this document.

Feel free to reach out to us at [email protected] for a consultation on our services.

November 1, 2018

In February 2017, MARCIVE released a new product that helps libraries keep a better handle on how authorities processing is performed in their ILS or LSP.  Over the years, customers had commented how once an initial backfile authorities processing project was completed and Standard Notification Service was begun, their systems didn’t always do a good job using the monthly updated authority records to revise the associated bibliographic records.  It was difficult to pinpoint why and in what cases an access point would not be updated, even though the proper information was present in the revised authority record.

Comprehensive Notification Service retains the bibliographic as well as the authority records, and periodically refreshes them using the newest authorities files on either a quarterly, biannual, or yearly frequency.  Only the bib records that reflect a change are provided, along with new/changed/deleted authority records.

Access points that were previously unmatched are updated when matched to new authority records through CNS.  Any new fields reflected by new policies in RDA, and continual improvements to MARCIVE processing are also seen.

The number of records changed is typically less than 5%, but different factors can affect the statistics:

–A change to a prolific access point is released by LC, so many records are affected.

–Changes in a profile option.  For example: A library that didn’t ask for processing of FAST access points at the onset and later requests it will see a large increase of changed records.  Or a library that decided to have URI identifiers added to their processing asked us to add that free option with the next update.

Subscribers can send in both bib and authority deletes before the next processing to keep the history files current.

If a library decides they don’t want to track deletes because they weed a great deal, or don’t have the staff to keep up can send their entire database to replace the current history and use that as the input file.

Although CNS was created with Ex Libris Alma members in mind, there are 10 different systems among customers of public, military, and academic libraries of various sizes.  Both public and academic consortia are represented as well.

For more information, please go to https://home.marcive.com/blog/new-comprehensive-notification-services-cns

January 25, 2018

Now as a part of RDA processing performed during authorities processing, we have the ability to create fields that can assist with formulating format facets, and prepare for linked data.    These new 34X fields provide consistency in describing the characteristics of various formats.  They are:

340      Physical Medium
344      Sound Characteristics
345      Projection Characteristics of Moving Image
346      Video Characteristics
347      Digital File Characteristics
348      Format of Notated Music

The conversion is only as good as the data elements that typically are already present in the MARC record in various fields and subfields.  Our processing looks at the LDR, 007, 008, 300, 533, and 538 fields to accurately create the new 34X fields.

Libraries looking to do authorities processing and RDA conversion on their legacy cataloging records can have this new processing included.  Existing customers can request that we add this option to any new bibliographic records sent for processing.  And even better yet—Comprehensive Notification customers can have this option applied with their next processing run—essentially having the entire backfile performed to include new RDA tags.  There is no additional charge for this option.

Here are some examples.

Interested in learning more?  Send us a sample and we can show you all the good we can do to make your records more useable.  Contact us at [email protected].

Written by Joan I. Chapa, MLS

Type of Library: Public
LeRoy Collins Leon County Public Library
Project Coordinators:
Cay Hohmeister, Library Director
Christopher Gorsuch, Library Services Manager for Collection Management
Paul Clark, Application Systems Analyst II

Address: LeRoy Collins Leon County Public Library, 200 W. Park Avenue, Tallahassee, FL  32301-7716

Telephone Number: 850-606-2665

E-Mail: [email protected]
[email protected]
[email protected]

Problems To Be Solved:

1. Make the Enterprise SirsiDynix Symphony catalog more unified and easier for patrons to search
2. Provide an easy way for parents to find suitable materials for reading incentive programs
3. Implement RDA conversion

MARCIVE Solutions:

1. Authorities processing with RDA Conversion
2. Reading Notes Enhancement with Lexile, and Accelerated Reader data

The Story

In 2013 the coming of RDA (Resource Description and Access) to the general library community forced our library to address how we were dealing with name and subject authorities, as well as how we would render a display of our bibliographic records. There was little incentive to deal with a long, labor-intensive project involving the conversion of AACR2 to RDA standards, especially since some of our records represented missing or withdrawn materials.

Needs identified, and MARCIVE selected

In the time leading up to our conversion, we conducted a selection of a vendor to perform the conversion of name and subject headings, as well as the conversion of bibliographic records to RDA standards.   MARCIVE was eventually selected through the usual competitive bid process for outside contractual services for Leon County, Florida. As a result, MARCIVE was awarded the contract for the following reasons:

1. MARCIVE could do what we needed them to do, according to the RFP (Request for Proposal)
2. MARCIVE was the most cost-effective
3. MARCIVE had many years of experience performing similar projects with similar-sized systems
4. MARCIVE could also provide additional AR/Lexile rankings in our bibliographic records

The last point regarding reading rankings was not originally part of the charge. However, when it was realized that such a long-desired enhancement could be effected without major alteration to the original mission (and without any additional cost), it became one more reason to select MARCIVE.

Funding obtained

The funds for this project were acquired through our county Management of Information Services process for FY 14/15. The funds were included in the capital projects for FY 14/15.In March 2014, a detailed request for $17,500 was submitted to update the catalog database, establish authority control, adopt RDA cataloging standards and provide AR/Lexile rankings. The initial run was estimated to be 350,000 bibliographic records. The funds were included in the capital projects.

Funding was approved by the Leon County Board of County Commissioners for FY 14/15. Capital funds may be carried forward in case the project extended into the following fiscal year.

The Process

All of this required some planning for our downtime, both internally and externally. This meant dealing with the bibliographic records for which items had been missing an extraordinary amount of time or items which had been lost, and otherwise paid for or reconciled. Throughout this process, MARCIVE was available to help walk us through the process and were able to schedule the actual freezing of the catalog and the ultimate flip to adding the new bibliographic and authority records at a time convenient to the library and our patrons.

Leading up to the project itself was the preparation work necessary for both our catalog and our staff. This meant implementation of the latter:

1. Establish realistic missing and searching protocols for library materials. In some cases, items had been “missing” or “lost-assumed” for ten or more years. The time now is 18 months, and then it is deleted from the system.
2. A one-time deletion of titles and items which had been in such status for over 18 months (this was after circulation information had been transferred to a separate file). This resulted in the elimination of almost 60,000 titles and almost 150,000 items.
3. This resulted in not only a more accurate catalog with which we provided MARCIVE but a reduced, per bibliographic charge for the whole initial project.
4. From the initial deletion onward, the staff has been diligent in searching for and/or resolving items in the various lost categories. The lists from which they operate are now of realistic size, and they can be processed in the time allowed.

Feedback from reference desk, Technical Services staff, and Patrons

After the actual changeover to our new records on 27 August 2015, we were anxious to hear any feedback on how the searching and retrieval of the records from the staff and the public users. In our case, “No news is good news.”  After about two weeks, after hearing nothing one way or the other, I asked managers and branch heads if they had any feedback at all after the first day of usage. The unanimous response was that no one had said anything, including the staff, which had made the transition from display of GMDs to display of 33X tags without any anticipated problems.

To a great extent, MARCIVE provided the support that resulted in a seamless, virtually invisible transition. Also, the addition of AR and Lexile scores and points has become relied on heavily by parents and schoolchildren in Leon County, thus creating a bonus win for our system. A special page was created for this purpose.

One of the factors in the success of this project was keeping the staff apprised of the progress of the project, and getting their buy-in for its success. There was some concern over losing the display of the GMDs from the index screens, but because we were offering equivalent displays using 33x tags, this concern was met. A day or so before we went live with the new bibliographic and authority records, the Director and the Head of Collection Management met with every branch manager and the department head in the main library, as well as with staff members, to show exactly what the new records would like, where their information had (or had not) moved, and to answer any questions regarding this. This proved to be effective, especially having it so shortly before going live.

Additional orientations were provided the Library Management team, as well as the Library Advisory board. The process and results of this project became the basis for a presentation “RDA Bibliographic and Authority Records: Preparing the Way!” given at the May 2016 COSUGI (Customers Of SirsiDynix Users Group, Inc.) by Chris Gorsuch and Paul Clark.

Continuity—Keeping the catalog up to date

Since the establishment of RDA bibliographic and authority records, the work continues. Routines have been refined around the new cataloging records sent for processing through Overnight Authorities Service and the monthly Notification Service files. If authorities have not been resolved during the cataloging process, they are caught each month and forwarded to the head of Collection Management for disposition or resolution. This results in fewer conflicts being noted because the authority records are already established in our local system. Also, blind references are removed when the last item is discarded/withdrawn from the catalog. This results in less patron frustration, and a more accurate picture of what is available through our system. We are very pleased to offer an up-to-date, accurate and attractive online catalog for library users.

February 23, 2017

Now we have an alternative way to keep your catalog up to date after the initial authorities processing/RDA Conversion project has been completed, through Comprehensive Notification Service (CNS).

We will retain both a copy of the matching authority records we supplied as well as the updated bibliographic records.  You should continue to send us new cataloging through Overnight Authorities Service on any time frame desired—daily, weekly, monthly, etc.  There’s never a minimum order, the work is done overnight, and updated bib records are posted the next business day for FTP retrieval, along with any requested reports.  The results of this processing are added to both the retained bib and authority files.

Then at the frequency of the library’s choosing, we will re-process the bibliographic records using all the same specifications, returning to the library only the changed bibliographic records, any NEW authority records, as well as authority records changed or deleted by LC, along with any reports.

Why would a library choose this subscription instead of Standard Notification Service?

CNS is a desirable method of maintaining records if your library’s ILS or library service platform does not have the function to fully update the corresponding bibliographic record with the corrected access point.  Sometimes the system has the capability but has difficulty converting the entire string in an access point.  CNS keeps a copy of your bibliographic records and the authority record files provide by MARCIVE.  The library chooses how often to update:  Quarterly, Semi-annual or Annual.  Pricing varies depending on the size of the bibliographic file, and how often you request the update. We ask you to list preferred dates for the bib updates.

What’s included with the Comprehensive Authorities Notification Service?

1.     Flip of access points to current LC practice.  This includes the update of access points that were not recognized when we did the initial processing.
2.     Inclusion of any NEW authority records on matched access points.
3.     Inclusion of any CHANGED authority records on access points that first matched during the initial processing, and any authority records deleted by LC.  It additionally includes differentiated authority records which were formerly undifferentiated.
4.     Undifferentiated-Differentiated.

In identified bib records, the access point will now match to a new authority record and the bib record will be changed.  Note:  several sources are used (e.g. 670 field, VIAF record, etc.) to verify a proper match.

5.     Partial matches that become full-string matches.
6.     Terms that change tagging.
7.     Fields that reflect changes in RDA.

What’s NOT included in Comprehensive Authorities Notification Service (CNS)?

If any type of enrichment (TOC, Summaries, Fiction/Biography data, Lexile or Accelerated Reader) is a part of your profile, that data will not be added during the re-processing of the bibliographic records during CNS.  This only happens during Overnight Authorities Service, or as a stand-alone project.

Commonly Asked Questions ABOUT CNS

1.     It’s time for my first update, and I haven’t yet sent any new records for processing, but I want them included.  What should I do?

MARCIVE Response:  Go ahead and send the file now, just as you normally would through Overnight Authorities Processing.  You’ll be charged the standard rates for this work.  These bibliographic records will be included in the update and will be added to the retained bib file.

2.     It’s time for our update, and our systems librarian is out on medical leave.  Can we re-schedule?

MARCIVE Response:  Yes.  Let us know when you are ready for this work.  Remember that you have pre-paid for the subscription and your updates need to occur within the subscription year.

3.     We have performed a large weeding project in our library and deleted a number of bibliographic records.  How do we let you know what we have deleted?

MARCIVE Response:  There are two ways to do this.  We can provide directions for sending us the control numbers of the bibliographic records to be deleted, and they will be removed from your history at the quoted rates.  The alternative method is to send us your entire bib file again, and we will replace your retained bib file with the new one.  Contact your Marketing Representative for a quote.

4.     We’re completing our profile with MARCIVE, and are trying to decide which Notification subscription is best for us.  Can you help us choose?

MARCIVE Response:  CNS was created in response to those libraries stating that while their ILS or LSP could update the main bib access point in a string using an updated authority record, often it could not update it if there were subfields included.

If your system can reliably perform this function, then we would suggest you choose the Standard Notification Subscription. Authority records are retained in your “history file.”  Also, we retain any unmatched headings for future updates through the NewMatch option.  You send new cataloging to us through Overnight Authorities Service, and any authority records produced are compared to your history file, and only those new to you are distributed.  These new authority records are added to your history file, which continues to grow.  With this subscription, you’ll rely on your local ILS or LSP to use the monthly files of changed/deleted authority records to update the associated bib records.  The advantage to this subscription is that because you get monthly updates, your catalog will be more current and in sync.

If your system has an issue with using an authority record to update an entire access point string, or there are problems running authority updates on a monthly basis, then CNS would likely be the better option.  Your entire bib file will be completely refreshed at the time interval of your choice and will include any new standard bibliographic processing functions that we have added.  The library does need to be aware that any access point that is processed through authorities processing and RDA conversion may overlay and therefore remove any in-house editing unless internal protections have been put in place.

5.     We are planning to do authorities processing/RDA conversion in preparation for migrating from a legacy system to ExLibris Alma.  We won’t be able to or need to do any ongoing authority work, will we?

MARCIVE Response:  According to reports from Alma users, there is an internal mechanism to automatically link bib access points to an external authority file.  However, this doesn’t always work as well as expected.  While Alma users don’t have the need for authority records, we can still process new cataloging through Overnight Authorities after the initial project has been performed, and more importantly, refresh the bib file on a periodic basis through CNS.  This frees the cataloging staff from having to continually confirm that bib access points are indeed being updated.  Additionally as described above, the library will benefit from any new options that have been developed as a result of RDA and other new cataloging standards and implemented for this service.

Further questions?  Would like some examples of changes provided through CNS? Give us a call at 1-800-531-7678 or email us at [email protected], and we will be happy to discuss your options and provide pricing.

Written by Joan Chapa, MLS

Libraries migrating to shared environment will be interested in the upcoming presentation given by Michael Cohen from the University of Wisconsin libraries: “Collocating the Collective: Third Party Database Remediation in an Alma Consortium” to be given at the ELUNA conference on May 6 at 9 am.  This conference will be held at the Cox Convention Center in Oklahoma City.

The Wisconsin libraries previously were on individual Ex Libris Voyager systems, and merged their bibliographic databases into a shared Alma consortial database.  After the merge, MARCIVE performed data remediation which included authorities processing and RDA conversion on over 8.5 million records.  The project was completed in January 2016. This presentation will discuss the highlights of that journey—including the decision making process, project configuration, file management logistics, affected cataloging policy, and lessons learned along the way.

Written by Joan Chapa, MLS

We have heard this question a few times now, and it’s a valid one. LC’s Program for Cooperative Cataloging (PCC) has recommended against an automated conversion of the 260 fields to 264 if the record is a serial or integrating resource. It is difficult or impossible to program this reliably. Since MARCIVE follows PCC recommendations, records coded as serials or integrating resources will not have the 260 changed to 264. It IS acceptable to manually change these locally.

PCC additionally recommends not changing the 260 for multi-volumes items. After reviewing records and doing extensive testing, MARCIVE is excluding records with date type [008/06] m, c, d, e, k, i, q, or u in the programming used to convert 260 fields to 264 fields. This is being done to avoid the risk of creating incorrect 264 second indicator values.

For more information about the 264 field, see the PCC guidelines about this field.

Written by Joan Chapa, MLS

Converting legacy data to RDA is a challenging idea to take hold in public libraries because of a school of thought regarding the short-lived nature of the collection. If your collection flips over every 15 years, why do anything with the legacy data?

Converting to RDA preps your data for the next generation systems and organizes your records in a layout that is easier for patrons to understand. Public libraries, in particular, have more formats than many other types of libraries, so the blanket term “electronic resource” is no longer relevant in today’s information environment. But don’t take our word for it, here is why some of our happy customers converted to RDA:

Cuyahoga County Public Library
Lori Ann Thorrat, Catalog Department Manager

“Cuyahoga County Public Library chose to convert our data to RDA for simplicity. Having our data in RDA format created a level of consistency that simplifies the configuration of the public catalog, improving our customer’s ability to find and retrieve materials. Dates are very important both for searching and sorting data.  Just having all of our publication dates in a single MARC field allows us to streamline how records display and sort in the public catalog. Because RDA is an internationally recognized standard, having our data already in RDA format will facilitate the conversion of our legacy data to Bibframe, the next generation schema for bibliographic data.”

Somerset County Library System
Adele Thoma Barree, Head of Technical Services

“We know that we will not have our current ILS forever, and that RDA is designed to handle links and connections among all types of data.  Getting our database in the best possible shape for the future is something MARCIVE can help us with by modifying our bibs to reflect basic RDA format.  We are very glad you offer this service!”

Thousand Oaks Public Library
Stacy Gordon, Cataloging Librarian

“Legacy data is worth converting so that older materials become as discoverable as new materials, especially as library management systems and other discovery layers begin to take more advantage of the new fields for content, media, and carrier type.  Since these fields (336, 337, and 338) have controlled vocabularies, greater consistency will be achieved between older and newer records.  As well, when BibFrame is ready to replace MARC, more of your records will be ready to be crosswalked to the new metadata standard that will be more compatible with other information systems in the greater linked data world.

Library catalogs have gone through many changes, and a recent change is to the new cataloging standard,  RDA.  Among the benefits of RDA are fewer abbreviations (no more “ill.” for illustrations or  the Latin “s.l.” for “Place of publication not identified,” and many others), more relationships identified between works, entities, manifestations, and items, as well as between persons, families, and corporate bodies and these FRBR requirements, and a catalog that’s data conform better to what’s being seen in the wider world outside of libraries.  Conversion would provide for greater consistency within your catalog, and will allow users to find information more easily, with RDA’s allowance for a greater number of access points, increasing discoverability.

We had no trouble deciding to go with MARCIVE for performing the retrospective conversion of our database to RDA.  We have had MARCIVE do our authority control for 12 years, and they have been extremely fast, reliable, and with gracious customer service.”

 –written by Ligia Groff, MLS

In the development of RDA (Resource Access and Description), the GMD (General Material Designation) 245$h was removed in lieu of using the CMC (Content, Media, and Carrier) 3XX fields to describe the medium of the item in a more representative way.  This action was due in part to the explosion of e-resources and varying technology needed to access these resources.  This change caused quite a stir here in our office, as well as in many libraries across the nation.  We often get asked what to do with the GMD, and we are hesitant to provide a definitive answer, because the value of the GMD varies from library to library.

PCC Guidelines on Hybrid Bibliographic Records recommends that the GMD not be removed until March 31, 2016.  In compliance with that statement, OCLC plans to remove the GMD from all of its records at that time.  For that inevitable change, many libraries are asking us to delete the GMD when we conduct RDA conversion.  Another reason libraries are asking us to remove the GMD is because they have already upgraded to a next-generation system that currently uses the 3XX fields to generate the icons that determine the resource’s medium.  We also have the option to move the 245$h to another field.

Some libraries are asking us to keep the GMD because they have not upgraded systems, and the GMD is vital in determining the medium.  For these libraries, it may be impossible for the patron to determine what the resource is, and acquisitions and reference staff (among others) would have to open the each record to determine the medium, causing a lag in workflow.  Many libraries have also taken great care in generating their own, not-so-standard qualifiers for the GMD’s, for example [videorecording (DVD)].  Due to staff and patrons being so accustomed to locating their content using these qualifiers, they are hesitant to relinquish all that work if they are unsure of how the new records will interact in their system.  MARCIVE’s current processing does not alter these non-standard GMD’s. For the libraries that wish to retain their GMD, MARCIVE offers the option to simply retain the 245$h, or to create the GMD from the 3XX and other fixed and variable fields for a small one-time fee.  We do not have set pricing for generating customized GMD’s, but we are always open to evaluating data and criteria in order to better ascertain programming costs.

For quote for RDA conversion or other services please contact us.
-written by Ligia Groff, MLS