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

Pushing peer review information into researcher's ORCID record #150

Closed
alexxxmendonca opened this issue Sep 9, 2020 · 3 comments
Closed

Comments

@alexxxmendonca
Copy link

Is your feature request related to a problem? Please describe.
ORCID Members that are using Member's API have the possibility to adding peer review information into a researcher's ORCID record when they performed a review for a given journal that is an ORCID member.

However, currently the ORCID plugin for OJS/OPS doesn't allow that.

Describe the solution you'd like
Allow journals and preprint servers that are ORCID members to "push" peer review information into researcher's ORCID record following these instructions:

https://members.orcid.org/api/workflow/peer-review

@alexxxmendonca alexxxmendonca changed the title Pushing peer review information into researcher's ORCID Pushing peer review information into researcher's ORCID record Sep 9, 2020
@amandastevens
Copy link

One of PKP PS's hosted clients requested this feature as a way to incentivize reviewers to contribute to a journal. "Some journals have a hard time incentivizing reviewers and are wondering if the ORCID plugin can be used to ingest review metadata from OJS into ORCID. This might be an additional incentive to potential reviewers."

@mew2232
Copy link

mew2232 commented May 3, 2021

We would love to have this feature to use across our OJS sites. Our student journals in particular find that offering recognition is key in attracting peer reviewers and Publons is not a good option for our program's size/budget. We would love to be able to utilize our ORCID membership through the same plugin that we use for authenticating author records so that we don't have to use our more than 1 of our 5 member API keys.

@withanage
Copy link
Member

This issue was addressed in #181.
Thus closing.

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

No branches or pull requests

4 participants