Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

There are 2 ways fo how the records can be generated in data-import:

...

    Create a new handler CreateMarcHoldingsEventHandler that handles the event DI_SRS_MARC_HOLDINGS_RECORD_CREATED.  The new handler should be written in the same principle as CreateInstanceEventHandler.

What the CreateMarcHoldingsEventHandler receives:

  • default mapping rules
  • SRS Holdings record
  • Instance HRID

What the CreateMarcHoldingsEventHandler does:
 - generates Holdings using the corresponding Processor from data-import-processing-core
 - retrieves Inventory Instance by the given HRID, takes instanceId from Instance and sets instanceId to generated Holdings record
 - saves Holdings record to the DB
 - throws DI_INVENTORY_HOLDINGS_CREATED_READY_FOR_POST_PROCESSING, prepare event payload for post-processing.

...

User stories

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDICORE-175
 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINV-483

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINV-486

...

Open questions

  • Clarify mapping for holdingsTypeId,
  • What changes on UI are needed? Changes on MappingProfile - Enable MARC_HOLDINGS record type, enable Holdings HRID field
  • (From Ann-Marie Breaux (Deactivated)) If a library only has MARC Holdings for some of their Inventory Holdings, and wants to use MARC Bib data to create/update some of the Inventory Holdings not controlled by MARC Holdings, how to we indicate that on the UI? One possibility - if the library selects incoming record = MARC Bib, then allow mapping for all of the Inventory Holdings fields. If the library selects incoming record = MARC Holdings, then grey out/disable the fields controlled by the default MARC Holdings-to-Inventory Holdings map.
  • (from Ann-Marie Breaux (Deactivated) ) If a library uses MARC Holdings, is it OK to grey out/disable the same fields for all libraries, or should that be responsive to which Inventory Holdings fields are controlled by the default map for a particular tenant? Maybe start with it being the same for all libraries, but a future story to make it responsive to the default map?

...