Spike: Record Contribution: Process contribution or update Jobs of Bibs to an INN-Reach central Server

Description

Purpose/Overview:

This is to prepare a design for MODINREACH-51. The design has to be documented, reviewed and approved by the team

 Acceptance criteria:

  • describe the findings on a wiki page

  • present to the team and get approval from architect

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Dima TkachenkoJanuary 10, 2022 at 12:42 PM

Not needed anymore since the dependent story has been implemented and demoed

Brooks TravisMay 17, 2021 at 9:53 PM

While we do need to be able to manage the contribution process manually, we also need to provide a facility for adding new records automatically or updating existing records when they are modified that does not require manual intervention. Ideally, we'd be able to re-use a lot of the same infrastructure for both scenarios. We also need to provide a general transaction log for those event driven updates that is accessible to a local administrator, as well. Just some things to keep in mind as we try to come up with a solution here. Thanks.

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Volaris

Fix versions

Release

Lotus R1 2022

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 14, 2021 at 11:48 AM
Updated March 17, 2022 at 5:05 AM
Resolved January 10, 2022 at 12:42 PM
TestRail: Cases
TestRail: Runs