/
MLN2 eContent Cataloging

MLN2 eContent Cataloging

These guidelines are used for electronic content records kept in Sierra on MLN2. MLN1 uses a different process.

Table of Contents

Should I store my eContent record in Sierra or Sideload into Pika?

Most eContent collections that have MARC record sets are easily handled as a Pika sideload. See the Sideloading Pros & Cons documentation for other considerations. We recommend storing eContent collections represented by a single MARC record, such as Mango Languages, in the ILS.

It may be preferable to store eContent records in Sierra because the records need to be exported to another service, such as EDS. Although it is likely the other service also has sideloading ability and could get the resource directly as well. Check with them.

When you choose to store eContent in the ILS, the following guidelines need to be followed for the eContent to display correctly in Pika.

Top of page

Cataloging eContent records for Pika

Basic Handling

Pika expects MARC records for MLN2 libraries to have specific data points in order to display records as eContent with a corresponding access link. The most appropriate values are bolded.

Typically, the eContent source is generically set as eContent unless the access link in the 856|u matches a value in the Special eContent Source Handling described below.

This handling is active for both itemless bibs and bibs with items.

  • FORMAT/BCODE2 value

    • 3 - EBOOK

    • m - COMPUTER FILE

    • t - ONLINE LINK

    • u - CD-ROM/SOFTWARE

    • w - ONLINE DATABSE

  • MARC 856, subfield u

    • Access link to eContent

  • If the record is itemless, location is referenced from the locations subfield in the record tag 907|b

    • The 907|b is not added during the cataloging process, rather generated on export from Sierra

  • If the 907|b is empty or has value “multi” the 998|h (Locations) is referenced

Special Handling for specific location codes

  • MARC 856, subfield u

    • Access link to eContent

  • MARC 962, subfield u (unique to Carnegie Library for Local History)

    • Access link to eContent

Bibs with items with the following locations will always be handled as eContent :

  • laopa (Lafayette Online Photographs)

  • Starts with bc (Boulder Carnegie Library for Local History)

Special eContent Source Handling

If the URL in the ILS eContent record matches the following data points, the corresponding eContent source will be displayed :

  • URL contains “ebrary.com”

    • eContent source displays as eBrary

  • URL contains “gutenberg.org”

    • eContent source displays as Project Gutenberg

  • URL contains “safaribooksonline.com”

    • eContent source displays as Safari Books

  • URL contains “uniteforliteracy.com”

    • eContent source displays as Unite for Literacy

  • URL contains “galegroup.com”

    • eContent source displays as Gale

Please submit a service request in the Marmot Help Desk if an additional source should be added to the handling.

Top of page

Importing MARC Records into Sierra

  • MARC Records should follow the Provider-Neutral (P-N) model outlined in the RDA Provider-Neutral E-Resource MARC Record Guide.

  • Options:

    • A P-N record may already exist in Sierra which item records can be attached to.

    • A P-N record can be brought in from OCLC or SkyRiver and be attached to.

    • A record for another format can be copied and upgraded to a P-N record by following the P-N guide.

    • Original cataloging can be done following the P-N Guide.

    • Metadata in MARC record format received from Publishers can be uploaded to Sierra.

    • Metadata in ONIX or other formats received from Publishers can be converted to MARC using MARC Edit and uploaded to Sierra.

ILS eContent item records should be attached to separate bibs representative of the eContent. ILS eContent items should not be attached to bibs for physical content.

Top of page

Related Documentation