-
Notifications
You must be signed in to change notification settings - Fork 33
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
add citation/references for datasets #3
Comments
ooh, missed this issue! I think that's a great idea!!! might be a heavy lift, how would you propose tackling it? |
by the way it's all thanks to Alex Lerch!! He's been doing the hard work with this for so long 😄 |
what about just starting with a DOI field for now to keep things homogenous? I can start adding a few through pull requests... |
yes I know his table for quite some time. |
@faroit @ejhumphrey BTW, for now I am maintaining only my original list at https://gist.github.com/alexanderlerch/e3516bffc08ea77b429c419051ab793a#file-data-sets-md because I don't have write access to the repository... |
@ejhumphrey maybe you can add Alexander to the repo? |
@alexanderlerch Great, lets fill in the fields later via PRs. |
hiya @alexanderlerch @faroit, a few things from me. access: given your past contributions, you've both been granted write access on this repository. Generally speaking though, I hope that not having write permissions won't dissuade folks from contributing via PRs ... if this is a high barrier, that'll be good to know. outputs: Ideally, this repository would have a "build" step, per #5, that automatically produces updated HTML tables (as JSON) and MD files when the YAML is changed (and verified, per #1). In this world, only the YAML would be modified directly, and everything else is automatic, and life is easy and great. 😀 Canonical Ref / DOIs: Two thoughts here. |
Just to verify how many references we will get, I went through the datasets starting with A through D and looked up the references (only added DOI links or permalinks). I added these as links to an additional 'reference' entry - let me know if that is how we can do it/what you think: https://github.com/ismir/mir-datasets/blob/lerch_updates/mir-datasets.yaml @ejhumphrey I noticed that there are no DOIs yet for the 2018 ISMIR papers - how should we handle that in the datsets list? |
cool, thanks for this! Looks good to me, I think ... @faroit, any thoughts here? Only thing that comes to mind is that the tests would need to be updated to reflect the schema change, as well as the readme. The 2018 papers do have DOIs, but I had forgotten that the PR is still outstanding (from November 😞). I'll see if I can get that over the goalline in the next 30'. |
Wow, this is great work!
Since we have the problem over there at SiSEC that folks constantly cite the wrong paper for one of our datasets, it came to my mind to help the community to make things more clear.
What about adding one citation field to each dataset. Possibly by using using a DOI or putting a CSL string. This could be a zenodo/a paper DOI or just a website when nothing applies. Tell me what you think? I can help out if you like the idea...
The text was updated successfully, but these errors were encountered: