Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback requested: a short implementation examples paper #155

Open
arfon opened this issue Sep 22, 2016 · 7 comments
Open

Feedback requested: a short implementation examples paper #155

arfon opened this issue Sep 22, 2016 · 7 comments

Comments

@arfon
Copy link
Contributor

arfon commented Sep 22, 2016

As one of the four final actions of this working group we (@arfon, @danielskatz & @kyleniemeyer) are considering writing a short implementation examples paper that demonstrates how to implement the software citation principles in a small number of common situations/scenarios. For example:

How to make your software citable

  • Discuss GitHub to Zenodo linkage and required metadata

In a paper

  • When the software being cited has a DOI
  • When the software being cited doesn't have a DOI (but is perhaps on e.g. GitHub)
  • Citing commercial or closed source software
  • Citing software that is only available as a service
  • When the software being cited has a paper and a DOI
  • What does a bibTeX entry look like for all of the above (fixes bibtex entry #148)

We'd like your help in two main ways:

  • If you have suggestions for which small number of use cases would be most valuable to discuss in this paper then please suggest them here (see this section for the full list of use cases we discussed).
  • If you're interested in helping substantially with this effort (i.e., actually willing to help write a paper with us) then please say so on this thread.
@nalsi
Copy link

nalsi commented Sep 22, 2016

Hi Afron,

My name is Kai Li. I am a PhD student in Information Science at Drexel University. I have never talked in this group. But I am very interested in this project, which is an area I am doing some studies myself. Two other faculty members in my school and myself recently finished a case study on the citation of LAMMPS, a popular software in material science.

So I would love to participate in this project if possible!

@tomcrick
Copy link
Contributor

Happy to help with the writing of the paper.

@ljhwang
Copy link
Contributor

ljhwang commented Sep 22, 2016

+1

@iliant
Copy link
Contributor

iliant commented Sep 22, 2016

Hi Afron,

As I have mentioned at WSSSPE2, in the world of materials modelling software the most popular cases is that the software doesn't have a DOI but has a paper. The code can be open source, closed source and most often it is on an open source restrictive licence (artistic, preserving a sole distribution body, commercial rights, intellectual rights). I am happy to describe the rational behind these mainstreams.

Also, within my institution there are practices that unfold onto DOI + possibly a paper for service oriented software as well as citing a web-page for numerical libraries. I am sure I can provide example of those or find a best person to provide information.

@mhucka
Copy link
Contributor

mhucka commented Sep 30, 2016

Thank you for organizing this effort. I'd be interested in contributing to this effort in some small way, such as helping with the paper or specific citation formats (perhaps related to #148).

@cm-j0nes
Copy link
Contributor

cm-j0nes commented Oct 5, 2016

I am really interested in the area of transferring theory to practice and am happy to contribute to writing the paper.

I have worked with others in my organisation who have tried to encourage software citation, and have used them as an example in the past - if you think this would be useful, then I can contact them to see if they are interested in contributing this as a use case.

@lnielsen
Copy link
Contributor

We're happy to help out with the "How to make your software citable", especially given the latest update to the Zenodo GitHub integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants