-
Notifications
You must be signed in to change notification settings - Fork 33
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
[FEATURE] add citation information via CITATION.cff #256
Comments
Template should be something resembling this:
For the authors, how do we want to handle this? Do we want to list ESIP STC, or individuals? I should think we want to list individuals -- we do participate in a credit economy. If I run
which I assume is a subset of what is depicted on Insights/Contributors However, this does not capture users who created, or commented, on issues or discussions, reviewed PRs, or contributed to discussion at meetings -- STC monthly meeting and/or January and July ESIP meetings. It would certainly make sense to include these Need to investigate if there is a sane way to automatically generating It seems we could also add the previous paper citation (Raskin and Pan, 2005) and designate one as preferred, one references the other, or perhaps to request both be used. Anyone have recommendations or thoughts on this? |
I love the concept of .cff files! I hadn't heard of this before. I do think we need to include more that just the committers to the author's list. Also, I hate using group names, as I've actually had to prove that I was a member of a group that did something and I never want to go through that again! So I hope you have luck with getting a contributors list out of the github api. If not, you could just do what the schema.org group did, which was ask folks to add themselves to a list kept in a github issue. That way, if you don't care and don't pay attention, you don't end up in the citation! Raskin and Pan, 2005 would not be the preferred citation! In my mind this, following the ESIP endorsed convention, should be like a new edition of a book, which can have an entirely new set of authors, etc. Yup, the version number has to be part of the citation... I think it is fine to include the previous paper as part of the "reference" list for this version of the SWEET citation; but am wondering if the .cff concept includes reference lists? And if not, where should those be kept? |
Agreed.
This looks like the easiest option. |
Updateoutput of git shortlog -ns --all (corrected for duplicates):
The above list accounts for all committers from repository creation until today. Anyone in the above list who would like to be acknowledged for their contribution -- e.g., included in the CITATION.cff file -- please reply to this issue using the following pattern:
or edit the associated PR directly. While this circulates, @brandonnodnarb will compile a similar table of contributors -- e.g. users who have contributed to issues, reviewed PRs, etc. without actually committing to the repository. |
Thanks, @brandonnodnarb 👍🏻
|
I'm sure 344342f isn't worth citing... |
Yeah, @bradh wrong link. Apologies. |
authors:
- family-names: Keil
given-names: "Jan Martin"
affiliation: "Friedrich Schiller University Jena"
orcid: "https://orcid.org/0000-0002-7733-0193"
|
The following is a list of everyone who has contributed to SWEET development by adding or commenting on an issue.
If anyone on this list would like to be added to the CITATION.cff file please reply to this issue completing the pattern above, or or edit the associated PR directly. |
Thanks folks. Great to see a lot of activity 👍 |
I am not sure my limited participation warrants authorship here, but in the interest of not holding things back:
|
Hey all good initiative, however, I don't think posting a few issues or discussions merits authorship or reference. If I ever had to occasion to really contribute to SWEET I would add my details but I don't think I have, so I don't intend to. Best of luck with the project. |
Agreed - I don't think recording an issue should count towards authorship at all. It's reporting a problem! |
I can't say I disagree with either of you. The previous tables were largely exploratory on my part. ProposalUse the CITATION.cff file to cover the maximum extent of authorship for the repository from time immemorial. All the authors, which in this case would be anyone who committed to the repository, or the second table I posted, who wish to be included will be added using the 'authors' tag on the CITATION.cff file. As the CITATION.cff standard has no 'collaborator' or 'acknowledgement' tag we will leave it at that for the time being; until the next release For the next SWEET release (3.6) we will incorporate a more standard workflow by which the authors and collaborators are properly added to the Zenodo metadata for that version -- version 3.6, and only 3.6. This process will mint the DOI for version 3.6 with the proper metadata and citation information. At this stage we can keep the CITATION.cff file should anyone want to cite the repository, but we will add the version information (3.6) to the CITATION.cff file and specify that the latest version is the preferred citation. The next SWEET release target is June, prior to the next ESIP meeting. Separately, I can investigate querying users who contributed to closed issues, more specifically users who contributed to issues closed due to a PR -- i.e., a change to SWEET not an issue that was closed for another reason (stale, irrelevant, etc.) When this is sorted we can discuss further additions. |
Thank you Brandon!!
For my limited participation:
```
authors:
- family-names: McKellar
given-names: "John Lindsay"
affiliation: "Geological Survey of Queensland"
orcid: https://orcid.org/0000-0001-5489-9590
```
Cheers,
John
|
authors:
|
see: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files#about-citation-files
This topic can be discussed at the monthly ESIP STC meetings.
The text was updated successfully, but these errors were encountered: