Supported Load File Formats
Most common functionality from the load file formats listed below is supported in ReadySuite. However, if you find a feature not implemented fully or properly, please contact us so that we may correct or alter it.
Summation (.dii, .edii)
ReadySuite supports the most common tokens and features from the Summation DII load file. Values are read and populated for both @FIELD and @C FIELD styled tokens. When exporting to this file format, if a field being exported is a standard dii token, it will not be designated with an @C (i.e. @TO would be used instead of @C TO).
When determining page numbers, ReadySuite uses the @T token for page identifiers. In addition, this value is placed in the DOCID metadata field.
Due to memory issues, multi-line tokens are read but their values are ignored and not stored in metadata fields.
Regarding attachment ranges, ReadySuite supports reading the @PARENTID token to determine parent/child groups.
When reading a DII file with multi-page image references, ReadySuite will first attempt to use either ENDDOC, ENDDOC# or PGCOUNT values to determine the document page count. Otherwise, if the image file is found and/or de-compressible, ReadySuite will retrieve the frame count to determine the documents ending number and page count.
Opticon (.opt, .log)
The Opticon load file format is believed to be fully implemented in ReadySuite. During import, folder break and box break flags are ignored. When processing a record with a page count and no additional page rows, ReadySuite will automatically determine the missing page id's based on the record's alias.
Currently, ReadySuite supports only IM and FD code identifiers. IS and IO records are currently ignored and will be implemented in a later release. For document flag designators, any value placed in this field is assumed to be a new document break.
If a 'C' is encountered for a document flag it will be parsed as an attachment to the previous parent document.
When an FD record is encountered, the description value will be placed in the FOLDER metadata field.
EDRM XML (.xml)
ReadySuite currently supports only Batch, Document, Image, Text, Native and Tag references from the EDRM XML schema.
When exporting to this file format, if metadata fields are being included, ReadySuite will check if the field is a standard field name and apply its data type appropriately. Otherwise, tag data types are set to Text. We expect to expand upon this feature in a future release.
Supported Image File Formats
ReadySuite officially supports the following image formats, though more may be supported than listed.