Skip to content
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

doi -> full citation in references.md #49

Open
ypar opened this issue Aug 29, 2019 · 3 comments
Open

doi -> full citation in references.md #49

ypar opened this issue Aug 29, 2019 · 3 comments

Comments

@ypar
Copy link
Contributor

ypar commented Aug 29, 2019

Currently, cimr-d recommends data submitters to indicate doi(s) of data or publication(s) to cite when specific submitted data is used. This is then stored in the catalog.txt. These doi should lead to a full citation (.ris, .bib or such likes) in cimr-d references.md.

@cgreene
Copy link
Member

cgreene commented Sep 6, 2019

The manubot citation infrastructure could be used to fill this in. Are you thinking that the full citation would go somewhere like the selected space in this screenshot?
Screen Shot 2019-09-06 at 9 09 01 AM

@ypar
Copy link
Contributor Author

ypar commented Sep 6, 2019

Yes. doi on the README.md of the processed dir with a link to references.md with a full citation will be best. To fit each file info per line, timestamps may need shortening (e.g. no h m s). I will give it a bit more thought.

@ypar
Copy link
Contributor Author

ypar commented Sep 10, 2019

Putting this as a reminder to myself. I think the useful format for the README.md in the processed dir would be, e.g.

  • data_type
    • [context such as disease or tissue name](aws s3 hyperlink): file_size, [doi](citation file, article link or specific line in cimr-d references.md), [metadata](processed yaml path), updated on ZZZZ

It will be some work trying to pretty-it-up, but it will be more informative than listing file names that tend to be very study-specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants