Manage module versions
Add module versions, set a default for new connections, and review version history so curricula and courses keep stable academic configurations over time.
Each module has at least one version. Versions let you revise credits, exams, and course templates from one academic year to the next while keeping earlier configurations available for reference. Curriculum items, cohort study plans, and linked courses point to a specific module version — not only the module name — which is what makes controlled academic change possible.
Think of the module as the catalog identity and each version as a dated academic snapshot. That pattern mirrors how many universities revise module handbooks without rewriting the history of past cohorts.
Why versions exist
When requirements change:
- Create a new version with updated settings.
- Leave older versions intact for students and cohorts already tied to them.
- Set a default version so new links prefer the latest configuration.
Without versioning, updating ECTS or examination rules on a shared module would risk silently changing obligations for students already mid-program. With versioning, the new intake can follow 2026 while the previous intake continues on 2025.
How it fits
| Related area | How versions appear |
|---|---|
| Curricula | Curriculum items choose a specific module version when you add modules |
| Link module to course | Course links always target a module version |
| Module planning | Planned modules come from the curriculum; the underlying version carries credits and templates |
| Edit a module | Academic and course fields are edited per version |
| Module groups | When modules are attached to a group, membership resolves to each module’s default version |
Key terms
| Term | Meaning |
|---|---|
| Version name | Label shown in the selector (for example, 1.0, 2.0, or 2025) |
| Module display name | Optional per-version override for how the module appears in study plans, exams, and planning |
| Default version | The preferred version for new curriculum items, course links, and other connections; only one at a time |
| Version history | The full list of versions in the Versions dialog, each editable independently |
| ECTS on the version | Credit points for that snapshot — changing them for a future year usually means a new version |
View and switch versions
Open a module from OrgHub → Database → Modules.
Use the Version selector in the page header to switch between versions. Each option shows the version label.
Versions marked Default are the institution’s preferred version for new connections.
Add a new version
Create a new version when academic rules change for a future period, while earlier versions must remain available.
Open the module and click the version selector.
Select Manage versions to open the Versions dialog.
Select Create Version and fill in:
- Module display name — optional override for how this version appears in study plans and exams.
- Version Name — the version label (for example,
2.0).
Select Save. The new version is added to the list and can be edited independently.
After saving, open the new version and complete Details and Course settings as described in Edit a module.
Set the default version
In the Versions dialog, use Set as Default on the version that should be preferred for new curriculum items, course links, and other connections. Only one version can be default at a time.
View version history
The Versions dialog lists every version with its label and default status. Select any version from the header selector to open and review its historical configuration on the Details and Course tabs.
Worked example — ECTS change across intakes
Module: Research Methods (RM200)
| Version | ECTS | Attendance | Used by |
|---|---|---|---|
2024 |
5 | 75% | Curriculum 2024 → Cohort WS 2024/25 |
2025 (default) |
6 | 80% | Curriculum 2025 → Cohort WS 2025/26 and new course links |
What you do:
- Keep version
2024untouched so mid-program students retain 5 ECTS and the original exam rules. - Create version
2025, set ECTS to6, update examination requirements, then Set as Default. - Place
2025in the new curriculum version. - Link new delivery courses to
2025, not to2024.
When to version vs. edit vs. archive
| Situation | Prefer |
|---|---|
| Typo or incomplete setup on a version not yet used by active cohorts | Edit the existing version |
| New ECTS, exams, or template for a future intake | Create Version, then set as default when ready |
| Module no longer offered at all | Archive the module after checking dependencies |
Versioning and curriculum / course relationships
| Connection | Behavior |
|---|---|
| Curriculum item | Stores the module version you chose when adding the item — changing the default later does not remount old rows |
| Linked course | Points at one module version; sync metadata after display-name or related updates |
| Module group attachment | When modules are attached to a module group, each module’s default version is used |
Best practices
- Name versions consistently (year labels or sequential numbers) so planners and curriculum editors can pick the right one at a glance.
- Set the default only after the new version’s Details and Course tabs are complete.
- Document internally which curriculum versions and cohorts use which module versions before large catalog revisions.
- Prefer versioning over archiving when the unit of study continues under a revised configuration.
- When ECTS changes, update both the new module version and the curriculum credit-point columns for rows that use it.
Common pitfalls
- Editing the default version in place when older cohorts still depend on its previous ECTS or exam rules.
- Creating a new version but forgetting to place it in the relevant curriculum version.
- Leaving an outdated version as Default, so new course links quietly attach to old settings.
- Assuming Set as Default rewrites existing curriculum items and course links — it does not.
FAQ
Do curriculum items update when I change the default?
No. Existing curriculum items and course links continue to reference the specific module version they were given. The default influences new connections.
What happens if a referenced version is missing?
If a referenced version no longer exists, Fuxam opens the latest available version automatically.
Can two versions both be default?
No. Only one version can be default at a time. Use Set as Default on the version that should replace the previous preference.
Does a new version copy ECTS and exams from the previous one?
After you create a version, open it and complete Details and Course as needed. Treat the new version as its own academic snapshot — verify ECTS and examination requirements before setting it as default or placing it in a curriculum.