CreDiT contributions
Melissa37 commented on May 15, 2019
Problem / Motivation
The CreDiT taxonomy provides a way to encode contribution information inside article XML files. The taxonomy identifies the specific nature of an individual’s contribution with respect to the research material at hand. The purpose of CRediT is to provide transparency in contributions to scholarly published work, to enable improved systems of attribution, credit, and accountability.
@Melissa37 Melissa37 added this to Post-public review working in Roadmap on May 15, 2019
@Melissa37 Melissa37 moved this from Post-public review working to Done in Roadmap on Jun 11, 2019
@Melissa37
Contributor
Author
Melissa37 commented on Nov 6, 2019 •
From the CRediT taxonomy documentation
https://casrai.org/?s=Credit
Degree of Contribution Optional – Where multiple individuals serve in the same role, the degree of contribution can optionally be specified as ‘lead’, ‘equal’, or ‘supporting’
MECA is adding this as specific use:
Data Collection
Perhaps we should update the recommendation with this?
But maybe wait until “other” is added?
@kelly-mcdougall For info 🙂
@Melissa37
Contributor
Author
Melissa37 commented on Nov 6, 2019
Requested “other” is added to the Taxonomy
@Melissa37
Contributor
Author
Melissa37 commented on Jan 21
Comment via: JATS4R/JATS4R-Participant-Hub#130
I am currently looking at the CRediT recommendation. I have a couple of problems that I’m not sure if you can help with. I have read the discussion notes and I know there was talk about Casrai’s URLs and special characters. Having just tried, none of the URLs for contributor roles resolve to anything useful on their site (Not something for you but interesting nonetheless). In the published recommendations however there is a little confusion regarding the 2 roles that have special characters
In what I think is the JATS 1.1 sample, but labelled as 1.2 there is:
Conceptualization
Data curation
Formal analysis
Investigation
Writing – original draft
https://orcid.org/0000-0003-2354-0408 Delon Wright Data curation Writing – review & editing
Where “Writing – original draft” has URL with [space][hyphen][space] and the second [space] replaced with [underscore] in both instances. In the “Writing – review & editing” the spaces have been replaced with underscore bit the hyphen and & have been retained escaped. Is this a mistake?
Did the group have an overall recommendation with regard to the URLs for these 2 awkward terms and their identifiers? While it seemed to be discussed it did not get mentioned in the recommendations.
It seems to me without resolution, it would be difficult to validate accurately, if these vocab-identifiers are not resolvable. Will Casrai update the URLs to match what J4R have recommended?
Also noticed that in example
Writing – Original Draft
Where vocab-term = “Writing – Original Draft”, but table of terms and urls has “Writing – original draft”. Does case matter for machine readability?
Any advice gratefully received.
@kelly-mcdougall have you got any advice?
@meden-cup FYI. I’ve moved it here. Vincent Lizzie from TandF was the one who knew the most about this and might be able to help?
Also NISO will also be creating a new work item to formalize the CRediT (Contributor Roles Taxonomy) [https://casrai.org/credit/] as an ANSI/NISO standard and establish a NISO Standing Committee to continue education and outreach efforts and foster continued development of the taxonomy.
This should be raised with that group when it forms.
Sorry to not be more help myself!
@hubgit
Member
hubgit commented on Feb 4
Having just tried, none of the URLs for contributor roles resolve to anything useful on their site
I asked on Twitter and it seems that the URLs (which used to resolve) should resolve again soon:
@hubgit
Member
hubgit commented on Feb 4 •
Did the group have an overall recommendation with regard to the URLs for these 2 awkward terms and their identifiers? While it seemed to be discussed it did not get mentioned in the recommendations.
The JATS spec for role has this example:
Example 3
Special characters in CRediT attribute values need to be given as Unicode character references. In narrative text, Unicode character references, general entities, or characters may be used.
Anne Berns Writing – Original Draft
so it’s clear that the (unfortunate) URL should be http://dictionary.casrai.org/Contributor_Roles/Writing_%E2%80%93_original_draft (with %E2%80%93 being an en dash).
@Melissa37
Contributor
Author
Melissa37 commented on Apr 1
From Kevin:
I think there may be a problem with the CRediT guidelines here: https://jats4r.niso.org/credit-taxonomy. In the Recommendations section, there are two sets of tagging examples: one for JATS v1.2 and one for v1.1. The first set of tagging examples for v1.2 seem fine. The second set of tagging examples are listed as being for v1.2, too, but I think this is a typo and should indicate v1.1 because it involves @Content-Type. The first example in the v1.1 tagging examples uses @Content-Type, which seems correct, but then the second example reverts to using @vocab-term.