OCR/openspec/specs/result-export/spec.md

result-export Specification

Purpose

TBD - created by archiving change fix-v2-api-ui-issues. Update Purpose after archive.

Requirements

Requirement: Export Interface

The Export page SHALL support downloading OCR results in multiple formats using V2 task APIs, with processing track information and enhanced structure data.

Scenario: Export page uses V2 download endpoints

• WHEN user selects a format and clicks export button
• THEN frontend SHALL call V2 endpoint /api/v2/tasks/{task_id}/download/{format}
• AND frontend SHALL NOT call V1 /api/v2/export endpoint (which returns 404)
• AND file SHALL download successfully

Scenario: Export supports multiple formats

• WHEN user exports a completed task
• THEN system SHALL support downloading as TXT, JSON, Excel, Markdown, and PDF
• AND each format SHALL use correct V2 download endpoint
• AND downloaded files SHALL contain task OCR results

Scenario: Export includes processing track metadata

• WHEN user exports a task processed through dual-track system
• THEN exported JSON SHALL include "processing_track" field indicating "ocr" or "direct"
• AND SHALL include "processing_metadata" with track-specific information
• AND SHALL maintain backward compatibility for clients not expecting these fields

Scenario: Export UnifiedDocument format

• WHEN user requests JSON export with unified=true parameter
• THEN system SHALL return UnifiedDocument structure
• AND include complete element hierarchy with coordinates
• AND preserve all PP-StructureV3 element types for OCR track

Requirement: Multi-Task Export Selection

The Export page SHALL allow users to select and export multiple tasks.

Scenario: Select multiple tasks for export

• WHEN Export page loads
• THEN page SHALL display list of user's completed tasks
• AND page SHALL provide checkboxes to select multiple tasks
• AND page SHALL NOT require batch ID from upload store (legacy V1 behavior)

Scenario: Export selected tasks

• WHEN user selects multiple tasks and clicks export
• THEN system SHALL download each selected task's results in chosen format
• AND downloaded files SHALL be named distinctly (e.g., {task_id}_result.{ext})
• AND system MAY provide option to download as ZIP archive for multiple files

Requirement: Export Configuration Persistence

Export settings (format, thresholds, templates) SHALL apply consistently to V2 task downloads.

Scenario: Apply confidence threshold to export

• WHEN user sets confidence threshold to 0.7 and exports
• THEN downloaded results SHALL only include OCR text with confidence >= 0.7
• AND threshold SHALL apply via V2 download endpoint query parameters

Scenario: Apply CSS template to PDF export

• WHEN user selects CSS template for PDF format
• THEN downloaded PDF SHALL use selected styling
• AND template SHALL be passed to V2 /tasks/{id}/download/pdf endpoint

Requirement: Enhanced PDF Export with Layout Preservation

The PDF export SHALL accurately preserve document layout from both OCR and direct extraction tracks.

Scenario: Export PDF from direct extraction track

• WHEN exporting PDF from a direct-extraction processed document
• THEN the PDF SHALL maintain exact text positioning from source
• AND preserve original fonts and styles where possible
• AND include extracted images at correct positions

Scenario: Export PDF from OCR track with full structure

• WHEN exporting PDF from OCR-processed document
• THEN the PDF SHALL use all 23 PP-StructureV3 element types
• AND render tables with proper cell boundaries
• AND maintain reading order from parsing_res_list

Scenario: Handle coordinate transformations

• WHEN generating PDF from UnifiedDocument
• THEN system SHALL correctly transform bbox coordinates to PDF space
• AND handle page size variations
• AND prevent text overlap using enhanced overlap detection

Requirement: Structure Data Export

The system SHALL provide export formats that preserve document structure for downstream processing.

Scenario: Export structured JSON with hierarchy

• WHEN user selects structured JSON format
• THEN export SHALL include element hierarchy and relationships
• AND preserve parent-child relationships (sections, lists)
• AND include style and formatting information

Scenario: Export for translation preparation

• WHEN user exports with translation_ready=true parameter
• THEN export SHALL include translatable text segments
• AND maintain coordinate mappings for each segment
• AND mark non-translatable regions

Scenario: Export with layout analysis

• WHEN user requests layout analysis export
• THEN system SHALL include reading order indices
• AND identify layout regions (header, body, footer, sidebar)
• AND provide confidence scores for layout detection