Option 3

Aspects of the proposal

1. SRM jobs for reporting
   1. Motivation: The existing reporting (e.g. data-import server and UI) can be leveraged  - rejected on meeting with PO 20 Oct 2022 , as there should be separate page
2. Using of mod-inventory topic instead of mod-inventory-storage topic - EST DIFF TBD Pavlo Smahin  UPD: needs spike to understand the effort. Considered to have it in Phase 2/3 
   1. Motivation: Avoid reverse mapping
3. Use existing bib records topic in mod-inventory - EST DIFF TBD Pavlo Smahin  UPD: needs spike to understand the effort. Considered to have it in Phase 2/3
   1.  Motivation: Avoid duplication of code in mod-inventory

Implied Changes per module

• mod-entities-links (1 sprint) 
  • consuming and processing authority messages coming from mod-inventory 
  • preparing and send messages to mod-srs
• mod-srs
  • consume and process messages from mod-entities-links
  • fetch job profile, but it's configured for bib-instance update. how to get mapping rules for marc-bib if profile is for marc-authority? (TBD - spike -0.5 sprint) + 1-2 sprints
  • prepare and send message to inventory, create some stubs in the payload to make it possible for mod-inventory to correct consume and process the message  - 1 sprint
• Reporting mechanism (TBD - spike - 0.5 sprint)
  • unclear what modifications are needed to meet the requirements (1-2 sprints)
• mod-quickMarc
  • rewrite to data-import. MARC-to-MARC Holdings update should be implemented (2 sprints)

Pros

• Mod-quick-marc is supposed to be migrated to data-import anyway
• Less complicated logic in inventory 
• The reporting works on the mod-inventory level