| Allow users create orders and order lines based on order data supplied in MARC bibliographic records | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | Closed |
|---|
|
|
|
| Allow users to create field mapping profiles, action profiles, and job profiles to support MARC-based order data | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
|
|
| Allow users to create, but not update, POs/POLs via DI | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. No need to consider updating unless significant use case identified in the future |
| Data import match profiles not needed for Order records | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. Since DI is only creating orders, use case for matching and updating an order does not apply. Use case for matching and then not creating an order: not common, and could only use Product ID or Vendor Ref ID for matching. Revisit if additional use cases identified in the future |
| Use for one-time orders (physical, electronic, or both). Do not use for ongoing or package orders | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. Revisit if any significant use case identified for Ongoing and/or Package orders |
| Show all the PO/POL fields in the Field mapping profile, but suppress the PO/POL fields and values that are only used for ongoing or package orders. | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. |
| Allow POs to be created as Pending or Open | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. Use cases for both identified. Will gather that info via a field at the top of the field mapping profile |
| Allow override to the tenant's default POL limit setting | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. Also, value may need to vary from one vendor to another or from one type of purchases to another. Will gather that info via a field at the top of the field mapping profile |
| User should have an option to auto-receive | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Yellow |
|---|
| title | Deferred |
|---|
|
| Confirmed by Acq SIG SMEs. Will gather that info via a field at the top of the field mapping profile. If PO is created as Pending, and then opened manually, can this requirement be included? Or only possible if the PO is created as Open? |
| Add mapping syntax for TODAY + x days | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Yellow |
|---|
| title | Deferred |
|---|
|
| Would be useful for fields like Activation date, Receipt date - but per DI SMEs, not important for now. Consider for refinement feature |
| Honor the Acquisitions unit settings | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. If import user invokes a job profile that creates POs, that user must be a member of the acq unit assigned by the field mapping profile, or the acq unit settings must allow non-members to create POs. This acq unit logic is already in place for Invoices. |
| Have a way to create POLs for multiple copies with different locations | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. talk with devs about whether the data needs to be configured in a certain way in the MARC file, e.g. - Maybe something like a repeatable 9xx field that has
- $a location $b quantity $c fund $d expense class (or $c fund:expense class)
|
| Have a way to create a POL that assigns more than 1 fund and/or expense class to cover the cost | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. See above. Include a way to assign the fund/expense class by % or amount. |
| Be able to accept fund and expense class whether they are supplied in separate MARC subfields, or in 1 MARC subfield, separated by a colon | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. For example (Fund code = History, Expense class = Electronic) - 980 $a History $b Electronic
- 980 $a History:Electronic
- Combined fund:expense class
| Status |
|---|
| subtle | true |
|---|
| colour | Yellow |
|---|
| title | deferred |
|---|
|
since no library is using yet; aim to include in refinement feature
|
| If Orders app is creating Inventory records based on instruction from Data Import (or based on opening orders), follow the tenant's setting for Disable instance matching | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs |
| Instances/Holdings/Items related to the created POL should display proper links in the Acquisition and Receiving history accordions, regardless of whether the POL or the Inventory records were created first | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Confirmed by Acq SIG SMEs. Works now when order is opened and Inventory is created by the orders app. Does not work if Inventory records are associated with the POL after it has been opened. Needs further discussion with devs |
| If a library wants to import a MARC Bib file to create orders, but does NOT want to create any Inventory records, will there be any problem? | | Status |
|---|
| subtle | true |
|---|
| colour | Yellow |
|---|
| title | deferred |
|---|
|
| May just require testing of a job profile with Create orders action, but no Create Instance action. |
| If a library has an Order setting that POs must be approved before opening, will that setting always apply to orders created by Data Import? If yes, need an option to always create the orders as approved, or always create as pending? | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Discussed in Acq SIG 28 June 2022; no libraries with that setting. A-M asked on Acq Slack channel. If field mapping has approved selected, the user importing the file must have permission to approve orders. |
| If a library has an Order setting that allows for the FOLIO PO to be edited, will that setting apply to orders created by Data Import? | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Discussed in Acq SIG 28 June 2022; no libraries with that setting. A-M asked on Acq Slack channel. Does not seem to be needed currently |
| Will libraries want to map PO numbers from the incoming MARC records? | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Discussed in Acq SIG 28 June 2022. No use case identified (yet) - wait and see if any identified before definite "No", since this decision would require coordination with Settings for editing PO numbers and max POLs per PO. If PO needs to not be mappable, easiest to disallow mapping the field completely on the field mapping screen (like HRID). A-M to ask on Acq Slack channel. |
| If the PO number is mapped from a MARC field (e.g. 950$p) and the PO varies from one MARC Bib to another, what should FOLIO do? | | Status |
|---|
| |
|---|
| subtle | true |
|---|
| colour | Green |
|---|
| title | closed |
|---|
|
| Wait until above question is resolved. Will not be mapped, so does not need to be dealt with |