| Requirement | Status | Use cases |
|---|
| Generate EDIFACT format files based on FOLIO Orders | | - Library currently communicates all orders with large vendors via EDI. This reduces the amount of duplicate effort needed to manage acquisitions through this vendor. Often this is because the vendor could not or would not support a direct API integration with their ILS system
- Users need to confirm that they don't already own or have an outstanding or for the material they want to acquire. This is most easily done in the LSP system. Libraries will then check multiple vendors to compare pricing before acquisition.
|
| Send orders in different formats as specified in the Organization record. Eg EDIFACT format, email etc | | - Library needs to configure different EDI details for different organizations. Often files need to be uploaded to different directories or use different naming conventions or different codes
|
| Send orders based on different export configurations for the same vendor, based on Account information | |
|
| Allow user to indicate they want the order to be sent AFTER the order has been opened | | - Librarian forgets to indicate they want the order to be exported. The order is now open, but we want to be able to check that box so it will be included in the next export.
|
| Send orders in different formats for the same Organization depending on account number or other order detail? | | - For a given vendor the library may send most orders through EDI but treat some order types differently.
|
| Limit what orders are sent based on order data (Acquisition method?, order type? material type?) | |
|
| Allow library to trigger a "Resend" for the generated file | | - If something goes wrong with the upload to ftp (Which does happen) we need to be able to resend the EDI file, without regenerating it and sending additional orders along with it.
|