Posts Tagged ‘RDA’

NEW! Comprehensive Notification Services (CNS)

Written by Joan on February 23, 2017. Posted in Blog

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

OCLC removing GMDs–now what?

Written by Joan on March 29, 2016. Posted in Blog

March 29, 2016

With the transition to the new RDA format, the GMD (General Material Designation) in the MARC 245 $h field is no longer used, and has been replaced with the more definitive CMC (Content, Media, and Carrier) which are the 336, 337, and 338 fields.

However, many local systems still use the GMD and some customers have asked us to retain it while processing their records through RDA Conversion (RDACS) and authorities processing.

As recommended in the PCC Guidelines on Hybrid Bibliographic Records, OCLC has retained the 245 h GMD for a period of 3 years in WorldCat records where it currently exists.  That time period is up on 3/31/2016.  OCLC will begin a project to remove all GMDs from the bibliographic records in their database.  After this work is done, libraries still wanting to use the GMD will have to create them in the records they download from OCLC.

Although rules state that the GMD must not be used in RDA records, some library integrated systems still rely on it.  For those customers that still require the GMD, MARCIVE can create them in records processed for authorities processing/RDA conversion for a nominal fee.  This can also be performed for records distributed through our Ongoing GPO Database Service.  It is not available for the Cataloging Record Distribution Project records, as it is not a part of the GPO contract.

While it isn’t difficult for many libraries to perform a global delete of unwanted GMDs, we can do so easily in records that we process for our customers at no additional cost.

Questions about GMDs?  Just ask!  Give us a call at 800-531-7678 or send your inquiry to [email protected]

Written by Joan I. Chapa, MLS

Presentation on Data Remediation for Consortium

Written by Joan on February 19, 2016. Posted in Blog

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

ELUNA in Minneapolis

Written by Joan on April 21, 2015. Posted in Blog, General

More and more libraries are asking us to convert their legacy bibliographic data to RDA compliance.  Why do this?  Don’t AACR2 and RDA records play together nicely in the library catalog?  One library’s perspective will be presented at the upcoming ELUNA (Ex Libris Users of North America) Conference in Minneapolis.  Mark Sanford from William Paterson University Library, a long-time MARCIVE authorities processing customer will talk about his experience.

Where:  Marriott City Center Hotel in Minneapolis
Room: Deer Lake
Who:  Mark Sanford from William Paterson University
When:  Thursday, May 7
Time:  3:30 pm

MARCIVE will have a table in the Atrium outside of the Grand Portage Ballrooms during the conference, so stop by and see us!

Aren’t able to attend ELUNA this year?  Contact a Marketing Representative for a copy of the presentation and further information.

Joan Chapa, MLS

Why didn’t all my 260 fields get converted to 264 fields during RDA conversion?

Written by Joan on December 1, 2014. Posted in Blog

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.

However, we are sensitive to our customers’ individual needs and can force all 260 fields to 264 fields upon request.

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

Written by Joan Chapa, MLS

Revised Notification Schedule

Written by Joan on November 20, 2014. Posted in Blog

RDA Phase 3A changes to LC authority records is scheduled to happen between December 1-19, 2014. This is much earlier than the 2015 date announced earlier this year. See the announcement by LC at http://www.loc.gov/cds/notices/141023c.pdf

During the earlier phases, MARCIVE output weekly instead of monthly files so that the files sizes could be more easily accommodated by our customers. LC has said that during Phase 3A they anticipate that approximately 30,000 changes a day will be made. Not every change affects every library, but most libraries would receive significantly larger files. As with the earlier phases, we anticipate going to more frequent Notification output during the month of December until the distribution returns to normal. It is possible that this will result in two Notifications files in December, and two in January. We will not run Notification the last two weeks of December. Much of this proposed schedule depends on when LC actually begins the large distribution.

Please note that the increase in file sizes does not affect the cost of Notification!

As this is a holiday time for most of our libraries, we are extending the time period that the files will be retained on the FTP server. Files will be retained for 60 days. They will still need to be retrieved and loaded in the order created, but there will be more time to complete these tasks.

With the introduction of many new authority format fields we recommend that libraries consider changing their profile option if they only receive records with significant changes. While this option reduces the file size, it also prevents the library from receiving valuable updates which may be needed in future cataloging environments. Please contact Denise Thompson ([email protected]) if you want to change your profile to receive all changed records in Notification.

Written by Joan Chapa, MLS

Why Convert Legacy Data to RDA: Public Libraries Weigh In

Written by Joan on November 3, 2014. Posted in Blog

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

The GMD–why keep it?

Written by Joan on October 10, 2014. Posted in Blog

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

havequestion_LFT