Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-3174] Analyze Folijet support work for Inventory Bound-with feature (Data Import) Created: 09/Jul/21  Updated: 28/Dec/23

Status: Blocked
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: cataloging, data-import, epam-folijet
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by MODDATAIMP-530 Update a bound-with instance, holding... Open
is defined by MODDATAIMP-529 Check schema updates for Inventory ho... Closed
Relates
relates to UXPROD-1241 BE: Analytical records; bound with - ... Closed
relates to UXPROD-2855 FE: Display Bound with in the UI (Ins... Closed
relates to UXPROD-3080 Edit - first iteration. Analytical re... Closed
relates to UXPROD-3640 Edit and delete - second iteration. A... Closed
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Very Small (VS) < 1day
Back End Estimate: Very Small (VS) < 1day
Development Team: Folijet
PO Rank: 75
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem: Inventory implemented backend support for bound withs in UXPROD-1241 Closed (Juniper) and will work on UI support for View ( UXPROD-2855 Closed ) and possibly Edit ( UXPROD-3080 Closed ) in Kiwi. Corresponding changes in Data Import need to be discussed and documented, and if possible, completed in Kiwi

In scope

  • How this new Inventory functionality affects Data Import profiles and jobs

Out of scope
(But related): how does this new Inventory functionality affect Acquisitions and Data Export

Use case(s)

Q&A with Charlotte and Prokopovych (see comments on UXPROD-2855 Closed

  • If data import is creating an item record from an incoming MARC Bib, would it be expected to somehow link that item record to multiple instances? Answer: NOT Relevant (assume they will be manually linked?)
  • If data import is updating an item record from an incoming MARC Bib, I think it'll be OK, since the match would most likely be on Item HRID, UUID, or Barcode number Answer: YES - all good
  • Is there any change to the Instance or Item record schema to add/modify a field to indicate an Item record belongs to multiple instances? If so, we may need to update the Item or Instance field mapping screen Answer: No, there are no changes to the Item, HoldingsRecord or Instance schema in Inventory storage. The Item is related to multiple holdings records (and thus by extension to multiple Instances) through a new data structure in Inventory storage. (Do we need to do something to take the new data structure into account in DI field mapping profiles or in the data that is sent to Inventory during an import job?)
  • If data export is outputting Instance + Item data, would it need to take into account a new data element Answer: No, as per above comment
  • If orders are creating items, and/or receiving is updating items, would it somehow need to take into account that an item record is linked to multiple instances? Answer: If Orders is creating an Item, it will not (yet) be connected to multiple instances (unless Orders makes it so at this point). If receiving is updating an Item, that is a bound-with, it can do so as before.
  • More details from Niels Erik Gilvad Nielsen:
    • If, down the line, data import/export or Orders need to register a new Item as a bound-with or need to retrieve it with it’s bound-with parts, then these modules must know how to persist and retrieve that information in Inventory storage using the new bound-with-part API for example: https://s3.amazonaws.com/foliodocs/api/mod-inventory-storage/bound-with-part.html
    • For completeness: There are schema changes for bound-with in the business logic module, mod-inventory. In both the Instance and the Item schema there is a new derived, read-only field `isBoundWith`, indicating that records are bound-with, to assist the UI in displaying that fact. And when retrieving a Item by ID, the Item will contain a list (read-only so far) of the titles that are bound within it, again for the benefit of the UI.

Proposed solution/stories
TBD

  • Any changes to Item field mapping screen UI?
  • Any changes to Instance field mapping screen UI?
  • Any changes to the DI payload for Creating or Updating Instances?
  • Any changes to the DI payload for Creating or Updating Items?
  • Any changes needed in DI UI log info?

Links to additional info

Questions



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 13/Jul/21 ]

From the meeting on 13 July 2021 (link to the recording still pending):

  • Changes to records
    • Flag in the instance that shows in the UI that this instance has a relationship to a bound with item
    • Holdings: No UI change, but behind the scenes, connected to the Bound with entity in the business layer that links all the various holdings represented by 1 item
    • Item: UI shows that it represents a bound with up at the top, and at the bottom is a list of all the instances included in that 1 item; behind the scenes it is linked to that bound with entity
  • Jiras
    • BE work for the BW entity done in Juniper
    • UI work to surface the bound with info will be done in Kiwi
    • BE work to allow manual edits to the bound with Info is yet to be scheduled (won't be Kiwi)
  • For Folijet in Kiwi
    • 1 story or task to check the schema updates for holdings and items, may need adjustment
    • 1 story or task to send updates to an instance, holdings, and item associated with a bound with, to see if the updates do anything to break the bound with info (by staying silent about bound with)

cc: Kateryna Senchenko Taisiya Trunova

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