Users not properly authenticated with ORCID?

@rossella.filadoro We noticed the same thing. While the intention of getting more contributors to connect their ORCIDs to their work is a good one, stopping publication when the contributors have not authenticated their ORCIDs is having the opposite effect. The editors are just turning off the ORCID plugin so they can publish, rather than having to go back through ALL the contributors for that issue and figure out which need intervention.

It would be helpful if there was an alert to editors at some point earlier in the process, with enough information so that they know who to contact to request that they authorize their ORCID. Having the alert at publication is resulting in fewer ORCIDs being registered with our journals.

(And besides, isn’t the inclusion of an ORCID optional? Why is an optional identifier stopping publication?)

– Marianne

1 Like

What was the end result of your consultation with orcid.org, @Dulip_Withanage?

Their suggestion was using only authenticated Orcid ids. But we disabled the strict Validation and released newer versions, as far as I can remember. Now @ewhanson is overlooking the development and may be he can verify it

Thank you for your work on this @Dulip_Withanage !

Hi everyone, I think that a fix as been published for this issue but not validated yet: fix: fix sending orcid validate email on create author action during … by zielaq Ā· Pull Request #321 Ā· pkp/orcidProfile Ā· GitHub

1 Like

Are you disabling the strict validation in general or only for the usecase where the content is republished (Marie-Helene’s usecase #2)

I am using OJS 3.4.0.8 and we are still running into the problem where users haven’t authenticated an ORCID, so editors are prevented from publishing the article.

In which version (of the plugin? of OJS?) is the strict validation disabled?

Hi everyone,
We are currently using OJS version 3.4.0.8, too, and have the same problem. As soon as one of the authors does not authenticate the ORCID entered by the corresponding author, the article cannot be published. The problem is that I cannot recognise which author is responsible. It would help to know which author(s) I might have to remind again.

1 Like

Ideally, an alert to editors earlier in the process would be ideal, so that they can notify the authors to validate their ORCIDs before the I-have-to-publish-NOW-before-I-leave-for-the-summer-tomorrow crunch is here.

We have now discovered that the problem occurs when the submitting author already enters the ORCIDs of his co-authors. In this case, authentication must take place. If no ORCIDs are entered, all co-authors will also receive an email. However, the article can still be published, even without the respective ORCID, if the co-author does not respond.
In my opinion, it would therefore make sense if the ORCID could not be entered by the submitting author during the submission process. Or am I seeing this wrong?

@Sleipnir Since we have no way of knowing if a submitter is entering ORCIDs for their co-authors, we hadn’t been aware of this nuance. I don’t want to discourage submitters from adding ORCIDs, because it is a normal behavior in just about any other publishing system. It would be great if the ORCID plugin in OJS was robust enough to send emails for all unauthenticated ORCIDs, no matter what the source is.