[ORCiD] | Publishing workflow, Unauthenticated ORCiD - During imports of published material it can bypass the ORCiD authrentication process and block new versions from being published

[Tribunal33]

Description:

• Include specific context details that have been discovered that surround this developer task.
• Link related tickets
  This is a ticket on fixing an issue when importing published materials with contributors who have ORCiD ids but have not been authrenticated by our system. Not sure if this occurs during updating versions with existing contributors as this could be due to integration with ORCiD into the core.

The issue becomes more noticeable when you have a published article and you unpublish it then try to publish it again. The contributors of the imported article will have the unauthenticated ORCiDs

Then when you publish you will be given this message which will block republishing until all the contributors have authrenticated.

Steps to test the changes:
These steps can include user interactions, database queries and API requests

1. Prereqs: Must have a published article with contributors with valid ORCiDs imported into the journal
2. Login as an JM/JE/admin role
3. Select Published filter from the dashboard
4. Unpublish the article
5. Publish the article (this will give the warning above)
6. Can also check the Publication > Contributors > {Contributor} Edit > ORCiD ID section for unauthenticated value
7. Should return '...'
   Solution: What the proposed solutions are and additional affected areas

Unsure what the solution would be. Currently to get around this you can disable ORCiD altogether and then publish but seems like a bad practice. It, also, would seem impractical to send emails to all unauthenticated ORCiD members as there can upwards of 20 contributors. Waiting for all of them to be authenticated might take a long time.

What application are you using?
OJS, OMP or OPS version 3.5, 3.6 (main)

Additional information
Please add any screenshots, videos or other information we can use to understand this dev task report.

[kaitlinnewson]

Hi @Tribunal33, I believe it's required for ORCiD's to be authenticated before publishing (see #6971) and is implemented that way to follow recommended practices from ORCiD.

Would you say the issue here is that the ORCiDs are losing the authenticated status when a publication is unpublished?