Y24-421 - As LeGO, we would like to make sure DAAs, which are already created and approved are updated in eDAM, when a Study in Sequencescape is updated

[harrietc52]

User story

As LeGO, we would like to make sure DAAs (which are already created from eDAM internal) are updated when a Study in Sequencescape is updated.

Currently, a script from eDAM pulls in the data from the MLWH study table at 2am everyday. It then uses this to create the DAA. When a Study in Sequencescape has been updated, the script in eDAM removes the existing studies in eDAM first, before inserting the studies obtained from MLWH, so all the studies in the system are up to date.

However, DAAs that have already been approved do not get updated.

Who are the primary contacts for this story
@harrietc52

Who is the nominated tester for UAT
Odion A

Acceptance criteria
To be considered successful the solution must allow:

• Add a story to eDAM to asking that DAAs are updated, when a Study in Sequencescape is updated

Dependencies
This story is blocked by the following dependencies:

• #<issue_no.>
• sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

• #<issue_no.>
• sanger/#<issue_no.>

Additional context
Add any other context or screenshots about the feature request here.

Questions

• Firstly, is this story required? Should it be allowed that a Study whose DAA is already approved, can be updated? If not, should the Study in SS be prevented from being updated if the DAA has already been approved?
• All are eDAM DAA fields, which have been added to the Sequencescape Study creation page, allowed to be updated?
• If a Study is updated, does this affect any samples assocaited with the study, either before or after sequencing?
• cant edit it both?
• can all fields be updated?
• single source of truth