...
| 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
- Horrasawitz does not accept standing orders via EDI so the library will send PDFs via mail or email.
|
| Send orders based on different export configurations for the same vendor, based on Account information. | | - The institution has multiple libraries there will be different pickup and dropoff directories for the EDI files. Meaning two separate EDI files would be uploaded to two separate directories OR two separate FTP locations. Eg. one for Main library and one for Law
- Some accounts with different envelope addresses (Library EDI codes) may be included on the same EDI file OR the library may need to have them exported on separate files.
|
| 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 based on account number and order type | | - For a given vendor the library may send most orders through EDI but treat some order types differently.
- Data that drives the identification of a different communication method
- Account number (Team/location/Acquisition unit. These would likely be represented by account number)
- Order type (One-time, Ongoing, Ongoing-subs)
- Material type (this could be a concern but generally if it is it will be backed into the account number or order type)
|
| Limit what orders are sent based on order data (Acquisition method?) | | - For some material types the library will send order info through EDI but for others, they may create orders in the vendor systems and recreate in FOLIO.
- The library will differentiate between rush and non-rush. Non-rush orders going through EDI and Rush orders going through email
- Orders that are identified as certain acquisition methods should NOT be exported because the Vendor would already have these orders.
|
| 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.
|
| Allow user to edit open order and set it to export. After save this order should be included in the next EDI export. Once exported this field would not be editable. | | - When we know files are being uploaded later in the day to the FTP location, someone may notice that an order was included on the wrong file. To correct this they will edit the order and indicate it should be exported and save. This should allow this order to be included in the file before it is uploaded to the Vendors FTP location at the set time.
- The library has not noticed that the box was checked and would like to uncheck the export box after it was opened but before it was included in the export.
|
Proposed workflow:
Export details are configured for each organization in the organization record
...
Option 1:
The organization has a default setting for "Automate export" and via which type it should be exported.
Image Removed
Option 2
by acquisition method
Acquisition method is a controlled vocabulary
Image Added
Automated export is set by acq method with "Export via" set by account number in the organization record and each
Image Added
Each is editable at the POL
Image Removed
Each organization can have multiple Integration details and details types configured. Ie. Possible multiple EDI configuration, Email, csv etc.
...
Question | Status | Conclusion | Comments |
|---|
| Should the decision to export be determined by the acq method on the POL and be based on organization? | | |
|
Should separate POLs potentially have different export settings? | |
|
|
| Do export details need to be shown at the PO level? | |
|
|
...