EBISPOT / DUO

Ontology for consent codes and data use requirements
Other
64 stars 15 forks source link

Term Change Request: Project-Specific Restriction #74

Open MKonopko opened 4 years ago

MKonopko commented 4 years ago

Term definition change requested: Project-specific restriction

Per H3Africa Feedback:

Original: This requirement indicates that use is limited to use within an approved project.

Suggested Change: This restriction indicates that use is limited to projects approved by XXXX

Reason: This definition is not clear, who approves the project? Does this mean each project that wants to apply for the data must first be approved? Does the DBAC example fit in here? Does the original PI approve, or does the consent/info sheet specify projects? Needs more context or example

Per @GiselleMarie "Suggests this remains as the original text definition. i.e., "This requirement indicates that use is limited to use within an approved project". This is because when the researcher applies for some data they sometimes have to specify & detail which project that data will be used in. Therefore, if the requestor wants to use the same data, but in another project they should have to re-apply or at least amend their original agreement." Per V Nembaware "Thanks for the clarity Giselle - not sure if you might be open to adding some of these key points you have raised to the original definition? Or maybe add/attach comments/notes to the term to make it clearer?" Per @mcourtot "This is a great suggestion - we always have the opportunity to add comments to the terms, or even example of usages. Any guidance that can be provided to make it as explicit as possible would be very helpful."

mamanambiya commented 4 years ago

Final response on this is that examples of who approves the project should be added in the comments/notes or definition.

mcourtot commented 4 years ago

I think adding examples is always a good thing, and should not be controversial. Can you suggest some please @mamanambiya @GiselleMarie ?