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

Feature: Include recommendations for authorship in guides #248

Open
1 of 3 tasks
munkm opened this issue Feb 21, 2022 · 1 comment
Open
1 of 3 tasks

Feature: Include recommendations for authorship in guides #248

munkm opened this issue Feb 21, 2022 · 1 comment

Comments

@munkm
Copy link
Member

munkm commented Feb 21, 2022

Our guides and checklists are very helpful for the writing process, what to include and what not to include, and how to write. I think it could be improved if we add some guidelines to who should be included as a coauthor vs. when to acknowledge them. For example, the conference abstracts checklist mentions authors opting in/out, but doesn't explicitly say how to choose/include coauthors. I think authorship can be tricky for new researchers to decide, and sometimes it isn't always super obvious.

I'm thinking something like https://casrai.org/credit/ could be a nice addition to our writing guides. Maybe we could link to this as a good practice in deciding coauthorship.

I'm submitting a ...

  • bug report
  • feature request
  • question

Expected Behavior

We should include additional information about authorship expectations in arfc in the guides

Actual Behavior

I couldn't find this information easily

How can this issue be closed?

This issue can be closed if we include some information on (co)authorship guidelines in our writing guides.

@munkm
Copy link
Member Author

munkm commented Oct 30, 2022

The previous link I used is not valid anymore. Instead we should use something like the CRediT taxonomy: https://credit.niso.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant