Recently, the old Plagiabot system on Wikimedia Cloud was turned off, so no new Turnitin matches were being added to the database that ruby-suspected-plagiarism.toolforge.org connects to. I updated the toolforge tool to connect to the replacement database that was set up for the continued operation of CopyPatrol. This one does basically the same thing, but there are a few important changes:
the IDs for the reports are now UUID instead of integer (so they couldn't be stored in the Revision.ithenticate_id column anymore, without migration headaches).
the reports are only supposed to be accessed via CopyPatrol
I originally implemented the suspected plagiarism system before I built out the Alert pattern that we've used for pretty much all the similar features that came afterwards, so revisions that might be plagiarism didn't actually have Alert records, just emails and a few front-end features for surfacing them. I've taken this opportunity to re-implement the tracking of possible plagiarism to use a standard Alert, so those cases will show up alongside other alert types, both at the individual course level and system-wide. Rather than trying to update the frontend features to use Alert data instead of the old revision-scoping approach, I've just ripped out all the frontend stuff; we'll treat them like other Alerts now.
Let's make plagiarism reports work again!
Recently, the old Plagiabot system on Wikimedia Cloud was turned off, so no new Turnitin matches were being added to the database that ruby-suspected-plagiarism.toolforge.org connects to. I updated the toolforge tool to connect to the replacement database that was set up for the continued operation of CopyPatrol. This one does basically the same thing, but there are a few important changes:
I originally implemented the suspected plagiarism system before I built out the Alert pattern that we've used for pretty much all the similar features that came afterwards, so revisions that might be plagiarism didn't actually have Alert records, just emails and a few front-end features for surfacing them. I've taken this opportunity to re-implement the tracking of possible plagiarism to use a standard Alert, so those cases will show up alongside other alert types, both at the individual course level and system-wide. Rather than trying to update the frontend features to use Alert data instead of the old revision-scoping approach, I've just ripped out all the frontend stuff; we'll treat them like other Alerts now.