The wikitable2schedule.py script successfully parses all items and everything.schedule.xml and everything.schedule.json are output. Each session from the wiki has its room attribute set to Self-organized.
Because of the overlapping start time and room name only the "last" sessions of such a group is displayed in the Android Fahrplan app.
Therefore, it would be great if the "overlapping" sessions could be spread to multiple virtual Self-organized rooms, e.g. Self-organized 1, Self-organized 2, Self-organized ....
The current list of self-organized sessions for the DiVOC event contains session which start at the same time. Here an example with multiple sessions starting at 15:00.
The wikitable2schedule.py script successfully parses all items and everything.schedule.xml and everything.schedule.json are output. Each session from the wiki has its room attribute set to
Self-organized
.Because of the overlapping start time and room name only the "last" sessions of such a group is displayed in the Android Fahrplan app.
Therefore, it would be great if the "overlapping" sessions could be spread to multiple virtual
Self-organized
rooms, e.g.Self-organized 1
,Self-organized 2
,Self-organized ...
.