Generated MARC Files

Use the GET /v6/bibs/marc operation to generate a binary data file of MARC records for a specified list or range of bibs. This file returns all MARC data from the bib record as well as related fields from attached records.

With the mapping parameter, you can specify the suffix that identifies the b2mtab export mapping file to use for file generation. If this parameter is blank, the system uses the default mapping file, which has no suffix. The mapping file defines the correspondence between Innovative field group tags and MARC tags. See MARC Records in the Sierra WebHelp for more information on the relationship between Innovative field group tags and MARC data.

The GET /v6/bibs/marc operation returns a MarcSummary object. You must use the GET /v6/bibs/marc/files/{id} operation to retrieve the generated file.

The MarcSummary object includes the following properties:

file

string

A link to the generated binary MARC data file.

Example:

"file": "https://example-library.edu/iii/sierra-api/v6/bibs/marc/files/724891443049039121"

inputRecords

integer

Specifies the number of bibs processed.

Example:

"inputRecords": 12

deletedRecords

integer

The number of bibs processed that were in a deleted state. (Returned only when applicable.)

Example:

"deletedRecords": 2

outputRecords

integer

The number of bibs written to the MARC data file.

Example:

"outputRecords": 10

errors

integer

The number of errors that occured during the MARC data file generation.

Example:

"errors": 0

The preceding list order reflects the sequence in which the data returns.

The following is a full MarcSummary object example:

{
  "file": "https://example-library.edu/iii/sierra-api/v6/bibs/marc/files/724891443049352823",
  "inputRecords": 2,
  "deletedRecords": 1,
  "outputRecords": 1,
  "errors": 0
}