The ReShare Shared Index brings together bibliographic, holding, and item metadata from a consortium to support discovery and fulfillment processes.
Record structure
The Shared Index is built using the FOLIO Inventory app, which was designed to provide generic storage for bibliographic information from a variety sources, presented in a uniform, abstracted form for management of the collection regardless of the format or content rules used to describe a resource.
The Shared Index uses’s Inventory’s default record structure, which includes three types of records.
Instance records are similar to bibliographic records, but with a simplified set of fields. They describe a global version of a particular resource, and are generally scoped to the edition-level. In the shared index each, instance record represents a bibliographic resource that is held by at least one member of
Holding records describe a particular institution’s unique holding of an instance, including location and lending policies. Holdings may represent a single item, a multi-volume set of items, or a serial publication.
Item records describe each individual copy or piece of a holding that is owned by an institution Each item record typically represents a single physical object identified by a barcode.
Important data for ReShare
This documentation will not attempt to describe every field on a shared index record, much of which is standard bibliographic data that should be familiar to most library staff. Instead, it will highlight the fields that play a role in ReShare’s processes.
Instance fields
Matchkey
A matchkey is created for each record upon ingest. The matchkey uses portions of the title, author, publisher, and other MARC fields to recreate a unique key for each record. Records with the same matchkey are associated with the same Shared Index Instance record, and a unique holdings record is created for each library that contributes a copy of the record.
The matchkey is displayed on each instance record for troubleshooting purposes. If you see errors in a matchkey that are causing false positives or false negatives, these errors must be corrected in the source data. Matches cannot be manipulated in the shared index itself.
Note that at this time the matchkey is stored in the “index title” field. This is a temporary solution. ReShare plans to add a dedicated matchkey field and contribute this code back to the main branch of the FOLIO code.
Resource ID
Each instance record can contain multiple resource IDs. Each ID is a key-value pair that includes an identifier type and the identifier itself. This field can be used for standard identifiers like ISSNs, ISBNs, OCLC numbers, etc.
In the ReShare context, this field is used to store the unique identifier of each bib record that is associated with the instance. This generally corresponds to the 001 of the original record, but may vary by source system. Each ReShare identifier will have a type that matches the ReShare symbol of the contributing library.
These resource IDs are used by ReShare’s fulfillment process. Once a supplier is assigned, ReShare will use that institution’s resource identifier to perform a real-time availability check using Z39.50 and automatically respond to the request.
Holdings fields
The holding record itself is important for discovery and fulfillment. In
Holdings location
ILL policy