Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1) (UXPROD-4049)

[UXPROD-4136] Managing unique identifiers in circulation records Created: 17/Mar/23  Updated: 30/Nov/23  Resolved: 09/May/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Anne Ekblad
Resolution: Won't Do Votes: 0
Labels: ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File New Request Form - 7-7-2023 - request types available.PNG    
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem: Circulation 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 Request and User records should be unique within a member vs what should be unique across members.

Uniqueness Not Required for Circulation

The the below Identifiers fall into the category of Uniqueness Not Required for Circulation for the following reason: Identification of ReShare DCB Circulation will be handled within the local library systems' instances of FOLIO. And, within the local library systems' instances of FOLIO, the below Identifiers are unique. Transactions across lending and borrowing library tenants include identifiers like patron UUID (userId), patron group, patron library code, patron pickup location, material title, author, call number, volume designation, item UUID (itemId), item barcode and material type.

User Record related

  • Barcode. The barcode of the User.
  • Username. The username of the User.
  • External system ID. The external system ID for the User. The field is auto-populated if it is included in source data provided by an external system.
  • Folio number. A system-generated number for the User Record.

Possible Request related

  • Item barcode
  • Instance HRID. Human readable identifier, also called the eye readable ID.
  • Requestor barcode - User requesting materials (User barcode)
  • Service point. (e.g., multiple institutions with Circ 1 as Pickup Service Point default)

Fees/fines considerations

Links to additional info

Managing Unique Identifiers Across Consortia Members - Shared wiki https://folio-org.atlassian.net/wiki/display/ACQ/Managing+Unique+Identifiers+Across+Consortia+Members

Questions:

 



 Comments   
Comment by Anne Ekblad [ 09/May/23 ]

Based on development plans, there is no work needed.

Generated at Fri Feb 09 00:37:33 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.