Add routing definition to mod-ebsconet

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://folio-org.atlassian.net/wiki/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

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Aliaksandr Pautau February 26, 2021 at 12:25 PM

Verified on folio-testing via API tests

Yauheni Kuzmianok February 25, 2021 at 1:09 PM
Edited

Verified on snapshot via api tests

 

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 27, 2021 at 7:05 AM
Updated February 26, 2021 at 12:25 PM
Resolved February 26, 2021 at 12:25 PM
TestRail: Cases
TestRail: Runs