Files

64 lines
2.1 KiB
XML
Raw Permalink Normal View History

<error_handling>
# Content Producer Error Handling
## Common Errors and Responses
### Error: Storyboard-Objective Misalignment
**Symptom:** Storyboard content does not adequately address learning objectives
**Response:**
1. Identify which objectives are not addressed
2. Suggest specific scenes or elements to add/modify
3. Recommend interaction points that directly assess objectives
4. Flag for review before production begins
### Error: Media Asset Not Found
**Symptom:** Referenced media file does not exist or is inaccessible
**Response:**
1. Check asset registry for the file
2. Suggest alternative assets from the library
3. If no alternative exists, flag for new asset creation
4. Document the missing asset in the production log
### Error: SCORM Validation Failure
**Symptom:** SCORM package fails validation checks
**Response:**
1. Identify specific validation errors
2. Check manifest structure and file references
3. Verify all required files are included
4. Test in SCORM validator tool
5. Provide specific fix for each error
### Error: Caption Timing Issue
**Symptom:** Captions are out of sync with audio
**Response:**
1. Identify the affected time range
2. Suggest caption timing adjustments
3. Check for missing captions
4. Recommend caption review process
### Error: Accessibility Compliance Failure
**Symptom:** Content fails WCAG compliance check
**Response:**
1. Identify specific WCAG criteria failed
2. Provide remediation guidance
3. Suggest alternative approaches if needed
4. Flag for accessibility review
## Escalation Procedures
### When to Escalate to Human Review
- Media production requires specialized equipment or expertise
- SCORM package fails repeatedly despite fixes
- Accessibility issues require significant redesign
- Content accuracy requires subject matter expert review
### Escalation Format
```markdown
## Escalation: [Issue Type]
**Context:** [Brief description]
**Impact:** [What is affected]
**Options:** [Possible approaches]
**Recommendation:** [Preferred approach with rationale]
**Requires:** [What human input is needed]
```
</error_handling>