Transition

Handbook pages

• Consolidate github workflows.
  • regularly run generate-projects-pages.py
• Set repository secrets for actions (e.g., LABOT_PAT_TOKEN).
• Imports: see new handbook (local import.py)
• Structure: areas / processes / alphabetical (instead of johnny decimal)
• Postprocessing:
  • remove “tocs” on pages (generated automatically)
  • visual check (images, figures, links)
  • check/fix links
  • Check for self-service boxes
  • Check for Johnny-Decimal references
• Restructure and link nextcloud (e.g., confidential links to grades: lectures, theses, …; archive; hr)
• Regular updates of the timeline and here
• Search for references to the “digital work lab”
• Consolidate state model with process overview in courses - also add validation script

Repositories

• Decide which repositories will remain in the old organization, and which ones will be moved.

• Upgrades to quarto:

  • theses
  • open-source-project
  • literature-review-seminar
  • digital-work-lecture
  • …

• Change buttons from “Offered by digital work lab” to “Offered by ISE (Frankfurt School)”

• Search for references to the “digital work lab”

Other

• Return library
• Team / alumni / recommendation letters / offboarding
• Machine setup
  • E-Mail (plus authenticator)
  • Windows VM
• Update e-mail footer
• Update affiliations and emails on profiles
• Change e-mail in submission systems
• Update Calendly
• Labot account
• Check: returning devices (will be collected by the IT service)

Pages that require an update for the transition

To mark pages that require changes, the transition_status and transition_comment fields can be added to the yaml header as follows:

---
title: "Resources"
transition_status: "toupdate"
transition_comment: "Update keys, lab access, printing/scanning, design, archive"
---

contents ....

Once the transition is implemented, the transition_status can be changed to updated.