Fabian Scheipl
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Timetables & Rooms === ## Procedures ### Timetable: Start: In the fourth week of the previous semester. 1. Clean up the overview of all lectures and list which course can/must be held next semester (according to the examination regulations). 2. (This is not done currently, but would make the work easier) Collect all time constraints of the lecturers 3. In the "Leitungssitzung" the lecutures are assigned to the responsible lecturer. 4. Clean up and complete the schedules of all minor courses that statistics students can take next semester (this is necessary because I usually only get a handful of responses when I ask how they plan to do next semester) -> see: https://docs.google.com/spreadsheets/d/1tWI7oe1ztmABuYEWrLglDYBxY9xIhJyAgvMkptmK21A/edit#gid=1046872125 5. Adding the next semester to the Google-Docs in 3 and send out asking other departments to fill out the plan for the next semester (is usually only done by 50%). 6. Preparation of a time schedule -> see: https://docs.google.com/spreadsheets/d/1iPayNc54pJks6swzuv2--UTO4ptYFl6JLUR-aD1tnzI/edit#gid=0 a. Discuss the schedule with the Department of Mathematics, the Department of Sociology, the Department of Computer Science, and the Department of Bioinformatics. b. If you do not receive a response within a few days, create a spreadsheet of the previous year's schedule and use that instead -> see: https://docs.google.com/spreadsheets/d/1MmNw18aOftIutddpFv1FrycFvdZgQ9j6OmCZt8MRrMM/edit#gid=0 c. Modify the schedule if needed and discuss it again with the Department of Mathematics, the Department of Sociology, the Department of Computer Science, and the Department of Bioinformatics. 6. Ask all teachers at the institute if the schedule is ok a. Modify it if necessary b. Discuss it again with the Department of Mathematics, the Department of Sociology, the Department of Computer Science, and the Department of Bioinformatics. 7. Inform all departments who can take either the 30 or 60ECTS statistics minor of the current schedule 8. Book all rooms before the deadline. (This is usually in the beginning November and Mai) 9. Write to everyone at the statistics institute that he/she should now decide which exercises he/she wants to hold 10. (This is not done, but something like this is necessary) Listing who and how many lecture hours the individual person has (or divided into groups) and in which language the exercises can be held. Now there is a 1-2 month break where I/we only discuss minor things. 11. Check which booking of the rooms was accepted and which was not a. If the lecture room does not meet the requirements (e.g. blackboard, beamer missing), then try to find another room, possibly also by making arrangements with other faculties b. If we don't get a room, we look for a new date and discuss it with the responsible person, the department of mathematics, ..... c. Checking on the large minor subjects (VWL, BWL, ...) of statistics students (it may be that these times have changed as well and we usually won't be informed about it). 12. Sometimes the type of lecture/exercise changes and this then results in a conflict in the schedule (e.g. only 1 and not 2 exercise sessions, needs a cip pool) -> find a new timeslot and room 13. Remind everyone that they need to hold an exercise class and that this information needs to be entered into the Google Docs in 5. 14. Look for people who are willing to hold the exercise session that are still open. 15. In the two weeks leading up to and during the first week of the semester a. need to resolve any time conflicts with minor subjects that were not anticipated b. Search for PHD students who can help out in exercises that are still open End: In the second week of the semester to be scheduled. ### Seminars 1. ask who would like to teach a seminar course in the coming semester. 2. collect all necessary information about the seminar courses. 2. Remind everyone that (in most cases bachelor) seminars are still needed. 3. set up lsf 4. assign students to seminars (depending on priority and progress of bachelor/master). 5. share the information about who is attending which seminar with the students and instructors. ### Tasks: Room booking - Lecture room booking (there is actually only 1 month break because we have to change something all the time). - Exam room booking (remember that you also have to book the retry exams -> you also have to work during the semester break). - Seminars have to be set up in the LSF - Other block courses etc. have to be booked. ## Problem(s) **Please add problems in this context not listed yet** *Timetable generation is complex:* - coordinating timetable generation and room bookings both within the department and across other depts. with which we share lectures take a lot of time and effort - lots of complicated constraints that must be considered. - with the recent growth in staff and complexity of currricula, it is no longer a task ("Dienstaufgabe") that some poor PhD student (i.e. Hannah B.) can be expected to just do by themself "on the side", without receiving a compensating reduction in teaching duties or sufficient support from colleagues. - Coordinating the schedule has a long learning curve (about two years, since you have to think of different things in the summer semester than in the winter semester) *Tasks are distributed so that they create lots of blocking:* - our current system assigns responsibilites for the booking of lecture rooms and for generating time tables to different people. - Room booking is done by a student assistant that works on this for 1h/day, and LMU room management usually takes a couple of days to confirm requests. - In combination, this means that room requests take multiple days to be answered, so the person trying to figure out our timetables spends a lot of time waiting for confirmation of room requests and can't proceed. *Lack of cooperation and coordination within the institute:* - PhD students increasingly often on "research contracts" without mandatory teaching - too little German speaking teaching staff available: difficult to find people for bachelors courses - different standards across groups whether/how much teaching people without contractual obligations are expected to perform - responsibilites for exercises, labs, tutorials are currently not being assigned in the faculty meetings that assign responsibilites for lectures and people need to be recruited informally afterwards - Thomas Augustin and Hannah report that it has become increasingly difficult to recruit people for tutorials and exercise sessions even though, on paper, we should have sufficient teaching staff. Needing to send out multiple begging emails in order to recruit staff for open courses wastes lots of time and energy. *Lack of cooperation and coordination across faculties/depts:* - lecture times in CS, maths etc determine constraints for our own lectures, but these are typically only known/communicated very close to the relevant deadlines for booking lecture halls etc - makes timetable generation an iterative problem: send proposals out to other depts., wait for responses, start over ### LSF for exam administration * starting next summer, we can use LSF for exam administration (as most of LMU already does) - exam registration for students can be done via LSF - students can choose a specific lecture/exam for a module in their study plan (e.g. for electives) - grade lists can be uploaded via LSF (who does that needs to be clarified) * Added/changed duties: - Link lectures to available modules in LSF (only for new lectures, lectures from previous years can be reused) - Add exams to LSF (is already done in order to book rooms) - Support for lecturers? (VS: LSF can also be used for planning seminars / distributing students to seminars) ## Possible (partial) solutions *Just brainstorming here, we can discuss feasibility/desirability/efficacy in depth when we meet. Please comment/add ideas.* ### faculty meetings ("Lehrplanungskonferenz") must also assign explicit responsibilites for exercises/labs/tutorials A. in the sense that specific staff are explicitly assigned to every exercise/lab being offered **+**: also covers cases like very small groups with too few teaching staff or temporary faculty who have no staff of their own **-**: often not known who will be available for teaching what 1 year in advance; makes planning inflexible B: in the sense that responsibility is assigned to a group and they make their own arrangements internally. **+**: more flexible -- easier/quicker faculty meetings **-**: does not help people in small groups that need to rely on staff from other groups **-**: you have to know half a year in advance how many people in the group will speak german. also: set exam dates collectively, provide lecturer availabilities, available hours per language per chair, tabulate lecture hours provided by whom/from which group, include (planning of) seminars ### lay off student assistant for room booking and have the same person be responsible for both timetables and rooms: **+**: avoids additional delays from unresponsive student assistants **-**: slightly higher workload for the person responsible -> Reply from Hannah: No, it's a 10 hour per week job. **bad idea unless we get a dedicated person that takes over all coordination responsibilities** ### give a teaching load reduction to the person doing this seems obvious to me, and obviously unfair that this is not being done already. **-**: Still, because of the long training period, it is very inefficient to have a Ph.D. student do this. ATM 1d/week. Unusually much because of re-accreditation. Should be doable with 5-6 h / week once used to the job, if supported by student assistants. but: accreditation by others (maths, sociology) coming up, will break schedules again. ### use software to generate timetables: [FET](https://lalescu.ro/liviu/fet/) is FOSS and able to handle complicated constraints. *General Comment*: After creating the timetable (which has to be done only after an accreditation), you can copy the one from the previous year and "only" have to adjust the problems caused by - another person gives the lecture - another department had an accreditation **+**: - works rather well (for small problems) IME -- used this for the ESG datascience timetable some years ago; - would guarantee that timetables are without conflicts if we supply the constraints correctly. - faster/easier/more reliable to run a program versus puzzling it out manually - could be one way to distribute workload more evenly: one person from every group supplies the FET files for the teaching staff from that group and the courses/lectures they offer. FET files describe the relevant constraints for persons (e.g. "not available Friday after 14:00") and courses (e.g. "can't overlap with lectures X, Y and Z", "no lectures on Wed afternoon") **-**: - fairly high up-front investment to encode all the constraints for the courses we offer in the file format used by FET - not sure how easy/hard it is to include lectures offered by others in the constraint set (e.g. "Analysis I" offered by maths dept at specific fixed times) ### hire (non-academic) person to take care of this (timetables and rooms) you don't really need the qualification you need for doing a phd, so the most efficient and ressource-optimal thing would be to hire a specific person for this? this person should also do the planning for seminars and book rooms for exams etc. **+**: - solves the "unfairness" issue - possible synergies with exam administration - cheaper than PhD - This person does this for longer than just a few years -> Coordination becomes easier over time - Tasks currently split across multiple people can be assigned a single person (Hannahs tasks + e.g., teaching evaluations, organizing student seminars, ...) **-**: - costs money - not sure where to take this from? But we spend so much for other - less useful - stuff that this could be a good idea imo - does not solve the cooperation issues **?**: - Paid by *Studienzuschüsse*? Can only used for "better" studies ### the cooperation issue has to be discussed in the leitungssitzung - don't think that in the end all chairs will do it the same way, but everyone should be aware of the above problems and group leaders responsible to make sure that their employees do (on average over the group) what they are obliged to do - I think we need the teaching obligation per chair as a number, each semester. "we" in the sense of "someone", I guess Thomas Augustin should be at least informed. ### This is a suggestion for a solution (by Hannah) *General Comment:* This idea is based on how the other departments organise their scheduling of the next semester, seminars, etc. I strongly recommend someone to do this over a longer period of time because: - the learning periode is long - every time we change a person, every other department has to learn in the person of the statistical institute. - A lot of tacit knowledge is needed, which I am trying to summarize at the moment, but I will not succeed in writing all of it down. - Many examination regulations should be known, and many of the regulations are not so easy to understand. *Staff:* 1. A staff person who has 5-6 hours a week to coordinate the schedule, room booking and seminars. This person should do this for a longer period of time, not just a few years, as coordination becomes easier after two years. (Note that more time is needed before the room booking deadline, just before the semester, and during the first two years.) 2. Hire one or two student assistants (about 20 hours per week). *Division of the work:* Here I refer to the process described above. Provided that the person responsible is already familiar with the exam regulations, it should not be so time-consuming to check everything that the working student has done. Timetable Coordination: - 1, 2, 3, 8 can be done by the student assistant. Note that this should be checked as it can be complicated (in my opinion) at the beginning. - 4, 7, 9, 10-15 should be done by the long-term staff. - 5, 6 a student assistant can help check if something went wrong in the planning. But communication with our institute and other institutes should be done by a long-term staff. Seminars: - 1,2,5: has to be done by the long-term staff person - 3,4: can be done by the student assistent, but should be checked by the long-term staff person. Room booking tasks: - Anything that is a month in advance and not incredibly important, the student assistant can book. - If a room is needed within a month, then the long-term staff person books the room - Use software where everyone enters their request for the lecture rooms. - The software sends the booking to either the student or the staff person (depending on how much time is left). - One cannot request a room unless all the information is given to book the room - One can also ask for additional time options or preferred rooms ### Thomas' opinion #### Best option Hire non-scientific staff at 0.75-1 FTE (full time equivalent https://de.wikipedia.org/wiki/Vollzeit%C3%A4quivalent) as a "teaching coordinator". This person would be responsible of all orga around teaching, including scheduling and room booking (courses + exams), finding/assigning lecturers/TAs when necessary, gathering seminar proposals, keeping track of over/under-fulfillment of teaching duties, etc. The position would be assigned/supervised by the dean of studies. I've seen this play out super smoothly in the Netherlands (where there was a full-time position for all that in smaller departments than ours). Benefits: - Great to have a single person on top of everything. - Very convenient for all others to know where to go to. - Frees up lots of research capacity of people currently doing (large) parts of this on the side. I doubt that anyone would be fundamentally opposed to the above, the main issue is obviously finances. It's unlikely the dept can afford an additional position at the moment, so we would need to give up on 0.5-0.75 FTE scientific staff. Since this frees a lot of mental capacity, I still think it would be a net positive in terms of scientific capital. This capital is currently bound in the dean of studies' group, so it would make sense to trade one position there. A second issue is that non-scientific staff normally needs to be given a permanent contract. As far as I know, PhD/Postdoc positions (even "Haushaltsstellen") are technically not available permanently, so the university administration would need to play along. If the above doesn't work, it seems like assigning duties, a significant amount of HiWi-hours, and a significant reduction in teaching load to permanent staff would be best. #### Misc - I'd suggest that Fabian (or I) also ask the current dean of studies (Thomas Augustin) for input/views. - Can we get a rough count of number of active teaching staff (lecturers/TAs) and courses taught per semester? - For assigning TAs: - Each prof discusses in their group who's TAing for what course. - Check if there's too much/too little capacity in the group for teaching the courses they're responsible for. - This info should be in the google doc *before* the Lehrplanungsitzung. - Profs with too little capacity can try to arrange "borrowing" suitable staff from other groups beforehand. - At the Lehrplanungsitzung we figure out how to fill remaining gaps (just as we do for lectures already). ----------------------- other institutes: - sociology: Schambach - phi: Wirsing -> von Hannah: Thomas Wyrwich - maths: ?? -> von Hannah: Schörner - CS: johansen / barth - --------------------------------------------------------------------------- --------------------------------------------------------------------------- Poll for Date: https://xoyondo.com/dp/Bex8QMwWTH7DKGG/f4NLXCjLnC

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully