Managing Unique Identifiers Across Consortia Members

Problem: Acquisitions records contain a number of human readable IDs that are expected to be unique within a given library. Some of these identifiers may also need to be unique across consortia. FOLIO needs to identify what identifiers in the Instance, Holding and Item should be unique within a member vs what should be unique across members. In order to develop this feature, we need to identify which unique IDs must be unique across the entire consortium.

See https://folio-org.atlassian.net/browse/UXPROD-4137 https://folio-org.atlassian.net/browse/UXPROD-4136

Use Cases

Case 1

• Identifier must (or should) be globally unique - requires validation against all tenants

• All tenants share "ownership" of this identifier

• Requires error handling and/or manual tenant assignment in the event of duplicates

Case 2

• Identifier must be accessible and usable by all tenants, but with localization allowed

• All tenants use this identifier, but this identifier can be tailored per tenant

• Uniqueness can be achieved via prefix. suffix or other internal handling

Case 3

• Identifier must be visible to all or specific tenants, but editable only by the owning tenant

• Uniqueness can be achieved via prefix, suffix or other internal handling

Case 4

• Does not need to be unique

• Disambiguation options

Processes Potentially Affected

General

• Staff/user management

• If another record type's number is stored in a given app or record, how does that affect the storing app/record if the owning app/record changes the number or number structure, e.g.

  • Inventory Instance doesn't know which SRS MARC ID it's related to, but SRS MARC record knows which Instance UUID it's related to

    • Inventory Instance links to the SRS MARC and allows for quickMARC lookup/edit/update SRS MARC/update Instance, based on that relationship

  • Inventory Instance/Holdings/Items do not know which POL(s) they are related to, but each POL knows every Instance/Holdings/Item related to it

    • Inventory displays POL info in the Instance/Holdings/Item

Circulation

• CI/CO

• Requests

• Loans

• Fines/Fees

• Users

Acquisitions

• Collaborative collection development (view-only)

• Joint orders (possibly - may be out of scope. Potentially impacts single-tenant, multi-acquisition unit sites more.)

Cataloging/Inventory

• Close association between Instance HRID and SRS

Data Import

Most important matchpoints for Data Import:

• SRS MARC Bib: 001, 010, 035, 9xx fields, 999 ff

• SRS MARC Authority: 001, 010

• Inventory Instance: HRID, UUID, OCLC number, LCCN, Other local ID, POL, VRN

• Inventory Holdings: HRID, UUID, Perm loc, URI, POL, VRN

• Inventory Item: HRID, UUID, Barcode, POL, VRN

Proposed Workflow

Questions