Y24-420 - As LeGo, we would like the new study set up fields to be added to the MLWH

[harrietc52]

User story
As LeGo, we would like the new study set up fields to be added to the MLWH, so that I can pull the data into eDAM and create and update DAA’s from it.

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.

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:

• on sample creation in Sequencescape, the list fields from the Google Sheet are sent to the MLWH study table
• confirm the SQL query with Obion to enable eDAM to read the new fields added to the MLWH study table. (See current query used below)

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

Questions

• Study title/ description questions as per Y24-419
• Confirm the field names? i.e check all fields in Google Sheet are agreed with eDAM as this is what they will end up being on study table in MLWH. The red fields in the Google Sheet are slightly different.
• Is “Yes” “No”, okay for those fields in MLWH, or would you prefer booleans?
• For include_collabs, would those collaborators be created as it currently does, in eDAM when you pull in the study data?
• There is a note in eDAM DAA setup questions “Users must be able to add multiple collabs”. How would you like this to be persisted in the study table in MLWH? If there is more than one collaborator?

Fields to be added:
Google Sheet

eDAM DAA setup questions

Current query used in eDAM to pull MLWH study data:

SELECT id_study_lims, description, accession_number, study_title, faculty_sponsor 
FROM study 
WHERE data_release_strategy=‘managed’
;