Restricted by date

[mcourtot]

EGA has a policy that restricts access to submission + 6 months. Depending on the date at which a dataset is submitted under this policy, their availability date will be different:

Policy object EGAP1 has DUO:0000025 = 'submission + 6 months'
Dataset EGAD1 ( which references EGAP1) submitted on 1/1/19 - returns DUO:0000025 = '1/7/19'
Dataset EGAD2 ( which also references EGAP1) submitted on 1/4/19 - returns DUO:0000025 = '1/10/19'

We should agree on a way to represent date as a specific format. Based on this use case I'd tend to say DUO:0000025 should be used with a date in ISO 8601 but I'd love to hear other use cases/comments.

[rushtong]

+1 to ISO 8601 - it is very much an accepted standard in software: https://stackoverflow.com/questions/10286204/the-right-json-date-format

[mcourtot]

Other use case from Blueprints project:

• being able to specify a start data eg "this dataset can be made available after the agreement X is signed"
• use such an event "agreement X being signed" instead of a fixed date

Because the date of the agreement is not known in this case those cases wold probably have to go through manual review anyway, but we should plan and have a text field that could capture that information

[mcourtot]

Other use case from THL Biobank: each project is typically valid for 5 years

[mcourtot]

From EGA: We already use DUO:0000025 for ICGC datasets and others (https://ega-archive.org/datasets/EGAD00010001591) for the same usecase, except this is time limited to 12 months from the date of first access.