Manage curriculum versions
Create new curriculum versions, duplicate structure, and review version history without disrupting earlier cohorts.
Like modules, curricula support multiple versions so you can revise a program’s structure without losing earlier configurations tied to existing cohorts. A version is a full snapshot: study periods, focuses, elective groups, module slots, and election settings as they stood for that blueprint.
Versioning is the academic equivalent of “new Prüfungsordnung for the next intake” — older cohorts keep following the rules they started under, while new cohorts receive the updated plan.
Why curriculum versions exist
Each cohort and student study plan references a specific curriculum version. When you revise a program:
- Create a new version (often by duplicating the current structure).
- Adjust modules, study periods, and elective groups in the new version.
- Assign the new version to upcoming cohorts while older cohorts keep their original version.
That preserves validity across intakes: each cohort’s obligations remain those of the version that was assigned — not whatever is currently being edited for next year.
How it fits
| Related area | Relationship |
|---|---|
| Edit a curriculum | Day-to-day edits on the version you have selected |
| Assign curriculum to cohort | Cohorts pick a specific version |
| Curriculum structure explained | What each version must contain |
| Modules / module versions | Curriculum items pin module versions; program and module versioning often move together |
| Study programs and cohorts | Program versions and curriculum versions should be planned in tandem for each intake |
Key concepts
| Concept | Meaning |
|---|---|
| Curriculum | The parent record (name, tags, program association) |
| Curriculum version | Independent structure snapshot selectable in the header |
| Duplicate | Copy an existing version’s structure as a starting point for the next revision |
| Version history | Earlier versions remain available to inspect what past cohorts were assigned |
| Shared vs cohort-specific | Shared versions live in Database for many cohorts; disconnecting a cohort creates a cohort-specific copy for local exceptions |
| Validity / intake binding | A version “applies” to students through the cohort assignment — not by calendar alone |
View and switch versions
Open a curriculum from OrgHub → Database → Curricula.
Use the Version selector in the page header to switch between curriculum versions.
Confirm you are on the intended version before editing modules or Curriculum Structure.
Create a new version
Open the curriculum and select Manage versions from the version selector (or the equivalent version management entry point).
Select Create New Version.
Enter a version name and confirm. Fuxam creates a new version — typically starting from a copy of the current structure so you can make targeted changes.
Save and switch to the new version to edit modules, study periods, and elective groups independently.
Duplicate an existing version
You can also duplicate a curriculum version from the version management actions. Duplication is useful when a new intake year needs nearly the same structure with minor adjustments.
After duplication, treat the copy as independent: change modules, elective groups, or study periods without altering the source version older cohorts still use.
Review version history
Each version has its own overview page, module table, and Curriculum Structure settings. Open earlier versions from the header selector to compare historical program layouts or verify what a past cohort was assigned.
This is especially useful during audits, accreditation reviews, or student advising questions about “what was required when I started.”
Versioning and validity in practice
| Intake | Curriculum version | What stays stable |
|---|---|---|
| WS 2024/25 cohort | PO 2024 |
Study plans and elective rules for that cohort |
| WS 2025/26 cohort | PO 2025 |
Revised modules and electives for the new intake |
| Advising / audit | Either version via selector | Historical truth of requirements |
Versions do not “expire” by themselves when a newer one exists. A version remains relevant as long as cohorts (and their students) still reference it. New cohorts only follow a new version when you assign that version.
Shared master vs cohort-specific copy
- Shared curriculum version — maintained in Database; many cohorts can point at it.
- Cohort-specific copy — created when you Disconnect on the cohort (see Assign curriculum to cohort); local edits stay with that cohort.
Use disconnect for exceptions. Use a new shared version when the whole next intake should share the same revised blueprint.
When to create a version vs edit in place
| Situation | Prefer |
|---|---|
| Typo, tag, or small correction with intentional propagation | Edit the current version carefully (Edit a curriculum) |
| New intake, new accreditation rules, major module set change | Create New Version or duplicate, then assign to new cohorts |
| One cohort needs exceptions | Consider cohort Disconnect rather than forking the master for everyone — see Assign curriculum to cohort |
Checklist after creating a version
- Switch the header selector to the new version.
- Walk Curriculum Structure (periods, focuses, elective groups, election mode).
- Review the module table (module versions, terms, credit points, elective assignments).
- Check semester and program credit balance.
- Only then assign the version to a cohort.
Best practices
- Freeze a version once cohorts are actively enrolled on it; put forward-looking changes in a new version.
- Keep module version pins aligned with the curriculum version’s intent (new teaching content often means new module versions and a new curriculum version).
- After creating a version, walk Curriculum Structure and the module table once before assigning any cohort.
- Coordinate curriculum version labels with study program versions so intake naming stays consistent.
- Keep a short internal note of which version each living cohort uses.
Common pitfalls
- Editing a live version when you meant to branch for next year — risk of propagating unwanted changes.
- Creating a new version but still assigning new cohorts to the old version by habit.
- Leaving the new version as an unfinished copy and assigning it too early.
- Confusing curriculum versions with module versions — both exist; curriculum items reference specific module versions.
- Using disconnect to implement a program-wide reform that should have been a new shared version.
FAQ
Do older cohorts move to the new version automatically?
No. Assign the new version to upcoming cohorts while older cohorts keep their original version. Student plans stay tied to the version from when they joined unless you explicitly change or propagate updates.
Is Create New Version the same as Duplicate?
Create New Version creates a new version — typically starting from a copy of the current structure. You can also duplicate from version management actions when you want to copy a chosen existing version as the base for minor adjustments. Both produce an independent version you then edit.
Can I still view what a past cohort used?
Yes. Open earlier versions from the header selector to compare historical layouts or verify what a past cohort was assigned. Each version keeps its own overview, module table, and Curriculum Structure settings.
Does a new version change Chronology terms?
No. Organization terms stay in Chronology. The new version has its own study periods; each cohort maps those periods to organization terms when the curriculum is assigned.