Timetable/itslearning: Difference between revisions
Jump to navigation
Jump to search
Created page with "==Get started with itslearning== ===Requirements=== *A Timetable user - this user holds all events *Access to Organisation API at itslearning *Valid itslearning sync from inL..." |
|||
| Line 7: | Line 7: | ||
===Create Timetable user=== | ===Create Timetable user=== | ||
For the purpose of syncing the timetable to itslearning, we need a | For the purpose of syncing the timetable to itslearning, we need a UMSServiceUser. The synckey for user object has to be the same as the username, UMSServiceUser. | ||
===Access to Organisation API=== | ===Access to Organisation API=== | ||
To get access to this API, you'll need to contact your local itslearning Services Team. | To get access to this API, you'll need to contact your local itslearning Services Team. | ||
Revision as of 12:41, 22 July 2019
Get started with itslearning
Requirements
- A Timetable user - this user holds all events
- Access to Organisation API at itslearning
- Valid itslearning sync from inLogic
Create Timetable user
For the purpose of syncing the timetable to itslearning, we need a UMSServiceUser. The synckey for user object has to be the same as the username, UMSServiceUser.
Access to Organisation API
To get access to this API, you'll need to contact your local itslearning Services Team.
See this for more information
Valid itslearning sync from inLogic
A valid sync of the users from UMS to itslearning is needed - this ensures our timetable information is matched correctly with student, activities and course information.