# 5. Sub Category Management

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 5. Sub Category Management

### 5.1 Create Specialized Domains Within Categories
**What it does:** Defines the specialized domains (sub-categories) within each major professional category — for example, within IT: Web Development, Data Science, Cybersecurity; within Business: Finance, Marketing, Management. The Super Administrator creates and organizes the sub-categories so the professional catalog has a useful second level of granularity, and courses are placed in the right specialized domain.

**Sub-features:**
- Create a sub-category under a major category: name, description, and status
- The sub-category set per category (the specialized domains it contains)
- Sub-category list per category with the count of courses under each
- Sub-category status: active sub-categories are browsable; inactive ones are not offered
- One sub-category belongs to one major category (clear parentage)
- Sub-category ordering for display
- Audit logging of sub-category create/edit

**Super Administrator User Journey:**
1. Under the IT category, Super Admin creates the specialized domains: Web Development, Data Science, and Cybersecurity.
2. Sets each sub-category's name and a short description (the domain's focus).
3. Saves; the sub-categories appear under IT and are available for course placement.
4. Reviews the sub-category list per category: each shows the count of courses under it, so coverage per domain is visible.
5. Places a course in the right sub-category (a web development course under IT → Web Development); the course now appears in that domain.
6. For a domain the platform is not (yet) offering, keeps the sub-category inactive: not browsable, but activatable later.
7. Confirms the parentage: each sub-category belongs to exactly one major category; there is no ambiguous placement.
8. Each sub-category create and edit is audit-logged with the category, the sub-category, and the timestamp.

**Rules & Edge Cases:**
- A sub-category belongs to one major category; the parentage is explicit and unambiguous.
- An inactive sub-category is not browsable but is preserved (activatable later).
- The sub-category list shows course counts, so an empty domain is a visible gap.
- Display order is maintained within the category for the catalog presentation.
- A course is placed in a sub-category (the specialized domain), which places it in the category by inheritance.
- Sub-category create and edit are audit-logged with the category, sub-category, and timestamp.

### 5.2 Career Path Suggestions
**What it does:** Associates career path suggestions with sub-categories: the careers and roles a learner can pursue by developing the sub-category's skills. The Super Administrator maintains the career path suggestions so learners can see the professional outcomes of a domain, connecting the learning to real career directions.

**Sub-features:**
- Career path suggestions per sub-category (the careers/roles the domain leads to)
- Suggestion authoring: clear career/role names with a short context
- Visibility: the suggestions are shown on the sub-category's page
- Multiple suggestions per sub-category (a domain can lead to several careers)
- Suggestion review: the set is checked for relevance and currency
- Update as career landscapes evolve
- Audit logging of career path suggestion changes

**Super Administrator User Journey:**
1. For the Data Science sub-category, Super Admin adds the career path suggestions: Data Analyst, Data Scientist, Business Intelligence Developer.
2. Writes a short context for each (what the role involves), so the suggestion is meaningful, not just a title.
3. Saves; the suggestions appear on the sub-category's page, showing the learner the professional outcomes.
4. For the Web Development sub-category, adds its suggestions: Front-End Developer, Full-Stack Developer, Web Engineer.
5. Reviews the suggestions for relevance and currency: the roles are real and current; an outdated role is updated.
6. Checks the visibility: a learner on the sub-category's page sees the career paths, connecting the domain's skills to outcomes.
7. As the career landscape evolves (a new role emerges), adds the suggestion to the relevant sub-category.
8. The career path suggestion changes are audit-logged with the sub-category, the suggestions, and the timestamp.

**Rules & Edge Cases:**
- Career path suggestions are per sub-category; they express the domain's professional outcomes.
- A sub-category can have multiple suggestions (a domain leads to several careers).
- Suggestions are clear and current; they are reviewed and updated as careers evolve.
- The suggestions are shown on the sub-category's page; they are the domain's outcome communication.
- A suggestion is a guide (a possible path), not a guarantee; the framing reflects that.
- Career path suggestion changes are audit-logged with the sub-category, suggestions, and timestamp.

### 5.3 Skill Progression Mapping
**What it does:** Maps the skill progression within and across sub-categories: how the skills a learner builds develop from foundational to advanced, and how one sub-category's skills lead into another's. The Super Administrator maintains the skill progression mapping so a learner's path through the professional catalog is a coherent, sequenced development of skills.

**Sub-features:**
- Skill progression within a sub-category: the foundational-to-advanced sequence of its skills
- Cross-sub-category progression: how one domain's skills lead into another's (e.g., Web Development into Full-Stack)
- Progression mapping: the links that define the development sequence
- Recommended path: a suggested sequence of sub-categories/skills for a goal
- Progression review: the mapping is checked for coherence
- Visibility: the progression is shown to guide the learner's path
- Audit logging of progression mapping changes

**Super Administrator User Journey:**
1. For the Web Development sub-category, Super Admin maps the skill progression: foundational (HTML/CSS) → intermediate (JavaScript) → advanced (frameworks), so the domain's skills are sequenced.
2. Creates a cross-sub-category progression: Web Development leads into Full-Stack (the skills build on each other), so a learner sees the natural next step.
3. Defines a recommended path for a goal (becoming a full-stack developer): the sequence of sub-categories and skills, starting from the foundations.
4. Reviews the mapping for coherence: the sequence is logical (no advanced skill before its foundation), and a gap is corrected.
5. Checks the visibility: a learner sees the progression and the recommended path, so their development is guided, not left to guess.
6. For a learner who has completed the foundational skills, the platform suggests the next step in the progression (the intermediate skills).
7. As the skill landscape evolves, updates the progression mapping (a new intermediate skill is inserted in the sequence).
8. The progression mapping changes are audit-logged with the sub-categories, the skills, and the timestamp.

**Rules & Edge Cases:**
- The progression is foundational-to-advanced; the sequence is logical, with no advanced skill before its foundation.
- Cross-sub-category progression connects domains where the skills build on each other; the link is explicit.
- A recommended path is a suggested sequence for a goal; it is a guide, not a mandatory order.
- The mapping is reviewed for coherence; gaps and out-of-order skills are corrected.
- The progression is visible to guide the learner; the next step is suggested based on completed skills.
- Progression mapping changes are audit-logged with the sub-categories, skills, and timestamp.