Focus Group for drafting requirements:
- DI PO: Ann-Marie Breaux
- Acq PO: Dennis Bridges
- Cornell: Jenn Colt
- 5C: Jennifer Eustis, Sara Colglazier
- Michigan State: Kim Wiljanen, Lisa Smith
5/20 May 2022: A-M, Kim, Sara, Jenn, DennisSchedule next mtg Weds 5/25 3-5 pm
25 May 2022:
Prep Jira:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
- What are your library’s use cases for creating orders from MARC Bib records?
- Approval plans (aka All happens at point of receipt/invoicing)
- Create individual orders for each title, along with Bib/Instances, Holdings, maybe Items - all at the same time
- DDA automatic eBook purchases - may not be creating items for these
- Firm orders (aka Point of order and Point of receipt/invoicing)
- 2 styles, depending on where the user presses the Order button:
- Order in vendor system: usually have to create a copy of that order in FOLIO (either via API, MARC data, or manually); usually the subsequent matching to update Inventory and link Invoices to PO Lines is done via vendor reference number, since the Vendor will not have the FOLIO POL (unless it is returned to the vendor after order creation in FOLIO)
- Order in FOLIO: Order is sent to the vendor in various ways; usually the subsequent matching to update Inventory and link Invoices to PO Lines is done via POL, although it may be via VRN if the library stored the VRN in the POL they created in FOLIO
- Firm orders that are not API - create individual orders/temp Inventory Instances, Holdings, Items, then later finalize Bib/Instance, Holdings, Item
- Lehigh tool workflow from Cornell (which uses MARC Bib data along with the the order API and Data Import)
- Kim: Get records from OCLC and download to local system to create an Instance and Order (ca. 80-90 records per session), but not holdings or item. Holdings and item created when the materials are processed, which may only be a couple days after the orders were created. (EastView for Russian materials, MARCnow does cataloging and adds to OCLC; library gets records from OCLC)
- 2 styles, depending on where the user presses the Order button:
- Multi-line POs instead of Single-line POs (Cornell and Mich State)
- Mich State likes 1 POL per PO for firm orders, but approvals are multi-line; settings are 999, which works for AP, but not for firm orders
- Approval plans (aka All happens at point of receipt/invoicing)
- Walk through one library’s details of the top use case (Approvals)
- Approval
Approvals: Cornell Aux Amateurs
- Separate MARC file for each invoice; POL limit setting is 999
- Holdings, Item, Invoice data in 9xx fields
- Create the order as Open,
- Be sure that the VRN is mapped into the POL
- Inventory interaction for the POLThen when : Create Instance, Holdings, Item
- When the order is opened,
- Orders app creates brief Instance, Holdings, Item
- Creates expected receiving pieces, with synchronized receiving
- Receiving pieces are created, but
- Cornell does minimal receiving for approvals; just click received and
- do not include barcode number or other item data
- Holdings and Item will be updated separately via Data Import
- Library could also default to receipt not required, but
- Lose some visual clues in that case, that the POL was fully received (which Michigan State observed)
- Receiving Piece would not be linked to the holdings or item and would not populate the Receiving history accordion
- Receiving pieces are created, but
- Encumbers the funds
- Lehigh app triggers Single record import that overlays
- Overlays each of the Instances
- Changes Source to MARC
- Updates the Holdings and Item
- Import stops if Instance Source = MARC already, so Library can review
- If no Lehigh app, and there is a file of 8 MARC Bibs
- Import the MARC file
- Matching on VRN for Instance, Holdings, Item
- Updating Instance, Holdings, Item based on the update field mapping profiles
- Approval Q&A:
- Template needed? Probably not, and since DI field mapping profile acts similarly; invoking a template might be overly-complicated
- Do libraries add extra lines to the approval POL manually? Usually no
- Allow the POs to be created as Pending or Open, since some libraries may want to review before opening them
- Also make sure that Receiving option is in the Field mapping profile, e.g. Receipt not required
- Could orders be created and automatically transition to received, especially if DI is populating the details like barcode into the Item record? Does the Orders app have to create brief Instance, Holdings, Item, or could DI do it? If DI does it, is there a way to link the POL to the Inventory records? A-M and Dennis discuss
- Approval
Firm orders
Placed outside of FOLIO and then need to be copied into FOLIO - can't count on the vendor having FOLIO POL
- Ways these could get into FOLIO:
- API
- Lehigh app (what is the new name)
- MARC Bibs with order data (after this dev work is done)
- Manual (after order is sent to vendor by e-mail, mail, or placed on their site, but if there is no automated way to get the data back into FOLIO)
- Sara
- Point of order
- Place orders on vendor site
- Get daily MARC file (from vendor, with OCLC numbers and Vendor reference number)
- Pick up the file (FTP)
- Get a daily e-mail that the file was picked up and loaded
- Create Imported MARC file creates bib, item, order in current system (do does not create the holdings yet - this is in their former system, not FOLIO)
- Order created in open status
- Point of receipt
- All matches by Vendor Ref Number (VRN)
- MARC file to update the bib
- Manual receiving (could FOLIO automate?)
- Manual create holdings and update item (could FOLIO automate?)
- Get EDIFACT invoice
- Point of order
- Ways these could get into FOLIO:
Placed in FOLIO and sent to the vendor - vendor would have the POL
- How?
- May be creating pre-orders from MARC Bibs, and then finalize and send to vendor (after this dev work is done)
- Manually key
- Jenn/Cornell
- Point of order - Cornell uses external selection tool to gather requests and recommendations from selectors and vendors
- Selectors may decide on candidate titles, which triggers MARC to be sent
- Vendor sends MARC Bibs for candidate titles
- Other records come from other vendors, and may be selected at this point - all is external to FOLIO
- Automation to check the file, maybe change vendor, assign funds
- Produces a MARC record with order data
- Weird ones go into review file
- Then pre-order MARC file is loaded into FOLIO - using the Lehigh app - all settings configured in the tool, so not using order templates
- Creates the order as Open
- When the order is opened, does its regular process: create the receiving pieces, Inventory instances, holdings, items
- Then run a data import to create SRS MARC, change Instance source, update the holdings with call number ON ORDER, no changes to item
- Only for 1 vendor automated; rest are manual
- Export the order info in csv and send to vendor
- Vendor creates orders, with the FOLIO POL
- Point of receipt
- Get a MARC file from the vendor
- Add the Instance HRID into the MARC, and then use that for matching
- Use "On Order" in the holdings call number field as a static match to update the correct holdings (or holdings HRID begins 1)
- Use "On Order" or "In process" item status to find the correct item and update it
- Updates the Instance, Holdings, Item (call number, location, barcode)
- EDI invoicing, probably using FOLIO POL for matchpoint
- Point of order - Cornell uses external selection tool to gather requests and recommendations from selectors and vendors
- How?
...
- /VRN and updating related Instance/Holdings/Item (delivered in Morning Glory)
- Matching by POL add link
- Matching by VRN add link
Possible Order field mapping UI
- At top
- Use template or not
- Use settings POL max or not
- Create orders as Pending or Open
- Anything about auto-receive?
- Then all the template data
Things we don't want to forget
...
/Misc Info and Q&A
- 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?
- 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?
- 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?
- 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?
- How does this dovetail with the Lehigh app - does this replace it or coexist with it?
- 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 Do is MARC Order 9xx data?
- 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)