Generate storage expiry notifications for cohort owners (Contacts in DAISY)

[pinarpink]

this request is from the BIOMAP project.

---

Hi Pinar

Thanks for the reply, very much appreciated – glad we can update the fields, that does make sense – we’ll just have to make sure (should we go this way) to update it as and when the studies get extended.

Obviously on us to make sure this happens but as a thought, if the system could send off an email reminder (to the cohort owners) with enough time for us to react (3 months?) prior to the data residence expiring that would be quite useful to ensure the cohort doesn’t expire when it shouldn’t.

Thanks again Michael Duckworth Data Manager Skin Therapy Research Unit St John’s Institute of Dermatology

[jLebioda]

To be discussed with Soumya to double check if this should be actually the way DAISY behaves

[soumyabrataghosh]

@pinarpink @jLebioda @vildead I cannot exactly recall the actual request sent to Michael Duckworth. As far as I understand the data-storage expiry should be on the date of project completion (March 2024). And Biomap people usually interact with the Biomap REDCap EDC system for updating their cohort metadata. Not sure why he communicated to/from DAISY.

[vildead]

Lets postpone the issue - pinar may have more clear information.

Once we come back to it, I can think of two things

• the cohort model has no start/end or expiration date but it will change once the cohort and project entity become more similar (as planned)
• more datasets of different projects can come from a same cohort. Each of the datasets can have different storage expiration date on our infrastructure.

moving to 2022