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

Identify the context of the reference #24

Open
npch opened this issue Apr 3, 2018 · 3 comments
Open

Identify the context of the reference #24

npch opened this issue Apr 3, 2018 · 3 comments

Comments

@npch
Copy link
Member

npch commented Apr 3, 2018

Ideally, we'd like to know what the context of the reference to a piece of software in a paper is, for example:

  • it's software created by the author to do a key piece of work for the paper
  • it's software created by the author that is described by the paper
  • it's software used by the author to do the work in the paper

as we might hypothesise that the reusability of each type and likelihood that they're updated might be different.

@npch
Copy link
Member Author

npch commented Apr 3, 2018

This is required by some of the work proposed in #19.

@andreww
Copy link

andreww commented Apr 8, 2018

Looking to see if we have a reference to the paper from the github repository would give us evidence that the paper falls into one of the first two categories and not the third. We could get that from the citation file (if it exists). See #18. However, if such a link does not exist it does not mean that the software does not fall into one of the first two categories.

@npch
Copy link
Member Author

npch commented Apr 8, 2018

That might work. Unfortunately, at present most repos won't have citation files of any sort. However a quick sample suggests that some repos do have a link to the paper in the readme - perhaps we could look for the DOI of the paper in the readme?

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

2 participants