How to handle the POL limit variation (in the field mapping profile, users can select to use the existing default or override to a number higher or lower than the default) | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
|
|
If DI only allows creation of one-time, non-package orders, will there be any problems if we remove all the non-one-time, non-package data elements from the field mapping screen? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
|
|
We want to use the existing Orders logic as much as possible, but we also want Instance/Holdings/Item linked with correct POL even when created before the POL. | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| How much extra logic would be needed? |
Return an error to DI log if the user does not have permission to create an order for the acq unit specified in the PO | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| Already in place for invoices. Can we reuse that work? |
If vendor supplies order date in YYYYMMDD format, can we convert it to FOLIO YYYY-MM-DD default format? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
|
|
Would we be able to support other order date formats? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
|
|
Test handling of multiple copies for multiple locations in the same POL; how can DI understand and parse properly? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
| POST-NOLANA | MARC field mapping syntax expansion required? Aim for repeatable 9xx field that has $a location code $b quantity maybe $c fund $d expense class? |
For prices, FOLIO always wants an explicit decimal (e.g. 25.15, not 2516, correct?) | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| Question for Thunderjet |
With invoices, data import does not try to correlate the expense classes allowed by particular funds (just display all the expense classes from Settings in a dropdown list). Should we refine that for Orders? How difficult would it be? | Status |
---|
subtle | true |
---|
colour | Green |
---|
title | CLOSED |
---|
|
| Per SMEs. no need to refine, at least to start with - show all funds and all expense classes in each dropdown. |
|
Would Folijet need to take the receiving app into account? What happens if the Inventory records are created before the Order records, and not triggered by the POL's Inventory setting - would that be an issue? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| Question for Dennis/Thunderjet |
If order is created as Pending, but Instance/Holdings/Item has already been created by DI, what happens when the order is opened manually? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| SMEs want the Instance/Holdings/Item to be linked to the appropriate POL on the PO that was manually opened |
If library wants no Inventory created, can job profile be set up to import MARC Bibs, but only create orders? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| May just take some testing |
From the SMEs: Can we assume that actions taken by the system are being done the same way as actions done by a user (except faster, and without any confirmation modals)? | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
|
|
Specific PO/POL data elements | Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
|
| Question for Thunderjet |
| Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
| Is there an endpoint where DI could do a lookup based on the vendor name or code? (an exact match on one or the other) | Question for Thunderjet |
| Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
| What data should be supplied - user who runs the import job? | Question for Thunderjet SN: Yes, correct, active signed user. It is set automatically by RMB when Verticle receives request. So it is populated by server, should not be populated by the client. Example of metadata payload when creating order with populated by RMB data. Image Added |
| Status |
---|
subtle | true |
---|
colour | Blue |
---|
title | Open |
---|
|
| What data should be supplied - current date/time? Will it default if not supplied? | Question for Thunderjet |