Inventory (UXPROD-785)

[UXPROD-2268] Move holdings and/or items - when the change is triggered by external source Created: 14/Feb/20  Updated: 16/Sep/21  Resolved: 05/Nov/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: GBV, metadatamanagement, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UIIN-1293 Display Instance.matchKey if present ... Closed
is defined by MODINVSTOR-587 Instance match key for union catalog ... Closed
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Niels Erik Nielsen
Front End Estimator: Niels Erik Nielsen
Back End Estimate: XL < 15 days
Back End Estimator: Niels Erik Nielsen
Development Team: Thor
PO Rank: 99
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R1
Rank: Grand Valley (Full Sum 2021): R1
Rank: TAMU (MVP Jan 2021): R4

 Description   

Goal: Transfer holdings from one instance to another when the change is triggered outside of FOLIO. This use case can be relevant with non-SRS implementation, e.g. like Chalmers and GBV.

Task:

  1. gather use cases for:
    • Which external sources can trigger a change of holdings and/or item
    • When are changes of holdings and/or items being trigged by an external source
    • How do FOLIO/Inventory receive input on changes triggered by an external source
    • How do FOLIO\/Inventory implement the changes (which automatic processes and/or manual processes? Which apps are involved in this chain: Data Import, Orders etc.

Uses case development for OCLC CBS union catalogues (e.g. GBV, hebis, SWB)

  1. In an external system, a holdings and/or item record is moved from one bib record to another.
  • The process has to be mirrored in Inventory, so that the new relationships are established (Item -> Holdings -> Instance).

mod-inventory-update module (NEW FOLIO module)

  • Definition of Update: update & insert (includes deletion and move)
  • FOLIO/Inventory would receive input on changes triggered by an external source via this new module
  • There are no changes to Folio Inventory required and nothing has to be implemented. The new module could be considered part of Inventory.

Documentation:



 Comments   
Comment by Charlotte Whitt [ 06/Oct/20 ]

Niels Erik Nielsen
Status for writing unit tests:

  1. We're ready to start writing tests for the upsert API.
  2. We have moved mod-inventory-update from OLE's github to FOLIO's github https://github.com/folio-org/mod-inventory-update, and rolled it into the continuous integration framework in Jenkins, for example to have Jenkins run the unit tests and have the coverage measured by SonarQube.
  3. We also worked to complete the API documentation at https://s3.amazonaws.com/foliodocs/api/mod-inventory-update/inventory-update.html# since understanding the required input and expected output is obviously useful for writing tests.

Notes:

  1. There are some tests for the to-be-deprecated API /instance-storage-match/instances and I've just started writing the first test for /shared-inventory-upsert-matchkey
  2. The API intended for use by GBV, /inventory-upsert-hrid, has no tests yet.
  3. There's a simple FakeInventoryStorage mock-up for the tests - it only handles instances, so things like holdings, items and locations need to be added.
Generated at Fri Feb 09 00:22:33 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.