Order Integration with External Systems (Misc) (UXPROD-1580)

[UXPROD-3257] Update FOLIO<>EBSCONET order renewal logic Created: 27/Aug/21  Updated: 15/Sep/22  Resolved: 15/Sep/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: Order Integration with External Systems (Misc)

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: EBSCO, acquisitions, lotus-at-risk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODEBSNET-15 Dates are being input as 01/01/0001 Closed
is defined by MODEBSNET-27 Update logic for supporting "customer... Closed
is defined by MODEBSNET-33 Update logic for supporting "customer... Closed
is defined by MODORDERS-636 Update po lines when an order is clos... Closed
is defined by MODORDERS-663 Update PO workflow status based on ca... Closed
is defined by MODORDERS-664 Release encumbrances when POL payment... Closed
is defined by MODORDERS-682 Remove Renewal date and renewal inter... Closed
is defined by MODORDERS-714 Fix issue with Receipt and Payment st... Closed
is defined by UIOR-961 Renewal date and renewal interval no ... Closed
is defined by UIOR-965 Display "Renewal note" field on POL Closed
is defined by MODEBSNET-13 Update logic for supporting fund expe... Closed
is defined by MODEBSNET-22 Support canceling POL(s) through EBSC... Closed
is defined by MODEBSNET-30 Update logic for supporting "Renewal ... Closed
is defined by MODEBSNET-39 Renewal note is blank after update Closed
is defined by UIOR-740 Add cancel POL action and display ind... Closed
is defined by UIOR-889 Add cancel PO action and display indi... Closed
Epic Link: Order Integration with External Systems (Misc)
Front End Estimate: Medium < 5 days
Back End Estimate: XL < 15 days
Development Team: Thunderjet
PO Rank: 75.95
Rank: Cornell (Full Sum 2021): R1

 Description   

Overview: Establishing an integration with EBSCONET to manage ordering and renewals via an API integration. This will limit errors and save users time in managing order renewals.

Order Requirements:

  • Ability to capture Title number and vendor order number to explicitly identify material being ordered
  • Ability to add or remove material from ongoing orders year over year as some may not always renew
  • Ability to observe in the UI the most recent date the order was renewed.
  • Update the renewal date upon renewing the order

See https://folio-org.atlassian.net/wiki/x/hgRU for details on EBSCONET data

see https://folio-org.atlassian.net/wiki/x/JQhU for detail on order cancelation

Out of scope:

  • Automated claiming workflow

Approach:

  • Build API integration through edge-orders that will route JSON file to a mod-EBSCONET module in FOLIO for mapping EBSCONET order data into FOLIO order data
    • allow external service to execute a GET OR PUT request for POL
  • Create MODEBSCONET module for retrieving UUIDs etc. for EBSCONET data and prepping data to be sent to mod orders
  • Communicating EBSCONET order data to mod-orders for order editing

Tech Design:

https://folio-org.atlassian.net/wiki/display/DD/Subscription+Orders+Integration



 Comments   
Comment by Dennis Bridges [ 05/Jan/22 ]

Adding the label lotus at risk because the cancelation of orders may be more complex logic than anticipated. It will require updates to other critical logic that adds some risk and need for more thorough testing.

Comment by Dennis Bridges [ 15/Sep/22 ]

All stories resolved

Generated at Fri Feb 09 00:30:40 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.