...
- Use the Inventory interaction setting from the POL
- Use the Data import job profile matching and sequencing
- Allow the user to choose (at the profile level or POL level?)
Job needs to create
- SRS MARC Bib
- Source = MARC Instance
- Holdings (as many as there are locations)
- If created by Order app, can create multi, with POL link and with limited details
- If created by DI app, can create single (for now), multi in the future, but with more details
- Could maybe be added by a secondary Update job profile
- Item (as many as there are copies)
- If created by Order app, can create multi, with POL link and with limited details
- If created by DI app, can create single (for now), multi in the future, but with more details
- Could maybe be added by a secondary Update job profile
Possible Nolana Job profile sequence (Data Import)
- Create Instance (source = MARC)
- Create Orders (with data from MARC Bib, Order data in MARC Bib, Order field mapping profile)
- DI would need to pass the Instance UUID as part of the Create orders info
- What happens if order is created as Pending?
- How to create source = MARC
- Open the order
- Which creates Holdings and Item, and provides the POL link
Second Nolana Data Import job
- Match on ??? (to find newly-created Holdings and Item)
- Action: Update holdings - field mapping profile; only worry about 1 holdings for now
- Action: Update item - field mapping profile; only worry about holdings for now
There are pros and cons to eachBackground:Orders app and DI app creating Holdings and Items
Per Olamide, keep as much business logic in the other apps (Inventory, Orders, Invoices) as possible, instead of Data Import having to understand and replicate that logic
Background:
- Preference is to use the Orders engine to create the Inventory records
- Orders can be created as Pending or Open via Data Import
- Changing an Order’s status from Pending to Open triggers:
- Creation of encumbrances (if fund and price supplied in POL)
- Creation of receiving pieces (depending on receiving setting in POL)
- Creation of Instance, Holdings, Items (depending on Inventory setting in POL)
- Currently orders feed all data to Inventory to create Instance, Holdings, Item
- The Order app’s Inventory matching is not as flexible as Data Import’s and is all-or-nothing, depending on the setting
- POLs are only linked with Instances, Holdings, Items if those Inventory records are created by opening orders
- Can those POL links be created/changed manually on Inventory records
- An Inventory record cannot be matched/updated via POL/VRN unless the Inventory record is linked to the POL; this is a very important workflow for libraries
- The data on an incoming MARC Bib record and in a data import profile can create richer Inventory records than the Orders app can
- Data import can only create a single holdings and item via an imported MARC Bib at this time, though that will change in Orchid or Poppy; Orders app can create multiple holdings and items
...