-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: adds superdataset metadata in studyminimeta.yaml #61
base: master
Are you sure you want to change the base?
Conversation
Wait, I used |
Yep, to Git would make it actually reviewable :) This should get it into Git. |
ping on this PR -- would be great to see it finalized/merged to get a complete dataset for the https://datalad.github.io/datalad-catalog/ demo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from a cursory read this looks ok to me
|
||
# person information, one record for every email-key used above | ||
person: | ||
[email protected]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it would be a great example to follow, I decided to ask a clarification question: why did you side for the meaningless a, b, c, d which might generally result in a confusion and misattribution (mixing up one person ID over another) in favor over some
- clearly not a valid email
- including the actual name
[email protected]: | |
person-ayan-sengupta: |
or even just
[email protected]: | |
ayan-sengupta: |
or alike?
This adds a
.studyminimeta.yaml
file with some basic metadata for the SF superdataset.The impetus behind this is to be able to render a pretty catalog, without missing data, from the SF super and subdatasets.
TODO:
Comments by @mih @adswa @loj et al welcome.