When managing users, classes and memberships it is useful to plan out the process and the screens you will need for the user interface. Sample screens and their corresponding mark-up are beyond the main focus of these tutorials. Furthermore the layout of the screens and their location within your application will be governed largely by the application you are using for learning management. However, there are some recommendations that we have found useful to follow in the integrations we have developed.

This section outlines the main components you should consider and the overall process flow involved.

The main purpose of the integration is providing access to the originality checking process within Turnitin from within your Learning Management Application. In order to do this there needs to be a Turnitin assignment your students can submit to.

As a standard approach to this process our engineers develop integrations using the following structure.

Add to the standard class screen a 'Create Turnitin Assignment' option, this will the take the following minimum data set:

• Class title
• Class end date
• Assignment title
• Assignment start date
• Assignment due date

In addition to this the instructor details - name and email address should be available

On submission of this data the process is:

• Create Turnitin class
• Create Turnitin user with default role of 'Instructor'
• Create Turnitin membership between the class and the instructor - setting the role as 'Instructor'.
• Create the Turnitin assignment

At this point the student user records have not been created or enrolled on the class. This step is completed as part of the submission.

When making a submission against the Turnitin Assignment the process should be:

• Check if the student exists within Turnitin already, if not proceed to step 3, else proceed to step 2
• Check for the student on the class membership, if the membership does not exist proceed to step 4, else proceed to step 5
• Create the student
• Create the membership
• Make the submission

After each point of creation the Turnitin ID for that data item is available, we recommend that this information is stored within your application to reduce the need to find the details in the future. This is a simple step that can speed up future use of your integration for the end user.

Once a submission has completed successfully the API returns the submission ID, it is recommended that these are stored so they can be used to launch the Document Viewer without calling the find methods of the SDK.

Each of these steps are detailed in the tutorials for each of the supported programming languages.