Tenant level mapping rules

Description

Overview
Currently the default mapping rules are stored along with the code. Few libraries have different requirements to change the how the default rules are present. Use mod-configuration to store tenant specific overrides.
Implementation:
If config is present in mod-configuration use that to create the rules. If not use default rules

Acceptance Criteria

  • Config is stored in mod-configuration

  • default mapping rules are loaded by default to the table

  • unit tests are written

  • API tests are written

Environment

None

Potential Workaround

None

Attachments

3
  • 11 Jun 2020, 07:57 AM
  • 11 Jun 2020, 07:57 AM
  • 11 Jun 2020, 07:56 AM

Checklist

hide

TestRail: Results

Activity

Show:

Andrii Novytskyi June 11, 2020 at 7:58 AM
Edited

Verified on folio-snapshot:
Add specific rules to the mod-config only for "001" field"

Export passed successfully

And the MARC record is valid and looks like:

Kruthi Vuppala June 2, 2020 at 12:02 PM

oh right, It skipped my mind that we were going to call this after we begin export.

Andrii Novytskyi June 2, 2020 at 11:56 AM

Agree with Igor, and then there will be no need to complicate the logic in the export manager

Igor Gorchakov June 2, 2020 at 10:59 AM
Edited

mod-config provides async client. As we sent HTTP calls from blocking code we need to use blocking client, this is the rule of data-export 🙂

Kruthi Vuppala June 1, 2020 at 3:19 PM

If you are did not come across already FYI.. mod-configuration provides a configuration client that helps you make these API calls. You can try to make use of that

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Concorde

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 6, 2020 at 12:13 AM
Updated November 30, 2023 at 8:28 PM
Resolved June 11, 2020 at 4:29 PM
TestRail: Cases
TestRail: Runs

Flag notifications