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

Allow a journal's editorial to authenticate and display ORCIDs #7406

Open
NateWr opened this issue Oct 27, 2021 · 2 comments
Open

Allow a journal's editorial to authenticate and display ORCIDs #7406

NateWr opened this issue Oct 27, 2021 · 2 comments
Assignees
Labels
Enhancement:3:Major A new feature or improvement that will take a month or more to complete.
Milestone

Comments

@NateWr
Copy link
Contributor

NateWr commented Oct 27, 2021

Describe the problem you would like to solve
Journals want to increase trust in the authority and prestige of their editorial team. They need a third-party to validate the claims they make that particular scholars perform editorial roles at the journal.

Describe the solution you'd like
Allow a journal's editorial team to authenticate their relationship with the journal through their ORCID profile. A journal manager would be able to enter the ORCID for each editorial team member. That individual would then receive an email asking them to confirm their relationship to the journal and authenticate it through ORCID. The journal would then be able to link to each team member's ORCID profile, where details of the relationship would be present.

The journal settings would need to permit journals to add, edit and delete records for each editorial team member. These records need to support both authenticated ORCID profiles and individuals without ORCID profiles. Where an ORCID profile exists, details such as name and affiliation should be taken from the ORCID profile. Where an ORCID profile does not exist, it should be possible to enter the person's name and affiliation directly.

@willinsky suggests the following distinct roles for editorial team members: Editor in Chief, Editors, Editorial Team Member.

The journal's webpage that shows the editorial team would need to be able to automatically list the team members, but also needs to be flexible enough to support cases that are not covered by the editorial team records. These include:

  • Historical team members for which active dates may be unknown or not specific (eg - Winter 1982 - Summer 1991).
  • Editorial relationships that are not captured by the historical Chief/Editors/Team distinction (eg - editorial collectives).

I suggest that the existing text field for the editorial team page be kept as-is, but with a variable (eg - {$editorialTeam}) that can be inserted to automatically populate the page with a list.

Who is asking for this feature?
Journals that struggle with the perception of being predatory or low-quality. This is part of the Integrity Initiative project led by @willinsky

There have also been community requests to better track the history of the editorial team (ie - who served when). This issue would facilitate that, though it is not part of the initial scope.

Additional information
At the current time, ORCID does not display editorial relationships on their scholar profile pages. This work can not begin until ORCID has added such support.

@NateWr NateWr added Enhancement:3:Major A new feature or improvement that will take a month or more to complete. Grant Requirement labels Oct 27, 2021
@NateWr NateWr added this to the 3.5 milestone Nov 30, 2021
@Devika008
Copy link

I have integrated ORCID iD verification with inviting users to take a role in OJS and the flow and UX/UI for it can be found here: #3022

Further to this issue, I worked with @willinsky, @bozana, @asmecher and @jardakotesovec to further the integrity initiative and display the users association with the journal under a setting in "Users & Roles" section called the Masthead. A new tab will be added for the same in the section and the landing page will look like:

image

On clicking "View" under any users name will lead to the following page:

image

Notes:

  1. When we kickoff the JII initiative, it will be a plugin. Those with the JII plugin, will have "appearing the masthead" as a compulsory option when adding users to the roles since they are endorsing the PFL as well. So the option to toggle between "appearing" and "not appearing" from the user invitation process will be switched off. However, there could be exceptions wherein the from the settings we can turn off the compulsory appearance of certain roles like assistant editors on the masthead. But the editors and board membership are required [to be on] the Masthead for JII.
  2. Those who are not yet endorsing PFL or JII, we will still show them an option for "appearing in the masthead" but it can be fidgeted with wrt to toggling between appearing or not appearing in the user invitation process. We still would request and encourage editors and board membership are required [to be on] the Masthead.
  3. Reviewers will be listed on the Masthead only when the review is submitted by them.
    Masthead records will only be for users who can provide consent to their names being displayed. No historical data wrt users being deceased or unable to give consent can be added to the masthead by the Journal Manager. However, if the user has been a part of the Journal for years prior to JII being initiated and has the means to provide consent, then that user could be displayed on the Masthead.

@bozana please do add anything you feel I've missed in this.

This was referenced Aug 31, 2023
@bozana
Copy link
Collaborator

bozana commented Aug 31, 2023

@Devika008, thanks a lot! That all sounds and looks great!
I created a new issue that will consider that part of masthead management: #9271, and copied your comment there.
This issue is rather for the user ORCID identification and update of user's ORCID profile (with the masthead services), that we still wait for and that we will probably leave for the end.

EDIT: And the main JII Masthead issue is here: #8957

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement:3:Major A new feature or improvement that will take a month or more to complete.
Projects
Status: In Progress
Status: Under Development
Development

No branches or pull requests

3 participants