GOBI API integration for creating Purchase Orders, Basic
(UXPROD-989)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2018 | Parent: | GOBI API integration for creating Purchase Orders, Basic |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Done | Votes: | 0 |
| Labels: | acquisitions, external_sys_int, integration, orders, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Epic Link: | GOBI API integration for creating Purchase Orders, Basic | ||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||
| Front End Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||||||||||
| Estimation Notes and Assumptions: | Still in early stages of analysis. Not sure if we will receive XML or JSON etc. | ||||||||||||||||||||
| Development Team: | EBSCO - FSE | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R5 | ||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||
| Description |
|
Purpose: Allow for the ordering of materials from GOBI via API integration. Create an order in the GOBI system and have it populate into FOLIO orders automatically.High-Level Requirements:Receive authentication key from GOBI and match it with the key the user has added to GOBI authentication key in FOLIO.Map fields for incoming data in order to create orders with the details sent from GOBI Response time expectations: As far as an SLA is concerned, other ILS systems usually respond between 3 and 5 seconds, with some outliers near 30 seconds. Appropriate SLA for Folio to meet is probably 95% of responses within 5 seconds and no requests exceeding 30 seconds. Not responding to the API ties up the thread and can hold other orders in a queue. If you expect Folio to be more popular than Alma or OLE, then meeting or exceeding this SLA would be needed to handle the volume without causing too much customer delay. *Note: when I say customer delay, I am talking about fulfilling their order, there is no actual customer at a UI waiting for this response, otherwise we would be asking for sub-second responses. *Also Note: At 100 seconds, our call fails (Timeouts), and the order is placed back into the queue for a retry (Up to 10 times) before it gives up. So if your application does not process the order within 100 seconds, you can expect to see it again. This can cause problems with duplicate orders unless you fail your own thread and rollback the order if you cannot respond within 100 seconds. This is what OLE does. |
| Comments |
| Comment by Hkaplanian [ 06/Jun/18 ] |
|
|
| Comment by Cate Boerema (Inactive) [ 09/Jul/18 ] |
|
Changing all the external system integration features into epics. While this will extend the epic list by 7 items, these really are all mini-projects that can be assigned to teams and have POs and priorities. In that regard, they make sense as epics. I will deprecate the old External Systems Integrations epic. |
| Comment by Cate Boerema (Inactive) [ 09/Jul/18 ] |
|
Actually, I should just clone these features and create epics that way. Making this a feature again and linking up to this epic:
|
| Comment by Dennis Bridges [ 18/Jan/19 ] |
|
This issue was split into
|