GetTimetable/Synergetic: Difference between revisions

From UmsWiki
Jump to navigation Jump to search
Kia (talk | contribs)
No edit summary
Kia (talk | contribs)
No edit summary
 
Line 1: Line 1:
==Prerequisites==
==Prerequisites==
You have to set make an entry in CalendarEvents for each semester. This will allow UMS to know which week number the schedules starts in.
You have to make an entry in CalendarEvents for each semester with the timetable start date and the day number. This will allow UMS to know which week number the schedules starts in.


https://wiki.synergetic.net.au/display/SYNMAIN/Timetable+Maintenance+-+Calendar+Events+tab
https://wiki.synergetic.net.au/display/SYNMAIN/Timetable+Maintenance+-+Calendar+Events+tab
Line 23: Line 23:


D10 = day number D10
D10 = day number D10
==Setup==
==Setup==
[[File:GetTimetable Synergetic.jpg|none|thumb|783x783px]]
[[File:GetTimetable Synergetic.jpg|none|thumb|783x783px]]

Latest revision as of 10:10, 14 April 2020

Prerequisites

You have to make an entry in CalendarEvents for each semester with the timetable start date and the day number. This will allow UMS to know which week number the schedules starts in.

https://wiki.synergetic.net.au/display/SYNMAIN/Timetable+Maintenance+-+Calendar+Events+tab

D1 = day number 1

D2 = day number 2

D3 = day number 3

D4 = day number 4

D5 = day number 5

D6 = day number 6

D7 = day number 7

D8 = day number 8

D9 = day number 9

D10 = day number D10

Setup

Format and content

Description

Name of the setting.

Export settings

FAQ

UMS uses this for SQL extraction

select *
From vStudentTimetableFullAll
JOIN FileSemesters ON (FileSemesters.FileYear = vStudentTimetableFullAll.FileYear) And (FileSemesters.FileSemester = vStudentTimetableFullAll.FileSemester)
LEFT JOIN pvCommunity ON vStudentTimetableFullAll.StaffID = pvCommunity.ID
Where
StudentID = 15731
And ClassCode = '08Sci3'
order by ClassCode


The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ImportFromDB_SkemaBrikker

This could be the result of someone scheduling the same class with PeriodNumberSeq = 1 and PeriodNumberSeq <> 1

It will give an error that ends with something like this.

The duplicate key value is (04-02-19_08:40_09:43_PKMQ_2019_1, 1)

This can help find the problematic timetable block. Decipher it like this

  1. Date = 04-02-19
  2. Start time = 08:40
  3. End time = 09:43
  4. Classcode = PKMQ
  5. FileYear = 2019
  6. ActualSemester = 1

The date is calculated based on 2 weeks schedule. This means the date is not too useful.

You can look in UMS using this SQL to find the Day number

Select *
From ImportFromDB_TimeTable_Synergetic
Where
Skemabegivenhed_ID = '04-02-19_08:40_09:43_PKMQ_2019_1'