Plagiarism Prevention Turnitin

Revision as of 08:25, 15 December 2010 by Daniel Wahl (talk | contribs)

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Plagiarism Prevention Turnitin.

Template:Moodle 2.0

Turnitin administration

Location: Administration > Plugins > Plagiarism Prevention > Turnitin

Activation of your Turnitin Account

  1. obtain a Turnitin Subscription from
  2. obtain an API Integration secret key. - once you have a Turnitin Subscription, to obtain this you will need to visit the administration panel inside your Turnitin account. - there may be an extra cost to have API activated on your account, but your account rep should be able to give you details on this.

Global Configuration of Turnitin

  1. Ensure Admin > Server > Environment indicates you have curl installed
  2. in the page Admin > Modules > Activities > Turnitin set the following:
    1. Tick the box "Use Turnitin Submission"
    2. Enter your Turnitin Account ID
    3. Enter your Turnitin Secret Key as obtained from your Turnitin Account Rep
    4. Elect whether to send students an e-mail to allow them to login to the site to view their submissions (this isn't necessary, and will likely cause your students more confusion, as all the information available in the website is available from your moodle site.) - even if no e-mail is sent, students can visit and use the forgotten password functionality on the turnitin site to get their password sent via e-mail. Admins can disable this by adding a prefix to all email accounts created - see below for details.
    5. Add an e-mail prefix if you don't want students to be able to access the reports on - it is advised that you allow the integration in moodle to control what your students see, however, if you allow them to login to they can bypass the settings made regarding when a report should be available. - it's also possible that they could potentially upload a file to instead of moodle, which you may not notice. It's reccommended that you put something in this box to make the e-mail addresses for students stored on the system invalid.
    6. Set a Course Prefix - this is not compulsory, however if you have more than 1 Moodle site connecting to the Turnitin API - eg a testing site, and a production site, then a prefix MUST be set, because Turnitin will only allow 1 course with the same name - and only 1 assignment within that course with the same name. - you will potentially get conflicts if this is not set.
    7. Set the Student Disclosure statement. - this is displayed to all students on the upload screen to notify them that the Turnitin system is in use.

Configuration of Turnitin inside Moodle Activity Modules

Assignment Module

(currently only available with the advanced file upload and single upload types)

  • Create a new Assignment within your course.
  • Enable Turnitin Submission


  • when testing the turnitin integration you should make sure debugging is turned on, as it will provide information regarding the process.
  • error codes recieved from the turnitin API are also logged in the mdl_tii_files table, so you can view issues with a production system.
  • each file that is going to be submitted to turnitin is added to the table mdl_tii_files - the field tiicode gives the "status" of the file, - there are 3 "good" states for this field:
  1. "pending" - this is a new file that has been uploaded to an activity module, and needs to be submitted to Turnitin (will happen next time cron runs)
  2. "51" - this is the turnitin API code for Successful upload - this means the file has been uploaded to Turnitin and we are waiting on an originality score,
  3. "success" - this is a file that has been submitted, and a score has been provided for it.

Any other response code in this field indicates an error state, see the Turnitin errors page for a complete list of codes.