Allow Journal Managers to invite users to adopt a role - ORCiD

[Devika008]

Hello,

Since #3022 (comment) was too big, upon discussion we decided to divide it into four smaller issues.

This fourth issue highlights the ORCiD prerequisite for the user flow of inviting editors, authors, readers, reviewers, etc to OJS. The information stated below reflects all the research, discussions and feedback received on this issue over the last few years along with some minor testing with a small user group at the Copenhagen Sprint.

WIP, PRs, and TODOs

PRs:

• pkp-lib: pkp/pkp-lib#9661 Allow Journal Managers to invite users to adopt a role - ORCiD #10679
• ui-library: pkp/pkp-lib#9661 Allow Journal Managers to invite users to adopt a role - ORCiD ui-library#460

Summary of requirement

1. In the “Users & Roles” section of the settings, we add a new “Invite user to take a role” action that can be used to invite any user to the journal OJS software based on an email address. The email sent will add the following:

• Invitation request along with details of the role, starting date etc.
• ORCiD verification details

2. Starting with 3.5.0, ORCiD Verification would not happen through a plugin. We're rewriting ORCiD support to be integrated into OJS rather than maintaining a plugin. The option to make ORCiD mandatory should be present as part of the 3.5.0 implementation; it shouldn't be necessary to write up a plugin to add the "make ORCiDs mandatory" checkbox.

3. If the JM/System Administrator/Editor has marked ORCiD verification as mandatory, then the email invitation sent will highlight that the verification is mandatory. If it’s not enabled then the ORCiD mandatory message on the email will not be shown

4. Mandatory or not, before the user is redirected to the ORCiD website to verify they have an option to skip the step. Since we cannot customize the ORCiD verification screen to show skip or not, the email will be the vehicle for communication.

5. If the user deny's access to ORCiD, they can go back anytime in their profile to authenticate it later on in the future

ORCID Journey in User Invitation process

a. Below is a sample of the email the user will receive informing them about ORCiD verification

b. After the user accepts the invitation, the user needs to first create an account on OJS

c. Once the account is created, in the next step the user is asked to chose whether they want to proceed with ORCID Verification or not

d. If the user accepts to verify ORCID, they are redirected to the ORCID Website to authenticate their ID

e. In the review screen, one can then see their ORCID iD with a verified logo to show that its connected

f. If the user chooses to skip ORCID verification, the following screen will be shown indicating that the user can verify via ORCID anytime through their profile

Over and above this invitation process, the landing page of Users and Roles will have indication of whether the user is ORCiD verified or not by ORCiD ID Icon

The editor can also search for the user via their ORCiD ID in the system and determine whether the user exists or not.

@bozana or @asmecher please specify anything I have missed