Details about the project (e.g., Name, Affiliation, website). May also includes a field for tagging any projects that protocols are compliant with (e.g., Earth Microbiome Project/TARA Oceans). Once submitted the relevant PI may be notified and could choose to endorse or reject the protocol as compliant with their project.
Issues identified during working session GSC22 meeting in Moorea:
-
key should be specific enough that the value can be atomic
- currently includes name + website + projects that the protocol is compatible with
-
Ambiguous whether it's the project who created it/used it/ ...
-
If we are going to be strict about compliance we should have a specific field for that, which would have an endorsement process behind it
Guidance for future terms
- if possible please provide the most consistent URI associated with your project (e.g. Cordis Project ID for EU projects)
ideally would be the DOI of you Project Management Plan
Issues identified during working session GSC22 meeting in Moorea:
key should be specific enough that the value can be atomic
Ambiguous whether it's the project who created it/used it/ ...
If we are going to be strict about compliance we should have a specific field for that, which would have an endorsement process behind it
Guidance for future terms
ideally would be the DOI of you Project Management Plan