-
Notifications
You must be signed in to change notification settings - Fork 32
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
iThenticate v2 (CrossRef similarity check) support #52
Comments
@gljk, the current implementation of the OJS iThenticate plugin is based on this 3rd-party iThenticate library, which does not support the v2 API. I suspect it is no longer being maintained. We have some upcoming work to remove this dependency from the plugin and update to the v2 API ourselves; I'll update this issue with progress. If you're interested in doing some work on this yourself, please let us know and we'll make sure we coordinate. |
@asmecher PR has been updated as per requested changes. If all ok, I can start working porting these changes to |
@asmecher PR updated based on new EULA requirement and some good enhancement . see more details about the implementation details at #57 (comment) . Please review the PR again . |
…d webhook registration on settings update
… along with user notification system on webhook handle
…as part of plugins settings
…wer launch functionality
…tHandler hook call
…tHandler hook call for OPS
…uired and validation passes
…g of eula required and validation passes
…ne ithenticate check at submission time
#52 iThenticate API update and plugin update
#52 Plugin update with new iThenticate API integration
#52 Plugin update with new iThenticate API integration
My journal has recently got similarity check through CrossRef and the credentials we use for login to turnitin at our unique link https://crossref-[your member ID].turnitin.com do not seem to work with this plugin.
https://www.crossref.org/documentation/similarity-check/ithenticatev2-account-setup/
We have not been able to get the plugin working with iThenticate v2.
The text was updated successfully, but these errors were encountered: