Post-MVP feature to keep Coko QA with NCBI data BCMS instance and BCMS production databases in sync
Context
Once #1456 and #1635 are implemented and after the NCBI Production BCMS is deployed, it will become important to keep the Coko QA BCMS instance with NCBI data in sync in real time with NCBI production data for accurate stress and other testing.
Proposal
Per the SOW and NCBI feedback to Coko proposals, NCBI proposes data be kept in synch via file transfer of newly added and updated data to Coko, which will also provide stress testing.
Design
TBD
Acceptance criteria
-
NCBI Production and Coko QA instances are in sych with up-to-date NCBI production data -
Means of keeping data in synch will not interfere with timely processing by NCBI submitters -
Means of keeping data in synch will not impose significant NCBI developer time
Definition of ready
-
BCMS User Story / Context has been well defined -
The priority of the user story is specified and agreed -
Digital assets added (design, database scheme, mockups etc if relevant) -
Coko Technical Proposal approved by NCBI -
Testable Acceptance Criteria approved by NCBI -
Estimate of effort to complete (time or points) -
The issue has been broken down into development tasks (if necessary) -
Requirements Clarified -
The product owner and development team agree that the user story is ready for development -
NCBI adds “Dev_Ready”
Definition of done
-
All coding tasks are finished and implemented -
QA approved -
Deployed and tested on “ncbidev” (by Coko team) -
Deployed and tested on “ncbi” (by NCBI team) -
Acceptance Criteria Met
Implementation
Alternative approaches (if applicable)
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking