Comments (8)
Alternatively, use the CRediT taxonomy, or Scoro ontology, to be investigated.
from citation-file-format.
Does any of these include free form field? They all seem to aim at strict ontology/taxonomy. My community needs something where we can specify which feature each person implemented. Please, let me know whether or not this is part of this suggestion of if it it elsewhere, if not I will create a new ticket with more details.
from citation-file-format.
Hi @wenzeslaus, thanks for the comment.
It seems that for your use case, if you can strictly separate features in the source code, one CFF file per feature might be something feasible.
Other than that, a free form field is a very good suggestion for special cases such as yours, and as a fallback.
What is your community if I may ask?
Also, note that this isn't something that's currently implemented, but will be in the future.
from citation-file-format.
Hi, I'm working on GRASS GIS and its modules. Here is an example of authors section (not a complete example, but shows people and features).
Francesco Tonini (original R version)
Zexi Chen (C++ version)
Vaclav Petras (parallelization, GRASS interface)
Anna Petrasova (single species simulation)
I would like to capture the same in the CITATION.cff file.
However, this is one module (aka function, command, extension, ...), not the whole GRASS GIS, so there would be one CFF file for module which would act, for the purpose of the citation, as a separate software (we go to the dependencies issue here). One CFF file per feature thus seems too many CFF files and the scope
key does not seem appropriate either because the contributions build on top of each other (esp. if authors may include people that have not contributed lines of code, but have contributed as testers, designers, reporters, managers (Give credit) and documentation in our case). I'm currently working a tool to extract the information from documentation and convert it to CFF (kind of #18 I guess).
I can still open another ticket for this if you prefer, just let me know.
from citation-file-format.
Hi @wenzeslaus, I'm in the process of answering your colleague P. L. who had inquired about this as well via email. I'll cc you in that email.
from citation-file-format.
On-topic, here's an initial crosswalk of contributor roles by Ted Habermann: https://zenodo.org/record/4767798. This may come in handy when developing/deciding on a vocabulary (if indeed there should be any).
from citation-file-format.
The upcoming release 1.3.0 of the CFF schema adds a key contributors
which can help solve the problem where repository owners
- gift authorship to contributors even when the contribution is insignificant, simply because there is no other mechanism to give thanks OR
- omit their contributors entirely, thus giving the impression that only they should be credited with the perceived benefits of the software.
However, the current issue as well as some others
- Allow differentiation between authors/contributors #84
- Create roles as a simple way to record contribution roles? #112
suggest that CFF needs more granularity in differentiating the specific roles that each contributor had. I'm wondering, who or what would benefit from the additional level of detail? How would these metadata be used?
from citation-file-format.
Locking conversation, please continue discussion in #112.
from citation-file-format.
Related Issues (20)
- Accompanying paper citations HOT 2
- WhatsApp HOT 1
- Bump actions version in workflow files HOT 1
- Anonymize test examples HOT 1
- Update testing section in README.dev.md HOT 1
- How should CFF store different parts of someone's name? HOT 3
- Should `contact` really be named `contacts`?
- Consider merging `license-url` into `license`
- Consider dropping the url based root keys in favor of `identifiers`
- Review README files used in testing
- Review changelog HOT 2
- Consider supporting only OSI-approved licenses HOT 3
- Consider letting a reference's version be able to express an applicable version range HOT 1
- Add support for `resourceType` from DataCite in Zenodo
- Consider allowing internal >1 whitespaces in `strictish-string` HOT 1
- Consider the hardwiring of `cff-version` values in the schema HOT 4
- Schema extension for Open Educational Resources
- Add link to cff2toml on README.md
- Cross-referencing a `.cff` for the reference section HOT 3
- TypeScript based website to convert BibTeX into GitHub ready CFF file
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from citation-file-format.