# 5. Export Management

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

---

## 5. Export Management

### 5.1 Choose Export Scope and Format
**What it does:** Chooses the export scope and format: the scope of the export (the scope, the data, the date) and the format (the format, the structure, the date) are chosen, so the export is defined (the choice is the definition). The Super Administrator chooses the export scope and format (the scope, the data, the date, the format) so the choice is structured and the definition is explicit.

**Sub-features:**
- Scope: the scope (the scope, the data, the date)
- Data: the data (the data of the export, the type, the date)
- Format: the format (the format, the structure, the date)
- Scope count: the count (the count of the scopes)
- Format count: the count (the count of the formats)
- Scope view: the view (the scopes, the data, the dates)
- Format view: the view (the formats, the structures, the dates)
- Audit logging of the export scope and format selection

**Super Administrator User Journey:**
1. Super Admin chooses the export scope and format: the scope (the scope, the data, the date), the data (the data of the export, the type, the date), and the format (the format, the structure, the date); the choice is explicit.
2. Sets the scope: the scope (the scope, the data, the date); the scope is the boundary.
3. Selects the data: the data (the data of the export, the type, the date); the data is the content.
4. Sets the format: the format (the format, the structure, the date); the format is the structure.
5. Views the scope count: the count (the count of the scopes); the count is the measure.
6. Views the format count: the count (the count of the formats); the count is the measure.
7. The export is defined: the scopes, the data, the dates, the formats, so the definition is complete.
8. The export scope and format selection is audit-logged with the scope, the format, and the timestamp.

**Rules & Edge Cases:**
- The scope is the boundary (the scope, the data, the date); the scope is the limit.
- The data is the content (the data of the export, the type, the date); the data is the payload.
- The format is the structure (the format, the structure, the date); the format is the shape.
- The scope count is the measure (the count of the scopes); the count is the volume.
- The export is defined (the scopes, the data, the dates, the formats); the choice is managed.
- Export scope and format selection is audit-logged with the scope, format, and timestamp.

### 5.2 Track Export Jobs and Status
**What it does:** Tracks the export jobs and status: the job of the export (the job, the scope, the status, the date) is tracked, so the exports are visible (the tracking is the watch). The Super Administrator tracks the export jobs and status (the job, the scope, the status, the date) so the tracking is structured and the watch is explicit.

**Sub-features:**
- Job: the job (the job, the scope, the status, the date)
- Scope: the scope (the scope of the job, the data, the date)
- Status: the status (the status of the job, e.g., the completed, the in-progress, the failed)
- Job count: the count (the count of the jobs by status)
- Job duration: the duration (the duration of the job, the time)
- Job view: the view (the jobs, the scopes, the statuses, the dates)
- Job export: the export (the jobs, the format, the status)
- Audit logging of the export job tracking

**Super Administrator User Journey:**
1. Super Admin tracks the export job and status: the job (the job, the scope, the status, the date), the scope (the scope of the job, the data, the date), and the status (the status of the job, e.g., the completed, the in-progress, the failed); the tracking is explicit.
2. Selects the job: the job (the job, the scope, the status, the date); the job is the task.
3. Views the scope: the scope (the scope of the job, the data, the date); the scope is the boundary.
4. Views the status: the status (the status of the job, e.g., the completed, the in-progress, the failed); the status is the state.
5. Views the job count: the count (the count of the jobs by status); the count is the measure.
6. Views the job duration: the duration (the duration of the job, the time); the duration is the time.
7. The exports are visible: the jobs, the scopes, the statuses, the dates, so the watch is complete.
8. The export job tracking is audit-logged with the job, the status, and the timestamp.

**Rules & Edge Cases:**
- The job is the task (the job, the scope, the status, the date); the job is the work.
- The scope is the boundary (the scope of the job, the data, the date); the scope is the limit.
- The status is the state (the status of the job, e.g., the completed, the in-progress, the failed); the status is the condition.
- The job duration is the time (the duration of the job, the time); the duration is the length.
- The exports are visible (the jobs, the scopes, the statuses, the dates); the tracking is managed.
- Export job tracking is audit-logged with the job, status, and timestamp.

### 5.3 Secure Delivery of Exported Data
**What it does:** Delivers the exported data securely: the delivery of the data (the delivery, the export, the method, the date) is done securely, so the data is delivered safely (the delivery is the transfer). The Super Administrator delivers the exported data securely (the delivery, the export, the method, the date) so the delivery is structured and the transfer is explicit.

**Sub-features:**
- Delivery: the delivery (the delivery, the export, the method, the date)
- Export: the export (the export, the scope, the date)
- Method: the method (the method of the delivery, e.g., the secure link, the encrypted file)
- Delivery status: the status (the delivered, the in-progress, the failed)
- Delivery count: the count (the count of the deliveries)
- Delivery view: the view (the deliveries, the exports, the methods, the dates)
- Delivery log: the log (the log of the deliveries, the date)
- Audit logging of the secure delivery

**Super Administrator User Journey:**
1. Super Admin delivers the exported data securely: the delivery (the delivery, the export, the method, the date), the export (the export, the scope, the date), and the method (the method of the delivery, e.g., the secure link, the encrypted file); the delivery is explicit.
2. Selects the export: the export (the export, the scope, the date); the export is the data.
3. Sets the method: the method (the method of the delivery, e.g., the secure link, the encrypted file); the method is the technique.
4. Views the delivery status: the status (the delivered, the in-progress, the failed); the status is the state.
5. Views the delivery count: the count (the count of the deliveries); the count is the measure.
6. Views the delivery log: the log (the log of the deliveries, the date); the log is the record.
7. The data is delivered safely: the deliveries, the exports, the methods, the dates, so the transfer is complete.
8. The secure delivery is audit-logged with the delivery, the method, and the timestamp.

**Rules & Edge Cases:**
- The delivery is the transfer (the delivery, the export, the method, the date); the delivery is the handoff.
- The export is the data (the export, the scope, the date); the export is the payload.
- The method is the technique (the method of the delivery, e.g., the secure link, the encrypted file); the method is the channel.
- The delivery status is the state (the delivered, the in-progress, the failed); the status is the control.
- The data is delivered safely (the deliveries, the exports, the methods, the dates); the transfer is managed.
- Secure delivery is audit-logged with the delivery, method, and timestamp.