E-Book Cataloging


(see also Workflow for E-books)

Policy:

We will use the single record approach to cataloging e-books. This means that whenever we own the same edition in print, we will add info about the online to the print record. This includes e-books purchased from NetLibrary. The only exceptions are the records loaded for consortially purchased netLibrary packages; these have separate records for online and for any print we may already own or subsequently purchase.

Background:

E-Books can be ordered from the vendors in packages or individually. If they are ordered individually the order is placed on the record where the link for the e-book goes. If they are ordered as a package, Aurora creates a SUPPRESSED provisional record, usually with the name of the package as the title, and opens an order for all individual titles to be paid in that record. Then, after the order is opened we get a file with MARC records and links for the individual titles.

We have worked with a few packages and we have decided to examine the records before we batch load the file into ALEPH. Then, after evaluating the records, we'll make the decision if they should be batched loaded or individually created and cataloged. We have found that in many cases, the MARC records we receive are vendor records and they lack information that is critical to maintain accuracy in our catalog.

Some of the issues we have come across in batch loading these files are:
  1. Duplicate records - we already had a print record in our system or duplicate records are sent for multi-vol sets.
  2. Mismatch between edition on record and edition in the link.
  3. Records missing OCLC number and lacking other fields.
  4. Records missing from the file.
*Note: only the batches of NetLibrary records from the Solinet consortial plan are to be loaded with the special VR "OWN" code (these are notified to Margarita and she loads them separately); all firm order e-books will be cataloged or loaded in the FI "OWN" code.