Minimal fields (to enable software citation & author credit)
See original GitHub issueDuring the codemeta workshop in Portland a few of us sat down and tried to work through what is the absolute minimal set of fields to enable software citation and author credit. I’m afraid I’ve managed to loose my note from this discussion but I believe we settled on the following (pulling field names from https://github.com/codemeta/codemeta/blob/master/crosswalk.csv):
AuthorId
SoftwareIdentifier
Version
We discussed the fact that Version
might not always be available and that datePublished
would be a worse-but-better-than-nothing-alternative.
Thoughts on this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (7 by maintainers)
Top Results From Across the Web
Guide for authors - Data in Brief - ISSN 2352-3409 - Elsevier
A Perspective article should contain a comprehensive review of current data sharing practices in the field, as well as a summary of current...
Read more >Chapter 9.Citations and Referencing – Writing for Success
The purpose of citations is twofold: to give credit to others for their ideas and to allow your reader to follow up and...
Read more >Instructions for preparing an initial manuscript | Science | AAAS
Journal article references should be complete, including the full list of authors, full titles, and inclusive pagination. Article titles are displayed in the ......
Read more >Submission Guidelines | PLOS ONE
Provide at minimum one contribution for each author in the submission system. Use the CRediT taxonomy to describe each contribution.
Read more >Reporting standards and availability of data, materials, code ...
A condition of publication in a Nature Portfolio journal is that authors are ... Citations of datasets should include the minimum information recommended...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is a great thread, but I think the codemeta project should defer to the Software Citation Implementation group to advise on this issue: https://github.com/force11/force11-sciwg (Thanks @danielskatz @mfenner and others) . Deciding precisely what metadata fields must be associated with a use case seems beyond the scope of codemeta.
I don’t think we should be proscriptive; a DOI or other global identifier would be best; a github URI to a tagged release is probably next best, and then a github URI to a repo (which loses version info).