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

Introduce CRediT roles (NMS suggestion) #547

Open
grahamjevon opened this issue Jun 10, 2024 · 0 comments
Open

Introduce CRediT roles (NMS suggestion) #547

grahamjevon opened this issue Jun 10, 2024 · 0 comments

Comments

@grahamjevon
Copy link
Collaborator

Summary of CRediT

CRediT (Contributor Roles Taxonomy) is a high-level taxonomy, including 14 roles, that can be used to represent the roles typically played by contributors to research outputs. The roles describe each contributor’s specific contribution to the scholarly output.

How it might work in Hyku

Currently we have the creator fields (with no option to specify roles). We also have the contributor fields (where a single role can be specified for an individual, such as supervisor, data curator, etc). The proposed development would do the following:

  1. Remove the field distinction between "creators" and "contributors" (and "editors"). Instead have just one set of fields for human involvement (probably named "contributors")
  2. Remove the existing controlled list of "contributor roles" (which includes, for example, "project leader", "supervisor", "data curator".
  3. Introduce a new metadata field with a controlled list of the 14 CRediT roles
  4. Ability to attribute more than one CRediT role to an individual

Additional considerations

  • How will this impact compatibility with the Datacite metadata schema?
  • Is there consensus to make this change amongst all tenants?
  • Can it be optional on a tenant by tenant basis?
  • How stable is CRediT? Will it be around for the long term? Is there wider sector support for it? If not, should we lead the way in implementing it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Partner Wishlist
Development

No branches or pull requests

1 participant