Assign rooms correctly #27
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
mysql
part
non-technical
part
packaging
part
xml
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Untis#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In a coupled lesson, if a room is not assigned to a learning group (in the example FrK), Chronos fills the gap from below so that the rooms are no longer assigned to the correct lesson. The expected representation can be seen in Figure 2.
assigned to @hansegucker
moved from AlekSIS-App-Chronos#148
The problem could also be that in this case two courses are taught by one teacher in the same room. I have now solved this for the time being by swapping the order of the courses in Untis.
assigned to @hansegucker
Here are some sample data from Untis:
The only difference I can see is the
13000at the line which shouldn't have a room. But I am unsure whether this is a safe mark.Okay, in general there seem to be these rules:
(Untis' data structure is the best one I have ever seen.)
created merge request !161 to address this issue
mentioned in merge request !161
Correction: If there are two lesson parts with the same teacher, they will use the same room, but the room will appear just one time in the room list.
mentioned in commit
29b6c4ca14