Description
As users renew orders with vendors in external systems, they hope that the renewal information will update the corresponding orders and order lines in their FOLIO instance.
Renewals are updates to existing orders so all of these requests will need to be sent with a FOLIO purchase order line number (ILS number). These unique numbers will be used to identify which POL that the corresponding system would like to update.
Problems being solved (Updated based on exercise 1)
Updating order information after renewing orders with a vendor is time consuming and thus expensive for the library. (Priority: 3.23)
Feedback
- More frequent updates after renewal are changes to Fund or subscription number
- Need to indicate what has been cancelled
- Occasionally we need to update when adding electronic access to a print sub
Manual data entry offers the opportunity for human error. As a result the data between the vendor system and FOLIO can get out of sync. (Priority: 4.75)
Feedback
- The updates may also just not happen
- Maintaining the match point is one of the most error prone areas
It is difficult to manage commitments for renewable orders as accurate data is often only provided to the library at time of invoice. (Priority: 3.34)
Feedback
- Minor differences can be expected as often encumbrances are based on expended amounts from the previous year
- This is why we do not encumber these
The data associated with renewable orders can change year over year (Eg. Publisher) and these types of updates could be missed and lead to confusion about library holdings. (Priority: 4.75)
Feedback
- Library is notified about changes to title, frequency, publisher, etc. and generally they are more a concern with updating the marc record than the order data
- There is a chance but not really tied to renewal
- Doesn't happen often and generally communicated when they do so they are not difficult to update
Other feedback
- Updating SNAs or providers
- Should help with confusion of whether an order should be closed or not. Sometimes this gets out of sync between the two systems and its difficult to determine what the library wanted to do
- Could be used to observe complete delivery of all items. Integrating the claiming of missing issues. Possibly delay of delivery could be pushed to the library to save time chasing issues
- We wouldn't want erroneous information from the vendor pushed into FOLIO. The vendor system may have errors as well that could make it a pain to have the integration
Use Cases & Requirements:
Requirement | Status | Use cases |
|---|---|---|
| Vendor system will send an indication of what titles have been canceled and what titles are renewing | PENDING | When renewing orders in third party systems the library will decide what to renew and what not to. Titles that are not renewed with the vendor are canceled in the ILS system. When these get out of sync it can be difficult for the library to decipher whether they wanted them canceled or not. |
| Order line format can be updated to reflect changes without disturbing integration | PENDING | Library needs to update order to add add electronic access to a print subscription |
| When vendor reference numbers are added they include a timestamp that can be seen in the UI | PENDING | When renewing an order for which the Vendor reference number is changing the library must update the ILS order and make clear which vendor reference number is the current one. Multiple numbers would be confusing over time if there is no indication of when and why they were added. |
Exercises:
Exercises
Exercise | Title | Status | Details | Results |
|---|---|---|---|---|
1 | Evaluating Problem Statements above | CLOSED - June 9, 2021 | See google form at https://forms.gle/TvgKfgTeRu37hsEK6 to participate. |
Data available for update:
| Data point | Logic | Comments |
Vendor | Not updated but included as reference | |
Cancellation Restriction | Updated | |
Cancellation_restriction_note | Updated | More important to have the most recent restriction note information. Adding to this field each year might result in the same note being added multiple times. |
Price | Updated | |
Currency | Updated | |
Vendor Reference Number | Added to existing | To safely update this field users would need to know what the most recent numbers are. Otherwise, it could be very confusing as to which number is current. Ie. what they actually renewed this year. Consider adding a data added to vendor ref number. to help identify which is most recent |
PO Number | Not updated but included as reference | |
PO Line | Not updated but included as reference | |
Customer Note | Added to existing | |
Subscription to Date | Updated | |
Renewal Date | Updated | |
Quantity | Updated: based on Purchase order line format | |
Fund Code | Updated | |
Publisher | Updated | |
Type | Not updated but included as reference | |
vendor_account_number | Updated | User group believes it could be useful to allow third parties to use this as a match point. Specifically if they are storing legacy order numbers in this field. |
unit_price | Updated: based on Purchase order line format |