Skip to content
Please note that GitHub no longer supports your web browser.

We recommend upgrading to the latest Google Chrome or Firefox.

Learn more
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

suggestions and comments #98

Open
wants to merge 1 commit into
base: master
from
Open

suggestions and comments #98

wants to merge 1 commit into from

Conversation

@danielskatz
Copy link
Collaborator

danielskatz commented Jan 10, 2020

No description provided.

@danielskatz danielskatz requested a review from npch Jan 10, 2020
Copy link
Collaborator

npch left a comment

What are your thoughts on the comments I've made?


Citing software helps further research and improves access to research software in order to:

- support proper attribution and credit
- support collaboration and reuse
- enable reproducibility of findings
- foster faster and more efficient research progress, and
- [DSK: this seems to duplicate the statement above the bullets] foster faster and more efficient research progress, and

This comment has been minimized.

Copy link
@npch

npch Jan 13, 2020

Collaborator

Perhaps. I think there's a difference, but maybe it needs to be more clearly worded. Should this be focussed on the "building on the shoulders of giants" aspect?

This comment has been minimized.

Copy link
@danielskatz

danielskatz Jan 13, 2020

Author Collaborator

yes, that seems reasonable.

- provide the means to share software and data with future researchers

FORCE11 has been developing guidance to support software citation. The Software Citation Principles (Smith et al 2016) were written to encourage broad adoption of a consistent policy for software citation across disciplines and venues. The Software Citation Checklist for Authors (Chue Hong et al 2019) and Software Citation Checklist for Developers provide more practical information for those seeking to improve their practice.
FORCE11 has been developing guidance to support [DSK: implement?] software citation. The Software Citation Principles (Smith et al. 2016) were written to encourage broad adoption of a consistent policy for software citation across disciplines and venues. The Software Citation Checklist for Authors (Chue Hong et al. 2019a) and Software Citation Checklist for Developers (Chue Hong et al. 2019b) provide more practical information for those seeking to improve their practice.

This comment has been minimized.

Copy link
@npch

npch Jan 13, 2020

Collaborator

Thanks - this was just an oversight.

This comment has been minimized.

Copy link
@danielskatz

danielskatz Jan 13, 2020

Author Collaborator

I assume you mean the 2nd reference? What about implement vs support?


- Creator: the authors or project that developed the software
- Title: the name of the software
- Identifier: a resolvable pointer to the software
- Identifier: a [DSK: persistent?] resolvable pointer to the software [DSK: or to a landing page?]

This comment has been minimized.

Copy link
@npch

npch Jan 13, 2020

Collaborator

My view here is that whilst we should make it clear that PIDs are better, it is the provision of a resolvable identifier that is the significant cultural change. I agree on the point that it could point to a landing page, but we need to write that in a term that someone unfamiliar with PID metadata would understand.

This comment has been minimized.

Copy link
@danielskatz

danielskatz Jan 13, 2020

Author Collaborator

Maybe we could say "Ideally, this would be a persistent pointer to a landing page, similar to a DOI for a paper that points to a page about the paper rather than directly to the PDF"

@@ -30,6 +30,8 @@ It may also be desirable to include information about three optional properties

### Software Citation Examples

[DSK: should we use a more common package as an example?]

This comment has been minimized.

Copy link
@npch

npch Jan 13, 2020

Collaborator

That would be fine - I basically made up three fake pieces of software using the Loren Ipsum generator. I would want any software to be broadly recognised by everyone reading the software, and to make sure that the recommended citation for that software wasn't at odds with what would be here, which would lead to confusion.

@danielskatz

This comment has been minimized.

Copy link
Collaborator Author

danielskatz commented Jan 13, 2020

Overall, this isn't really necessarily a PR but more feedback - feel free to close the PR and accept any of the comments you see as helpful by making changes directly to the document

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.