Inventory (UXPROD-785)

[UXPROD-3703] Create API endpoint to get the current maximum assigned HRID Created: 08/Jun/22  Updated: 18/Dec/23

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Theodor Tolstoy (One-Group.se) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: API, data-migration, epam-folijet, inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-785 Inventory In Progress
is defined by MODINVSTOR-921 Create API endpoint to get the curren... Closed
Release: Not Scheduled
Epic Link: Inventory
Development Team: Folijet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem:

Today, when we perform initial data migration from a Legacy system, we mint HRIDs for the inventory record types that have references in other records, like SRS records. 

When we have generated all the objects outside of FOLIO, and posted them, we then update the HRID settings in the tenant, so that any new record will be assigned an HRID that does not collide.

However, we have come across many scenarios when we (and the library) would benefit greatly if we could somehow get hold of the maximum assigned HRID for the various objects, and not tamper (=reset) the current HRID settings, but instead let our tools align with what is currently in FOLIO.

This would for example allow for inclusion of new libraries into a FOLIO tenant in a consortial scenario, and many more.

In scope

Out of scope

Use case(s)

Large additions to inventory, initial data migration, 

Proposed solution/stories

  1. Create an additional endpoint in /hrid-settings-storage that returns the current maximum hrid assigned in the database for all object types (instances, holdings items (authorities?)

 



 Comments   
Comment by Brooks Travis [ 08/Jun/22 ]

I'd like to jump in here and suggest we broaden the scope of this feature a bit to include APIs for:

  • Retrieving the current sequence value
  • Retrieving the next sequence value (without incrementing the actual sequence value)
  • Retrieving the next sequence value (and incrementing the actual sequence value)
  • Setting the current sequence value to a particular value
Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ]

Moved from Prokopovych backlog to Folijet Backlog cc: Ryan Taylor

See above comment from Brooks

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