Grooper Help - Version 25.0
25.0.0017 2,127
  • Overview
  • Help Status

OPEX Import

Import Provider Grooper.Core

OPEX XML Interface (OXI) Import For OPEX Scanning Devices (OSD)

Remarks

The OxiImport provider enables automated ingestion of scanned document batches produced by OPEX scanning devices using the OPEX XML Interface (OXI) specification.

Overview

  • Processes .oxi files and associated scanned images from a directory structure defined by the OPEX OXI Interface Specification.
  • Converts OXI batches, transactions, and pages into Grooper Batch Folders and Batch Pages, mapping OXI metadata and content to Grooper's data model.
  • Supports both single-batch and multi-batch import modes, with flexible options for file and folder disposition after import.

Usage Scenarios

  • Automated Import: Monitor a directory for new OXI batches exported from OPEX devices and import them into Grooper for downstream processing.
  • Batch Segmentation: Use Single OXI Mode to create a separate Grooper batch for each OXI batch, or aggregate multiple OXI batches into a single Grooper batch.
  • File Management: Prevent reprocessing by renaming OXI files after import or moving processed folders to an archive location.

Integration and Behavior

  • OxiImport is typically used as an Import Provider within an Import Behavior on a Content Type.
  • The importer recursively scans the base directory, processes each .oxi file, and creates Grooper batches, folders, and pages according to the OXI structure and mappings.
  • Metadata and attributes from OXI XML are mapped to Grooper fields, supporting downstream classification, extraction, and workflow.
  • Disposition options (renaming, moving) help manage source files and prevent re-import.

Best Practices and Limitations

  • Ensure the directory structure and file naming conventions match the OPEX OXI Interface Specification for reliable import.
  • Configure content mappings to align OXI types with the correct Grooper Content Types.
  • Use disposition options to avoid duplicate imports and maintain a clean import source directory.
  • OxiImport does not support sparse import mode; all content is fully ingested.

Properties

NameTypeDescription
Import Source
Disposition
OXI Settings
Processing Options

See Also

Used By

Notification