...
- All 3 Inventory record types linked to POL as of Kiwi, but can only see the POLs in holdings; Lotus: can see the POL links on all 3 record types
- Be able to assign a template as part of Order field mapping profile or no? Still TBD
- POL maximum setting OK to follow? Maybe NO, if library does multi-line for APs and single-line for FOs or vice versa; have a way to override the default in the Order field mapping profile?
- If set it as part of the DI profile, then will have problems if library tries to unopen/reopen the order
- Can we confirm that things done manually happen the same way when they are done mechanically?
- Work through scenarios where multiple libraries share the same instance, but separate holdings and items
- Does Inventory creation happen via Orders app (Instances would be Source = FOLIO) or Data Import app (Instances would be Source = MARC)? If DI, can we trigger POL links to be created?
- Via Opening Orders
- Order generates automatically if there's not already a reference in the POL
- Will connect to existing instance, if matches on Product ID
- May or may not match to an existing holdings
- If no Holdings ID in the POL (has location ID only), it creates a new holdings
- If Holdings ID in the POL, it matches to existing holdings (but the POL has to know about the holdings before the PO is opened)
- Always creates a new item
- During receiving, can correct the linkage of the item from an incorrect or duplicate holdings to the correct one, and delete the holdings that no longer has an item
- Approvals doesn't know POL, but knows VRN
- Order generates automatically if there's not already a reference in the POL
- Via Data Import
- Hard to get the proper links in place
- Via Opening Orders
- What happens if vendor cannot provide the POL or VRN in the MARC Bib, or the OCLC number/ISBN is not a good match
- Could orders be created and automatically transition to received, especially if DI is populating the details like barcode into the Item record?
- Should Inventory be created first, and then the POLs? Or vice versa
- Receiving app? Does DI need to create pieces? Not if the orders app does its work first
- Only 1 holdings/1 item can be updated by DI right now
targeted for OrchidJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2741
- Fund and Expense class - do we need special field mapping syntax to split if they come from the vendor as 1 value?
- If library uses 1 order location, and then change to a different permanent location - all is fine as long as the holdings is linked to the POL
- How does this dovetail with the Lehigh app - does this replace it or coexist with it?
- Would a library ever want to create POLs from the incoming MARC, but not want to create Instances at all? (similar to EDIFACT invoices creating invoices but then not being linked to any Inventory record)
- What happens with POL links to holdings/items before the POL in holdings was implemented? Are they there retroactively? Is there a script that the library can run to identify them and populate them?
- Ongoing orders - how necessary or not is MARC Order 9xx data?
- What about PO/POL notes (using the notes app) - support import for that data or no?
- For POs/POLs, do we need update, or just create?
- If only create, would match profile ever be needed? (Match allows you to find an existing record and update it OR determine there is no existing record and create it)