Open mfenner opened 7 years ago
I think a starting point is the metadata standards that are part of the citation workflow, e.g. bibtex. If you can generate a meaningful bibtex entry for software with the metadata, you can enable downstream workflows (import and use in reference managers, generation of a DataCite DOI, submission of bibtex file to publisher, etc.).
This makes sense to me too. Now we need to figure out how to do this, which might really mean getting enough knowledgeable people involved
Knowledgeable people for citation workflows include @zuphilip, @adam3smith, @aurimasv and @rmzelle. Maybe some of them can help out, e.g. to clarify what metadata are needed by reference managers.
Also added specific issue regarding software citation support in Citeproc/Citation Style Language: https://github.com/force11/force11-sciwg/issues/6
Some information about how to cite software from common citation styles I have found:
In BibLaTeX there is a special entry type for software which uses also the field version
, e.g.
@software{hadoop,
author = {{Apache Software Foundation}},
title = {Hadoop},
url = {https://hadoop.apache.org},
version = {0.20.2},
date = {2010-02-19},
}
However, this entry type is an unsupported entry type which means that it is treated the same as misc
in the default styles from BibLaTeX.
It looks that at least APA would like to use [Computer program]
, so support of type (Software
or ComputerProgram
) is probably needed. I would also think that publishers like to make it easy to distinguish software from other works in reference lists.
The other property that is probably needed for software citation and usually not needed for citing articles is version
.
The above is consistent with the recommendations for data citaton.
Continuing the great discussion from https://github.com/codemeta/codemeta/issues/76