-
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
Turn off plagiarism checks for specific sections #12
Comments
I guess the title of this issue is misleading: Uploading for plagiarism checking should be dependent on article component. We do not want to check cover letters, supplementary materials etc., but the main article text. Thus, it should be configurable if uploads to a specific component are send for plagiarism check or not. (Excluding/including article sections - like Editorials - might also be a feature...) |
This is really an additional issue. A cover or contents page is not an article component. A cover letter is. However as I indicate, I can work around the things the editors upload like the contents page by skipping upload and adding the content as a galley so the additional level of control you suggest would also be useful. For supplementary material, it is a bit less clear as this can include content that really should be checked since it is part of what is published. If someone reuses a cover letter, who cares? It is not published. |
A new discussion started at #33 to gather more ideas/proposals and to finalise an improved implementation if possible . Any idea/proposal is highly appreciated . |
My journal has some sections like coverpage and frontmatter that should not be sent for plagiarism checking.
I could probably avoid this by creating a new submission and not uploading a file and only adding a file as a galley – presumably that would not be submitted to iThenticate?
If this would work, I can live with it but it would be better if sections that do not contain materials that should be checked could simply have passing to IThenticate turned off.
The text was updated successfully, but these errors were encountered: