ADS is currently generating incorrect BibTeX records for citations to code entries in the ASCL. This will be fixed, but in the meantime, here's an example of what is being generated and how to fix it, courtesy of Mark Taylor and Alberto Accomazzi.
Hitting the "Bibtex entry for this abstract" button on the ADS page for the ASCL Sherpa entry gives:
@ARTICLE{2011ascl.soft07005F,
author = {{Freeman}, P. and {Nguyen}, D. and {Doe}, S. and {Siemiginowska}, A.
},
title = "{Sherpa: CIAO Modeling and Fitting Package}",
journal = {Astrophysics Source Code Library},
year = 2011,
month = jul,
pages = {7005},
adsurl = {http://adsabs.harvard.edu/abs/2011ascl.soft07005F},
adsnote = {Provided by the SAO/NASA Astrophysics Data System}
}
The identifier that should be in "pages" is "1107.005" as ASCL IDs are all of the form yymm.nnn. However, a better Bibtex entry format is:
@ARTICLE{2011ascl.soft07005F,
author = {{Freeman}, P. and {Nguyen}, D. and {Doe}, S. and {Siemiginowska}, A.
},
title = "{Sherpa: CIAO Modeling and Fitting Package}",
journal = {Astrophysics Source Code Library},
year = 2011,
month = jul,
eprint = {ascl:1107.005},
adsurl = {http://adsabs.harvard.edu/abs/2011ascl.soft07005F},
adsnote = {Provided by the SAO/NASA Astrophysics Data System}
}
Note the removal of "page" and the addition of the "eprint" field.
After running LaTeX and BibTeX on it, it should generate an entry in the .bbl file that looks like this:
bibitem[{{Freeman et al.}(2011)]{2011ascl.soft07005F}
{Freeman}, P., {Nguyen}, D., {Doe}, S., and {Siemiginowska}, A. 2011
Astrophysics Source Code Library, eprint{ascl:1107.005}
My thanks to Dr. Accomazzi and Dr. Taylor for their work on this!
ASCL has a display table at ADASS XXII; below is the short presentation we are running at the table.
Several of the ASCL's Advisory Committee are panelists for a Birds of a Feather session that seeks answers to the following questions:
How do we ensure code release is recognized as an essential part of assuring reproducibility of research?
How can the community change the culture so developers will release their programs?
What can we do to ensure code authors receive credit for writing and releasing their software, and encourage them to release it even if it's "messy" code?
How do we reduce expectations of support when a developer does not wish to (or cannot) take on that role after program release?
What role might journal publishers and funding agencies have in furthering code release, and how can the community influence them to take on that role?
How can universities be convinced to change policies which prohibit software publication?
Can funding agencies and publishers encourage documentation of programs, and if so, how?
Got answers? Ideas? Comments? Please share!