Skip to main content
  1. Turnitin Guides
  2. Turnitin in an LMS
  3. Moodle
  4. LTI 1.3
  5. Configuration and administration

Turnitin's LTI 1.1 to 1.3 upgrade within Moodle: Recommendations for Feedback Studio administrators

Updated

In this guide:

  1. Stage 1: Vetting
  2. Stage 2: Testing
  3. Stage 3: Preparing
  4. Stage 4: Aligning stakeholders
  5. Stage 5: Deploying

 

As the Turnitin admin, we will be communicating with you periodically over the next year regarding best practices for upgrading from the Turnitin LTI 1.1 integration to the Turnitin LTI 1.3 integration in Moodle. Before we continue, please be aware that there are several Turnitin integrations available for Moodle for Feedback studio customers: Plagiarism Plugin, Direct V2, LTI 1.1, and LTI 1.3. You may have multiple integrations enabled in your Moodle environment. As such, please check with your Moodle admin to verify which integration(s) you have enabled.

Should you find that you have the Turnitin LTI 1.1 integration enabled, please be aware that the industry standard is upgrading to LTI 1.3 and your IT Department may want to move to the Turnitin LTI 1.3 standard sooner rather than later. To be clear, these upgrade recommendations and upcoming communications apply to upgrading the Turnitin's LTI 1.1 integration to LTI 1.3 only, they do not apply to the other integrations.

It is important to remember that Turnitin plans to end support of the Turnitin LTI 1.1 integration with Moodle on June 30, 2026 and to deprecate this integration entirely on December 31, 2026.

What we are asking of you is assistance in preparing your institution for this anticipated change when you are ready. In the following pages, we have outlined best practices and provided supporting documentation to facilitate the internal conversations (testing, rollout, providing support, etc.) you may need to have at your institution before enacting that change.

There are two aspects to this change that you may want to consider - one which addresses the technological part of the change and one that addresses the policy part of the change.

Here is an example of a recommended workflow:

Stage 1: Vetting

You may have a Cybersecurity or IT department that would like to vet the LTI 1.3 integration before deploying in production and also before you talk to any stakeholders or do anything else.

Therefore, you may need to contact them to see what they would need for this process and find out how long this might take (as this will affect your initial testing in your test or staging environment and also deployment for your production environment). Some documents they may want Turnitin to provide to them might include:

Stage 2: Testing

Once the integration has been vetted (if required), if you are not a Moodle administrator, you may want to reach out to your support staff for a discussion on setting up and testing the LTI 1.3 integration in your test or staging environment (if you have one). If you are one administrator of several, you may want to speak to your fellow admins about this as well. In order to facilitate those discussions and the testing itself, we recommend the following:

  1. If you have one, in your Moodle test or staging environment, check to see which Turnitin account is connected to your LTI 1.1 integration. Then in production check to see which Turnitin account is connected there. We do not recommend using the same Turnitin account id for test or staging and production environments.
  2. If the same account has been used for the LTI 1.1 integration in your test or staging and production environment, log in to turnitin.com (or turnitinuk.com) and set up a new sub-account for the LTI 1.3 integration specifically for your test or staging environment. If you never had Turnitin integrated in your test or staging environment, we still recommend you create a separate subaccount for testing.
  3. Complete the LTI 1.3 integration setup.
  4. Create LTI 1.3 assignments. You may want to focus on workflows that reflect what your instructors will be doing in their own classes. You may also want to ask if there are any special use cases (and thus any unique workflows) that a department or instructor uses and test that as well.
  5. Submit to the assignments as a student (you can use the student role for this).
  6. Because you need to use the same account id for your LTI 1.3 integration that was used for your LTI 1.1 integration to test how old LTI 1.1 assignments are accessed, we recommend testing this once you have installed the LTI 1.3 integration in your production environment. Please note that the directions for converting your existing LTI 1.1 integration to an LTI 1.3 integration are different and can be found here.

In addition, to assist in your testing you may find the following documentation helpful:

Stage 3: Preparing

While Turnitin has support documentation available for you, your institution may want to develop their own support documentation. If this is the case, you may want to involve the training staff and/or instructional designers on staff for this. Here are some quick links to our help pages should you wish to use them for guidance:

Step 4: Aligning stakeholders

Once you have all your technical testing and documentation completed, you may want to involve various stakeholders to have discussions on when to implement LTI 1.3 and stop using LTI 1.1 in your Moodle environment. Some of those stakeholders could include:

  • Department Heads

  • Writing Center Department/Staff

  • Instructional Design staff

  • Academic Integrity Department/Staff

  • Student Support Department/Staff

  • Faculty Senate

  • Library staff

  • Others

Alternatively, depending on your institutional policy and procedures, you may be able to begin this step at the same time that the vetting and testing is going on.

Managing stakeholder expectations is important. This change will not be a major upheaval causing instructors to have to recreate all their assignments. The Admin FAQ that is provided to you lists all the gain of functionality and any potential loss of functionality that users might experience. This document will be very important in assisting with managing stakeholder expectations and providing answers to questions below that might be discussed in these talks.

In your discussions, you might want to consider the following questions:

  • When is the best time in the school year to make a change?
  • How do we communicate the changes to your instructors, instructional designers, and support staff?
  • Because the workflow does not change for students in this move, do you need to communicate anything to them?
  • What happens to assignments in past courses? Do we still have access to them though Moodle?
  • What about record retention? Is any data going to be lost?
  • What additional workload does this place on our instructors/staff and how do we support them in this?
  • Do we need to have Q&A sessions to get user feedback?
  • What resources do we need to have in place for students and instructors before we make the change?

Stage 5: Deploying

Please remember that Turnitin will provide a comprehensive list of resources to assist you in this transition including:

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

Powered by Zendesk