Feature request: send only Article Text component to iThenticate

[tmrozewski-york]

OJS 3.3.0.10
iThenticate plugin 1.0.5.1

I'm piloting use of the iThenticate plugin for a couple journals I host. I have noticed that some journals routinely receive multiple non-manuscript files alongside the manuscript in the Submission process. These can include cover letters, ethics reviews, figures, or other. The plugin sends these indiscriminately to iThenticate for review.

Since there is a per-document cost to use iThenticate, would team consider updating the plugin so that only the Article Text component of a submission is sent to iThenticate for review? In the 8 months of our pilot to date, I note that only about 50% of the documents sent to iThenticate for review are article manuscripts that need to be screened, so there is a real cost associated with this. Thanks!

[asmecher]

@tmrozewski-york, can you have a look over #4 and see if it resolves this question?

[tmrozewski-york]

@asmecher it doesn't quite address the question directly, but I think that what you propose for 3.4 in that thread is a fantastic idea no matter what and it's something that I would love to see implemented

I'm talking here about which Article Components are sent to iThenticate. We may wish to continue screening all manuscripts upon submission, and in this case the solution you linked wouldn't help.

[twakeford]

A big thumbs up from us....having all files sent to iThenticate is going to be a big cost burden. Having options to limit which files are sent, based on the component, is the ideal solution for us.

I think that the issue of when to send files to iThenticate should be kept separate from the issue of what to send to iThenticate. I can see why some journals may want to have more flexibility on when they send and whether this is manual or automatic, but the issue will still exist that there will be lots of files where it isn't useful/desired to send to iThenticate (permissions, tables, cover letters, preprint reviews, datasets etc may all be legit 'text' files but the journal/publisher wouldn't necessarily want them checked and it will increase costs dramatically if they are all sent).

If we can link to Components then this gives the journal better control over the content and costs of using the plugin..

e.g.

[tmrozewski-york]

Thanks for the backup @twakeford - in our year-long pilot, we found that the plugin sends on average 2.6 documents per submissions. 160% increase in usage cost is pretty significant!

[touhidurabir]

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 .