Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-190

Create/Renew orders in FOLIO from EBSCONET

    XMLWordPrintable

Details

    • Medium < 5 days
    • Medium < 5 days
    • Low
    • XXL < 30 days
    • Thunderjet
    • 75.95
    • R2 2021
    • R4
    • R4
    • R4
    • R4
    • R4
    • R4
    • R5
    • R5
    • R4
    • R4
    • R4
    • R4

    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 with EBSCONET.

      Order Requirements:

      • Ability to identify materials as renewing
      • Ability to maintain order number from year to year for ongoing orders
      • Ability to be able to continue to receive and invoice against ongoing orders year over year
      • Ability to capture start date and period for renewable material being ordered
      • 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

      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
      • 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 creation/editing
      • Returning Order number(s) and response EBSCONET system

      Tech Design:

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

      TestRail: Results

        Attachments

          Issue Links

            has to be finished together with

            New Feature - New feature requests UXPROD-2361 Simplify implementation of order API integrations for vendors

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is cloned by

            New Feature - New feature requests UXPROD-2588 Prep for Create/Renew orders in FOLIO from EBSCONET

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. EDGORDERS-5 API Tests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. EDGORDERS-6 End-to-end tests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. EDGORDERS-40 Add routing definition to mod-ebsconet

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FOLIO-2985 Create mod-ebsconet github repository and add to CI

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-1 Project setup in GitHub: mod-ebsconet

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-2 Define order lines EBSCONET schema

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-3 Implement retrieve ebsconet order line logic

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-4 Implement update ebsconet order line logic

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-5 Define retrieve and update ebsconet API for order lines and stub them

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-7 Add /ebsconet/validate endpoint configuration

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODEBSNET-9 Attempts to renew through EBSCONET are failing in Rancher env

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODEBSNET-10 Handling mixed orders for ebsconet

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODGOBI-100 Update the logic of checking the availability of orders and acq-module

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-521 Allow updating quantity and location for Open order if it is initiated by EBSCONET

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-548 Publisher could not be updated by EBSCONET

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-195 Import invoice in EDIFACT format (Folijet work)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-1019 Vendor agnostic integration API with subscription agent system for subscription renewals

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-136 Title, PoLine schema updates

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases