Uploaded image for project: 'edge-orders'
  1. edge-orders
  2. EDGORDERS-40

Add routing definition to mod-ebsconet

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.0
    • Labels:
      None
    • Template:
      Thunderjet/Firebird Back-end Story Template
    • Sprint:
      ACQ Sprint 108
    • Story Points:
      2
    • Development Team:
      Thunderjet

      Description

      Purpose/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

      Needed as a router to the corresponding mod-ebsconet module with business logic according to the routing configuration.

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

      Requirements/Scope:

      1. Add routing configuration GET and PUT order lines for EBSCONET
      2. Define GET and PUT order lines endpoints

      Approach:

      • Add routing configuration GET and PUT order lines for EBSCONET to the src/main/resources/api_configuration.json
      • Define GET and PUT order lines endpoints in the ramls/edge-orders.raml
      • Add PUT method to org.folio.edge.orders.utils.OrdersOkapiClient#send
      • Note* : As edge-orders uses mapping from configuration and works as proxy, then no need other specific implementation

      Acceptance criteria:

      • Routers defined
      • API definitions added

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                aliaksandr_pautau Aliaksandr Pautau
                Reporter:
                Andrei_Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases