ORCID Plugin enhancements for OJS 3.1.2 and beyond

[withanage]

Following issues and enhancement requests are related, currently being developed or in discussion for the OJS 3.1.2 and 3.2 + support.

Description	Issue	Status	area
Issue publish	pkp/pkp-lib#5572	🆗	Issue
Sandbox iDs	pkp/pkp-lib#4893	🆗	Issue
datacite export	pkp/pkp-lib#4903	🚧	Issue
Empty URI after failed auth	#113	🚧	Issue
icon problem	https://forum.pkp.sfu.ca/t/orcid-icon-problem/53637	🚧	Forum
icon problem	https://forum.pkp.sfu.ca/t/ojs-3-1-2-1-orcid-icon-doesnt-show/54613	🚧	Forum
Option for emails	#112	🚧	Issue

[withanage]

Hi @asmecher @isgrim @gmejias

Here are the currently known issues related to OJS 3.1.2. Forum questions can be added here directly and the users are encouraged to subscribe to this issue.

@gmejias Feel be also free to add any ideas for UI betterments, so that we can gather them all here.

[nils-stefan-weiher]

PR for stable-3_1_2: #77

[librariam]

+1 from PKP|PS re #113 - encountered it on 3.2.1.1 (not sure of the ORCID plugin version at the time since I updated it to v1.1.2.6 after the bug happened).

[librariam]

+1 more from PKP|PS re #113 on 3.1.2.4, plugin v. 1.1.1.5
An added consequence here is that the incomplete URL in the ORCID iD field breaks Crossref XML export. There is no easy way to remove it without disabling the plugin.

[withanage]

Hi @librariam ,
Thanks for the info.
I will look into this issue in the next release.

[bibliothekswelt]

When an article is pushed to my ORCID profile via the ORICD plugin, it seems to be, that only the URL of the article is transmitted but not the DOI. Is it possible to transmit the DOI, too? We are synchronyzing our local repository with ORCID (for users which have an ORCID iD) but we are only using the DOI for this mechanism. If an article gets pushed to an ORCID profile it can make it's way to our local repository automatically when there's a DOI for the record in ORCID. It would be great, if the DOI can be added.

[librariam]

+1 more from PKP|PS re #113 on 3.2.0.2, plugin v. 1.1.2.3

[librariam]

@withanage do you have any update on #113 ? We get reports about it from editors fairly regularly and it's a pain to deal with after the partial URL is recorded. Thank you for taking a look!

[withanage]

@librariam #113 is closed. Thus closing this meta issue.