Rapid Recall Key 28–54

1. Native: original file format. Near-native: converted/extracted close to original while preserving needed context.
2. IA: organizes a body of information for navigation, labeling, browsing, search, retrieval and user understanding.
3. IA components can include navigation maps, Metadata maps, controlled vocabularies/taxonomies/ontologies, search specs, use cases and user flows—any four source-supported examples.
4. Keyword: specified literal terms. Semantic: meaning/context/relationships.
5. Lack of table structure does not remove ownership, sensitivity, retention, accuracy, context, search, lineage or compliance requirements.
6. Workflow: routes content/documents through repeatable tasks/approvals, assigns work and exposes status.
7. Plan: Plan Records Management; Develop Content Strategy; Create Content Handling Policies; Define Content Information Architecture.
8. Manage lifecycle: Capture Records/Content; Manage Versioning/Control; Backup/Recovery; Manage Retention/Disposal; Audit Documents/Records.
9. Publish/Deliver: Provide Access/Search/Retrieval; Deliver Through Acceptable Channels.
10. Capture Metadata at intake because later ownership, classification, security, retention, versioning, retrieval and e-discovery become less reliable if context is missing.
11. ECM: enterprise-wide coordination of content-management capabilities, governance and lifecycle processes—not merely one repository.
12. DMS: document capture/version/workflow/rights/retrieval. CMS: content creation/publication/reuse. Records System: formal classification, retention, legal and disposition controls.
13. Workflow software adds routing, task assignment, status, approvals/escalations and repeatability.
14. XML: markup/schema-friendly representation with explicit structure. JSON: lightweight text interchange.
15. RDF/SKOS/OWL: semantic/knowledge representation, controlled knowledge structures and ontologies/relationships.
16. Litigation response playbook: cross-functional procedure for identifying, preserving, collecting, processing/reviewing and responding to litigation information, including roles/escalation/hold actions.
17. E-discovery data map: inventory of ESI repositories, systems, custodians, formats/locations and retention/destruction information used to scope response.
18. Readiness assessment: test practices, repositories/volumes, legal risk, technology/integration, sponsorship, skills, user needs, culture/process readiness and migration before large implementation.
19. Culture can be harder because users must abandon uncontrolled habits, adopt common Metadata/workflows and accept governance/ownership changes; software installation alone does not change behavior.
20. Information Governance: enterprise policies, standards, roles, decision rights, oversight and cross-functional accountability.
21. Information proliferation: duplicates/obsolete copies, storage cost, search difficulty, protection exposure and larger retention/e-discovery scope.
22. Govern quality through ownership/standards, Metadata/classification, appropriate version/control, content-quality expectations, review/audit, feedback and metrics.
23. Records KPI families can include compliance/retention-disposition, retrieval/availability, classification/indexing, training, cost/efficiency and business-process integration.
24. E-discovery KPIs: time/cost to identify/collect/process/review; duplicate/irrelevant reduction; processing/review efficiency; responsiveness/lifecycle performance—any two.
25. ECM metrics: adoption/satisfaction; uptime/users; storage; search/retrieval; workflow/paper/cost reduction; complaints/training; risk mitigation—any three.
26. Precision = relevant retrieved ÷ all retrieved. It measures result-set purity.
27. Recall = relevant retrieved ÷ all relevant that exist. It measures reach/coverage.

← Rapid Recall 28–54 · Blank-Page Rebuilds →