stan-dev / stan-dev/stan-dev.github.io
DOIs for case studies
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 23
- Forks
- 41
- Avg merge
- 11h 42m
- Merged PRs (30d)
- 2
Description
@bnicenboim suggested here: https://github.com/stan-dev/stan-dev.github.io/issues/37#issuecomment-309366022
you should think on adding DOIs to the case studies and the Stancon papers. If I want to refer to them in a paper, it's much better than to have a link (and journals usually ask for the DOIs).
We generate DOIs for the software, but we don't know how to generate DOIs for case studies. So any suggestions would be appreciated (feel free to just edit the issue rather than adding comments if there's a concrete workable suggestion).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing DOI process for the software and the case studies and Stancon papers referenced in the issue. Determine a concrete, workable approach for assigning DOIs and document what would need to change; the issue is complete when that approach is clear enough to apply.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100