Skip to main content
Support - EBSCO Help

MARC Data Export Checklist for EBSCO Custom Catalog

To ensure that you have the best experience possible with your EBSCO Discovery Service (EDS) custom catalog database and to help us create your catalog in a timely manner, we encourage you to review the items listed below before delivering your catalog data to EBSCO.

The following metadata must be included your export:

Note: EBSCO does not currently accept holdings data in two separate files (i.e. a bibliographic record file and a holdings record file). The data must be consolidated into one file.

  1. A unique identifier in each record. (This is required.)
  2. Holdings data (also known as item data) integrated within the bibliographic record or in the MFHD (holdings record). This may include location codes, call numbers, other copy information, etc.
  3. URLs for e-resource content. Usually this is exported in the 856 field.

If you need to update your records to meet these requirements, we recommend using MarcEdit, a free and complete metadata editing suite.  To download and use MarcEdit, please visit the MarcEdit website

Data Format and Character Encoding

Example of a record in machine-readable format:

00619nam 2200157 a 4500001001600000008004100016100003600057245015300093260000900246599002200255599002100277907003500298933001800333998004600351945006400397 110989862155136 1 ¬aFisher, Michael Herbert,d1950- 4¬aThe Travels of Dean Mahomet: An Eighteenth-Century Journey through India / cEdited with an introduction and biographical essay by Michael H. Fisher a1997 aERM Coverage Load aOnline full-text a.b18886346b07-08-11c09-01-10 a.b18886346b- amcaonb - - cmdze-

  • Data format: Records must be in machine-readable format in order for EBSCO to load your records. Records cannot be loaded if they are formatted or human-readable in any way.
  • Encoding: The custom catalog currently supports record data encoded in UTF-8, MARC-8, and Windows Code Page. If you are not able to export in any of these formats, please let your DSC or Catalog Specialist know which encoding type your data uses.

    NOTE: We only support one encoding type at a time per catalog. Should you wish to start sending in data in a new data encoding type, please upload a new Full data set in your new encoding type to FTP, and contact

    Example of a catalog Bibliographic MARC record (human readable):
    Please note that your data may differ from the example below depending on your ILS vendor or cataloging method.

    =LDR 01323cam 22003498a 4500 (record leader)
    =001 000001 (unique identifier)
    =008 890317s1989dcumcfa001�beng (needed to load date and language information)
    =100 1$aAuthor
    =245 10$aTitle [other metadata fields…]
    =945 $lmain$aSL546 E1 R54 2000$i37329736826 (subfield $l contains location code, $a contains call number, $i contains barcode)


Disponible en español, haga clic aquí.