Edit a term
Update study period names, codes, and date windows inline in the Chronology table, including validation, duplicates, and safe deletion.
Terms are edited directly in the Chronology table. You update names, codes, and date windows inline; changes apply across OrgHub once you save. Editing is how you refine election and reassessment schedules, correct calendar mistakes, and keep labels aligned with your published academic year — without recreating the term and breaking existing planning references.
Treat edits to active terms with care. Renaming updates labels broadly; shortening dates after planning or enrollment already exists can affect records scoped to that period.
Why it matters
Academic calendars change: exam boards shift reassessment windows, elective election weeks move, or official semester end dates are corrected. Chronology must stay the single source of truth for those windows. Inline editing lets authorized staff adjust the institutional clock without rebuilding planning data from scratch.
At the same time, terms are referenced by planning rows, courses, exams, and cohorts. Unvalidated date ranges or duplicate codes would break trust in filters and selectors — so Fuxam validates each term’s own start/end relationship and rejects duplicate Term Code values on save.
How it fits
Editing Chronology updates the same master records that module planning, curricula election timing, and cohort module planning consume. For how term changes surface in planning grids, see Term effects on planning.
Before you start
- Confirm you have update permission for Chronology.
- Note which planning, course, or exam data already references the term.
- Prefer editing future terms for structural date shifts; use smaller corrections for the current period when unavoidable.
- If you plan to delete, check whether the term has dependent data first (deletion is blocked when dependencies exist).
How to edit a term
Open the Chronology table
Go to OrgHub → Database → Chronology.
Locate the study period you want to update.
Edit term fields
You can update these columns inline (when you have update permission):
| Column | What to edit |
|---|---|
| Name | Rename the study period |
| Term Code | Change or clear the unique code |
| Start date / End date | Adjust the term window |
| Election Start / Election End | Adjust the election window |
| Reassessment Registration Start / Reassessment Registration End | Adjust the reassessment window |
Click a cell, enter the new value or date, then save when the unsaved-changes indicator appears.
Date validation and overlap warnings
Fuxam validates term dates as you edit:
- Start date cannot be after End date — if you pick a start date beyond the current end date, the change is rejected and the previous value is restored.
- End date cannot be before Start date — the same rule applies in reverse.
These checks prevent an invalid term window within a single study period. They do not block overlapping date ranges between different terms — institutions may intentionally run parallel or staggered periods.
Duplicate term codes
If you enter a Term Code that already exists in your institution, saving fails with a code-already-exists error. Choose a different code or leave the field empty for auto-generation.
Delete a term
Select one or more terms and use the delete action in the toolbar. Deletion is blocked when a term has dependent data — for example, cohort starts, course offerings, exams, or study program items. In that case, keep the term and stop using it for new planning instead of deleting it.
Best practices
- Rename for clarity only when the published calendar name changes; avoid cosmetic renames mid-semester that confuse staff comparing reports.
- Adjust election and reassessment windows before those periods open for students, not after.
- When fixing an invalid draft, correct Start date and End date in an order that keeps start before end (or accept that Fuxam will restore the previous value if the window becomes invalid).
- If a past term is obsolete but still referenced, leave it in Chronology and simply stop selecting it for new planning.
Common pitfalls
- Shortening an active term’s dates after modules, courses, or exams already reference it.
- Reusing a Term Code from another period — save fails with a code-already-exists error.
- Expecting date validation to prevent overlap between two different terms — overlap between terms is allowed.
- Trying to delete a term that still has cohort starts, course offerings, exams, or study program items — deletion is blocked; stop using the term for new work instead.
Troubleshooting
| Problem | What to try |
|---|---|
| Start or end date reverts after edit | Ensure Start date is not after End date (and vice versa); invalid edits are rejected and the previous value is restored |
| Save fails on Term Code | Choose a unique code or clear the field so Fuxam can auto-generate one |
| Cannot delete a term | The term has dependent data; keep it and stop using it for new planning |
| Reassessment columns missing | Your institution may not have the exam center reassessment period enabled |
| Changes not visible elsewhere | Confirm you saved via the unsaved-changes indicator; then refresh the planning or filter view |
FAQ
Does renaming a term update planning labels?
Yes. Changing a term’s Name updates labels wherever that term is referenced. Changing dates does not automatically reschedule existing appointments or course offerings — see Term effects on planning.
Can two terms overlap on the calendar?
Yes. Validation only enforces a valid window within one term. Institutions may intentionally run parallel or staggered periods.
What if I need to retire a term that still has dependents?
Keep the term. Deletion is blocked when dependent data exists. Stop selecting it for new planning, courses, or exams instead of deleting it.
Can I clear a term code?
Yes — you can change or clear the unique code in the Term Code column (subject to uniqueness rules on save). Leaving codes empty where appropriate allows auto-generation behavior on create; when editing, follow the uniqueness rules described above.