Complex Document Mapping

Overview

Document mapping requirements can vary significantly based on document structure, table configurations, and formatting. For highly complex documents, a one-size-fits-all approach may not work. Use the following recommended workflow to ensure accurate mapping and data integrity.

Why Mapping Can Be Complex?

Mapping complexity is often driven by:

• Document Structure: Non-standard layouts or nested sections.

• Table Configuration: Complex merged cells, varying column/row headers, or multiple questions per row.

• Content Placement: Mixed content types (text, images, form fields) within a single area.

Recommended Workflow for Complex Scenarios

1. Review Document Structure: Before importing, identify the tables, headers, and specific formatting that must be preserved. Determine if the document uses standard Word styles (H1, H2) which aid auto-identification.

2. Consult Advanced Training: Review the Advanced Word Mapping training materials in the Responsive Academy to understand advanced concepts like the Split function and Table Properties.

3. Test with a Copy: Always test your mapping configuration on a copy of the document first. This allows you to experiment with different marking strategies without affecting the original file.

4. Verify the Output: After a test import, review the project UI and a sample export. Check specifically for:

   • Table alignment and cell integrity.

   • Header accuracy.

   • Proper mapping of answer types (e.g., checkboxes vs. rich text).

5. Adjust and Refine: Based on the output, return to the mapping screen to adjust configurations. You may need to manually mark certain sections if auto-identification fails due to complex formatting.

6. Seek Expert Guidance: For unique edge cases or extremely large, non-standard files, consult your project lead or the Responsive configuration team for document-specific strategies.