# 4. Mind Map Management

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

---

## 4. Mind Map Management

### 4.1 Pre-Built Mind Maps for Each Topic
**What it does:** Provides a pre-built mind map for each topic: the Super Administrator (or the content owners they coordinate) creates the mind map that visualizes a topic's concepts and their relationships, so a learner sees the topic's structure at a glance — the big picture and how the parts connect — before or alongside the detailed content. The mind map is the topic's visual map.

**Sub-features:**
- Pre-built mind map: the mind map created for a topic (the concepts and their relationships)
- Topic coverage: a mind map per topic (the topic's visual map)
- Concept nodes: the concepts as nodes, with the relationships between them
- Hierarchy: the topic's structure (the main concept, the sub-concepts) shown
- Visibility: the mind map shown in the topic's context
- Update: the mind map updated when the topic's content changes
- Audit logging of mind map create/update

**Super Administrator User Journey:**
1. For a topic, Super Admin (coordinating the content owner) creates the pre-built mind map: the topic's main concept, the sub-concepts, and the relationships between them.
2. Structures the hierarchy: the main concept at the center, the sub-concepts branching out, so the topic's structure is visible.
3. Saves; the mind map appears in the topic's context, and a learner sees the topic's map at a glance.
4. A learner reviews the mind map before the detailed content (the big picture) and alongside it (the connection of the parts).
5. For a topic whose content changes (a concept added or revised), Super Admin updates the mind map to reflect the new structure; the change is recorded.
6. Reviews the mind map coverage: the topics with their mind maps, so a topic missing its map is a visible gap.
7. Checks the mind map accuracy: the concepts and relationships are correct (a wrong relationship is corrected); the map is a faithful representation.
8. The mind map create/update is audit-logged with the topic, the map, and the timestamp.

**Rules & Edge Cases:**
- A mind map is per topic; it is the topic's visual map (the concepts and their relationships).
- The hierarchy is shown (the main concept, the sub-concepts); the structure is visible at a glance.
- A content change (a concept added/revised) triggers a mind map update; the map matches the current content.
- A topic missing its mind map is a visible gap; it is not a silent omission.
- The mind map is a faithful representation (the concepts and relationships are correct); a wrong relationship is corrected.
- Mind map create/update is audit-logged with the topic, map, and timestamp.

### 4.2 Interactive, Clickable Nodes
**What it does:** Makes the mind map interactive: the nodes are clickable, so a learner can click a node to expand it (see the sub-concepts), collapse it, or jump to the related content. The Super Administrator configures the interactivity so the mind map is a navigable map, not a static image — the learner explores the topic's structure by clicking through it.

**Sub-features:**
- Clickable nodes: the nodes clickable (expand, collapse, or jump)
- Expand/collapse: a node expanded to show its sub-concepts, or collapsed
- Navigation: clicking a node navigates to the related content
- Interactivity configuration: the interactivity set per mind map
- Learner exploration: the learner explores the topic's structure by clicking
- State: the learner's exploration state (the expanded/collapsed nodes)
- Audit logging of interactivity configuration

**Super Administrator User Journey:**
1. For a mind map, Super Admin configures the interactivity: the nodes are clickable (expand, collapse, or jump to the related content).
2. Sets the expand/collapse behavior: a node expanded shows its sub-concepts; collapsed hides them (the learner controls the depth).
3. Sets the navigation: clicking a node jumps to the related content (the video, the resource for that concept).
4. Saves; the mind map is live, and a learner can explore the topic's structure by clicking through it.
5. A learner clicks a node to expand it (sees the sub-concepts), clicks another to jump to the related video; the map is a navigator, not just a picture.
6. For a node that should not be clickable (a terminal concept with no sub-content), Super Admin sets it as non-navigable (it expands but does not jump); the behavior is explicit.
7. Reviews the interactivity: the nodes behave as configured (a node that should navigate but does not is fixed); the map is navigable.
8. The interactivity configuration is audit-logged with the mind map, the configuration, and the timestamp.

**Rules & Edge Cases:**
- The nodes are clickable; the interactivity is configured per mind map.
- The expand/collapse is learner-controlled (the depth is the learner's choice); the map is not forced to one view.
- The navigation (a node jumping to content) is set per node; a terminal node is non-navigable (it does not jump).
- A node that should navigate but does not is a configuration issue; it is fixed.
- The learner's exploration state (the expanded/collapsed nodes) is the learner's; it is not reset arbitrarily.
- Interactivity configuration is audit-logged with the mind map, configuration, and timestamp.

### 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance
**What it does:** Connects the mind map to the learning content and signals the concept weight: the nodes link to the related videos and resources (the content for that concept), and the concepts are color-coded by importance (the core concepts distinguished from the supporting ones). The Super Administrator sets the links and the color-coding so the mind map is both a navigator (to the content) and a priority guide (what matters most).

**Sub-features:**
- Content links: the nodes linked to the related videos/resources
- Link target: the video/resource for the concept (the content the node points to)
- Color-coding: the concepts color-coded by importance (core vs. supporting)
- Importance mapping: the color mapped to the concept's importance level
- Legend: the color meaning shown (the learner knows what the colors mean)
- Visibility: the links and colors shown in the mind map
- Audit logging of link/color-coding changes

**Super Administrator User Journey:**
1. For a mind map, Super Admin sets the content links: each node linked to the related video/resource (the content for that concept).
2. Sets the color-coding: the concepts color-coded by importance (the core concepts in one color, the supporting ones in another).
3. Sets the legend: the color meaning shown, so a learner knows what the colors signify (the core vs. the supporting).
4. Saves; the mind map is live, with the links (the navigator) and the colors (the priority guide).
5. A learner clicks a node to jump to the related video (the content) and sees the color (the concept's importance); the map guides both the navigation and the focus.
6. For a node missing its content link (the video not yet attached), Super Admin adds the link (or flags the content gap); the change is recorded.
7. Reviews the color-coding: the importance mapping is consistent (a core concept is not colored as supporting); the legend is clear.
8. The link/color-coding changes are audit-logged with the mind map, the links, the colors, and the timestamp.

**Rules & Edge Cases:**
- The content links connect the nodes to the related videos/resources; the map is a navigator to the content.
- A node missing its content link is a gap (the content not attached); it is added or flagged.
- The color-coding is by importance (the core vs. the supporting); the mapping is consistent.
- The legend is shown; the learner knows what the colors mean (the colors are not arbitrary).
- A color-coding inconsistency (a core concept colored as supporting) is corrected; the change is recorded.
- Link/color-coding changes are audit-logged with the mind map, links, colors, and timestamp.