feat: comet data release - #184
Open
mkirk111 wants to merge 8 commits into
Open
Conversation
Contributor
Author
|
/preview |
yoon-chi
force-pushed
the
cometdatarelease_7_2026
branch
from
July 21, 2026 20:21
dc77724 to
800fcc3
Compare
Contributor
|
/destroy |
Contributor
|
/preview |
|
I agree with the copy, except I try to avoid using em dashes when commas are appropriate. I will say that the definition of unrestricted data feels a bit weak. We try to align with NIH guidance ([here](https://grants.nih.gov/policy-and-compliance/policy-topics/sharing-policies)) and follow their best practices for distinguishing between restricted (closed) and unrestricted (open) data. @mkirk111 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
updates to documentation for iDAT file release for COMET
updated to add unrestricted data request information