You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've used plot-likert in a recent publication (https://doi.org/10.5194/gc-7-201-2024), and at the proof-reading stage we had some discussions with the typesetter who insisted on putting a citation of all software in the reference list. However, we did not know how to appropriately cite this software, so ended up with
nmalkin, charlesbaynham, alaskamike, Maocx, rnikiforova, and valentynbez: nmalkin/plot-likert, GitHub [code], https://github.com/nmalkin/plot-likert/ (last access: 15 July 2024), 2024.
Perhaps you can add a CITATION file, so others can cite the software more easily? I expect that more journals will request adding software packages to reference lists
Great tool by the way; thanks for developing!
The text was updated successfully, but these errors were encountered:
We've used
plot-likert
in a recent publication (https://doi.org/10.5194/gc-7-201-2024), and at the proof-reading stage we had some discussions with the typesetter who insisted on putting a citation of all software in the reference list. However, we did not know how to appropriately cite this software, so ended up withPerhaps you can add a CITATION file, so others can cite the software more easily? I expect that more journals will request adding software packages to reference lists
Great tool by the way; thanks for developing!
The text was updated successfully, but these errors were encountered: