Skip to main content
  1. Turnitin Guides
  2. Administrator hub
  3. Upgrading to Turnitin Advantage (LTI 1.3)
  4. Canvas
  5. Upgrading from Plagiarism Framework to Turnitin Advantage (LTI 1.3)

Plagiarism Framework to Turnitin Advantage (LTI 1.3) upgrade recommendations for Turnitin administrators

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 moving from your existing Turnitin integration in Canvas to the Turnitin Advantage (LTI 1.3) integration. There are some things that you may want to consider in this journey.  Please note that Canvas has announced the end of life date for Plagiarism Framework integrations for December 31, 2027.  We recommend institutions start internal discussions soon to determine the best timeline for upgrading for their users and institution.

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 upgrade.

There are two aspects to this change that you may want to consider - one that 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 Turnitin Advantage (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 beta environments and also deployment for production). 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 Canvas administrator, you may want to reach out to your Canvas support staff for a discussion on setting up and testing the Turnitin Advantage (LTI 1.3) integration in your beta environment. If you are one of several admins, you may want to speak to your fellow admins about this as well. To facilitate those discussions and the testing itself, we recommend the following:

  1. If you need to test the Turnitin Advantage (LTI 1.3) integration, create a new Turnitin sub-account.
  2. Then complete the integration setup in beta.  We recommend testing the integration in the Canvas beta environment as the Document Processor workflow of Turnitin Advantage (LTI 1.3) does not work in the Canvas test environment.
  3. Create Turnitin assignments (i.e. new Standard and Multipart assignments) as needed and Canvas Assignments (that are enabled for Turnitin features via Document Processor). You may also want to focus on workflows that reflect what your instructors will be doing in their own classes. Are there any special use cases (and thus any unique workflows) that a department or instructor uses?  If so, this probably needs to be tested as well. Please note that the results of this testing may differ from what happens in your production environment, depending on how much the beta environment matches production, including access to external systems.
  4. Submit the assignments as a student.   We recommend impersonating an enrolled student (can be a dummy student) that has a corresponding email (which does not have to be real).
  5. You may want to also test copying assignments into new courses. 
  6. Testing for access to past Turnitin enabled assignments (as needed)
    1. LTI 1.1
      1. Because you need to connect your beta environment to a Turnitin account that differs from the Turnitin account that is connected to your production environment, if you try to launch existing LTI 1.1 assignments, they will launch as “new” Turnitin Advantage (LTI 1.3) assignments instead.  If you want to test access to past LTI 1.1 assignments in beta, you will need to change the LTI 1.1 integration key and shared secret to the new Turnitin account you want to use for testing in beta, recreate the assignments again with submissions made to them, then upgrade to the Turnitin Advantage (LTI 1.3) integration (using that same account).  Alternatively, once you have installed the Turnitin Advantage (LTI 1.3) integration in production, you can make it available at a course level that has previous LTI 1.1 assignments and submissions in it. When you are done testing for access, you can remove the Turnitin Advantage (LTI 1.3) deployment from the course and make it available to all your users instead.  
    2. Turnitin Advantage (LTI 1.3)
      1. There is no need to test these assignments if you already have this integration enabled in your Canvas Production environment. 
  7. Testing for access to past Plagiarism Framework enabled assignments 
    1. Access to past Plagiarism Framework enabled Canvas assignments will occur upon migration to Document Processor using the migration button.  However, because you are unable to set up a new Plagiarism Framework integration that is linked to a separate Turnitin account in a Canvas beta environment, testing for access to past Plagiarism Framework enabled Canvas assignments will have to occur in your Canvas production environment.  You cannot test the migration button in Canvas beta environments.      
  8. Remember that beta updates every week, so you may need to redo the integration if you are in the middle of testing.

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 its 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:

Stage 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 Turnitin Advantage (LTI 1.3) and stop using the LTI 1.1 and/or Plagiarism Framework integration in your Canvas 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.  The Admin FAQ that is provided to you lists all the gains of functionality, any potential loss of functionality, or any change in workflow that users might experience. This document will be very important in assisting with managing stakeholder expectations and providing answers to the 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? For example, changing the integration in the middle of a semester is not recommended, as that will disrupt current courses and assignments.
  • How do we communicate the changes to our instructors, instructional designers, support staff?
  • Are there any changes to the workflow for students that need to be communicated to them?
  • What happens to assignments in past courses? Do we still have access to them and their submissions through Canvas?
  • 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 open it to all or to just a few initially? Do we want to do a soft launch?
  • Do we need to have Q and 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