# Reader, Document Extraction, and OCR

Reader, Document Extraction, and OCR on Evotec with installation guidance, setup notes, reference details, and project documentation.

Project

PSWriteOffice

PowerShell document automation across OfficeIMO's document, spreadsheet, presentation, PDF, Project, Access, EPUB, invoicing, and conversion engines.

[View on GitHub](https://github.com/EvotecIT/OfficeIMO/tree/master/PowerShell/PSWriteOffice) [Visit Website](#) [Releases](https://github.com/EvotecIT/PSWriteOffice/releases/tag/v3.0.5) [Changelog](#) [Get package](https://www.powershellgallery.com/packages/PSWriteOffice)

Stars**722**

Forks**84**

Open issues**2**

PowerShell Gallery downloads**5184525**

Release**v3.6.2**

Language: C# Updated: 2026-11-22

Documentation

Detect formats and extract normalized documents, chunks, hierarchy, tables, visuals, assets, OCR text, and ingest results. Includes examples and cmdlet links.

Reader is the cross-format path for search, review, ingestion, migration, OCR, and AI preparation. Its 15 exported commands expose the normalized OfficeIMO.Reader model and the easy local image OCR entry point without forcing the caller to switch on every native document type.

## What Reader returns

- `Get-OfficeDocument` returns the normalized document envelope.
- `Get-OfficeDocumentDetection` reports detected format and routing evidence.
- `Get-OfficeDocumentCapability` explains the selected adapter's supported output.
- `Get-OfficeDocumentHierarchy` exposes section and structural relationships.
- `Get-OfficeDocumentChunk` returns bounded text/content chunks.
- `Get-OfficeDocumentStructured` exposes structured content.
- `Get-OfficeDocumentTable`, `Get-OfficeDocumentVisual`, and `Get-OfficeDocumentAsset` return non-text material explicitly.
- `Get-OfficeDocumentBatch` and `Get-OfficeDocumentIngest` support pipeline-scale processing.
- `Search-OfficeDocument` searches the normalized result.
- `Get-OfficeImageText` performs local image OCR and can return either plain text or the canonical typed OCR result.

## Choose Reader versus a native family

Use Reader when downstream behavior is common across file formats: indexing, chunking, extraction, discovery, classification, previews, and bulk ingest. Use Word, Excel, PowerPoint, PDF, Visio, or another native family when the script must modify format-specific objects and preserve their native semantics.

Reader adapters are modular. A deployment can carry only the adapters it needs, while broader presets compose multiple local formats. Optional OCR, web, and process-backed integrations have separate dependency and trust boundaries.

## Task guides

- [Search across Office and document files](/projects/pswriteoffice/docs/reader-search-corpus/)
- [Extract chunks, tables, and assets](/projects/pswriteoffice/docs/reader-chunks-tables/)
- [Build bounded ingestion pipelines](/projects/pswriteoffice/docs/reader-ingest-pipelines/)

## Operational pattern

Detect first, inspect capabilities, extract the required surfaces, and record warnings/provenance with the output. Do not silently reduce a document to plain text when tables, visuals, or assets matter to the consumer.

See the [document Reader examples](https://github.com/EvotecIT/PSWriteOffice/tree/main/Examples/Reader) and search the [command reference](/projects/pswriteoffice/api/) for `OfficeDocument`.

<!-- PowerForge markdown artifact sha256:4EBBE4ACF017EB362475BBD4972A40E3DD9A24744C616E16118411CAD1D5A9AC -->
