GetTimetable/Scyllabus: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Prerequisites == | ==Prerequisites== | ||
There must be views created in Scyllabus for UMS to extract data. | There must be views created in Scyllabus for UMS to extract data. | ||
These views are: | These views are: | ||
* rdowner.UMS_ACTTIMETABLE | *rdowner.UMS_ACTTIMETABLE | ||
** InternalID | **InternalID | ||
** parentinternalid | **parentinternalid | ||
** activityhostkey | **activityhostkey | ||
** scheduledstart | **scheduledstart | ||
** scheduledend | **scheduledend | ||
* rdowner.UMS_ACTSTAFF | *rdowner.UMS_ACTSTAFF | ||
** InternalID | **InternalID | ||
** parentinternalid | **parentinternalid | ||
** activityhostkey | **activityhostkey | ||
** staffhostkey | **staffhostkey | ||
** staffname | **staffname | ||
* rdowner.UMS_ACTLOCATION | *rdowner.UMS_ACTLOCATION | ||
** InternalID | **InternalID | ||
** parentinternalid | **parentinternalid | ||
** activityhostkey | **activityhostkey | ||
** locationhostkey | **locationhostkey | ||
** locationdescription | **locationdescription | ||
** locationname | **locationname | ||
* rdowner.UMS_ACTSTUDENTSET | *rdowner.UMS_ACTSTUDENTSET | ||
** InternalID | **InternalID | ||
** parentinternalid | **parentinternalid | ||
** activityhostkey | **activityhostkey | ||
** studentsethostkey | **studentsethostkey | ||
** studentsetname | **studentsetname | ||
** studentsetdescription | **studentsetdescription | ||
* rdowner.UMS_ACTMODULE | *rdowner.UMS_ACTMODULE | ||
** InternalID | **InternalID | ||
** parentinternalid | **parentinternalid | ||
** activityhostkey | **activityhostkey | ||
** modulehostkey | **modulehostkey | ||
** modulename | **modulename | ||
** moduledescription | **moduledescription | ||
The students will be attached to timetable blocks based on information extracted from the GetStudents job. This is done by looking at the activityhostkey from Scyllabus and the activity in the Students table. The students will be attached if they match. | |||
==Setup== | ==Setup== | ||
[[File: | [[File:GetTimetable Scyllabus.jpg|none|thumb|689x689px]] | ||
===[[GetTimetable/Format and content|Format and content]]=== | ===[[GetTimetable/Format and content|Format and content]]=== | ||
| Line 46: | Line 48: | ||
Name of the setting. | Name of the setting. | ||
==== | ===[[GetTimetable/Absence_settings|Absence settings]]=== | ||
===[[GetTimetable/Export_settings|Export settings]]=== | ===[[GetTimetable/Export_settings|Export settings]]=== | ||
==FAQ== | ==FAQ== | ||
Latest revision as of 09:49, 14 February 2020
Prerequisites
There must be views created in Scyllabus for UMS to extract data.
These views are:
- rdowner.UMS_ACTTIMETABLE
- InternalID
- parentinternalid
- activityhostkey
- scheduledstart
- scheduledend
- rdowner.UMS_ACTSTAFF
- InternalID
- parentinternalid
- activityhostkey
- staffhostkey
- staffname
- rdowner.UMS_ACTLOCATION
- InternalID
- parentinternalid
- activityhostkey
- locationhostkey
- locationdescription
- locationname
- rdowner.UMS_ACTSTUDENTSET
- InternalID
- parentinternalid
- activityhostkey
- studentsethostkey
- studentsetname
- studentsetdescription
- rdowner.UMS_ACTMODULE
- InternalID
- parentinternalid
- activityhostkey
- modulehostkey
- modulename
- moduledescription
The students will be attached to timetable blocks based on information extracted from the GetStudents job. This is done by looking at the activityhostkey from Scyllabus and the activity in the Students table. The students will be attached if they match.
Setup
Format and content
Description
Name of the setting.