User story
When a study is created in Sapio, and propagated to mlwarehouse and Sequencescape via the Integration Hub, we would like the Integration Hub to act the same whether the study exists in Sequencescape or not. Therefore, the Integration Hub will just call a Sequencescape 'upsert studies' endpoint, and the Sequencescape will behave differently depending on whether it already knows about the study or not.
Who are the primary contacts for this story
Katy, Steve I
Who is the nominated tester for UAT
Test within PSD, and with the Integration Hub.
Acceptance criteria
Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:
- When Sapio study creation API endpoint is called:
- If Sequencescape does not already have a study with that uuid:
- If Sequencescape already has a study with that uuid:
Additional context
See Slack conversations:
Sequence diagram - relevant portion copied below:
Deployment notes
Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.
Add any other context or screenshots about the feature request here.
User story
When a study is created in Sapio, and propagated to mlwarehouse and Sequencescape via the Integration Hub, we would like the Integration Hub to act the same whether the study exists in Sequencescape or not. Therefore, the Integration Hub will just call a Sequencescape 'upsert studies' endpoint, and the Sequencescape will behave differently depending on whether it already knows about the study or not.
Who are the primary contacts for this story
Katy, Steve I
Who is the nominated tester for UAT
Test within PSD, and with the Integration Hub.
Acceptance criteria
Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:
Additional context
See Slack conversations:
Sequence diagram - relevant portion copied below:
Deployment notes
Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.
Add any other context or screenshots about the feature request here.