Indexable AFP requirements
Begin Named Group (BNG) and End Named Group (ENG) structured fields that already exist in the input AFP data can be either recognized and retained by AFP Indexer, or removed and replaced using AFP Indexer to define a new document trigger.
If existing named page groups are retained, the levels of nesting to be retained can be selected during configuration. The system determines documents based on the outermost named page groups.
When named page groups are preserved, existing index tags (TLEs) can also be preserved.
This section describes the requirements of the AFP data to be input to AFP Indexer.
|Requirements and Examples|
|Valid AFP||The AFP data must conform to the Data Stream and Object Architecture: MO:DCA Reference.|
|BDT/EDT(s)||The AFP data can contain more than one pair of Begin Document (BDT) and End Document
(EDT) structured fields, but they cannot be nested.
Example: BDT ... EDT BDT ... EDT
|Pages – BPG/EPG(s)||Pages before the start of named groups are not indexed.
Example: 2 banner pages discarded BDT BPG/EPG BPG/EPG BNG BPG/EPG (1st document) ENG ... EDT
|Existing Named Page Groups – BNG/ENG(s)||Named page groups for document boundaries can be present. The nesting level is specified
when you select to keep the existing named page groups.
You can remove named page groups and redefine boundaries by setting a new document trigger.
Existing TLEs are removed if the document trigger is redefined.
Example: 2 documents BNG (1st document) BNG/../ENG (nesting allowed) BNG/../ENG\ ENG BNG (2nd document) ENG
|Existing Indexes – TLE(s)||Existing index tags can be retained if named page groups are maintained. Index tags cannot occur outside of existing named page group boundaries.|
|Document Triggers||To add named page groups for document delineation, you must define a document trigger.
The AFP text field must be in a constant physical (print) location, in the same sequence in the case of multiple fields in that location.
If parsing is required, the parsing rules must apply consistently to the document trigger text for every document in the file.
Only Presentation Text Object Content Architecture (PTOCA) within an AFP page is supported. AFP Image, Draw Rules, Bar Code Object Content Architecture (BCOCA) objects, or PTOCA in page segments or overlays are not supported as document triggers.
Sample document trigger: BPG PTX TRN (full trigger text) EPG
|Index tags||Index tags can be created from either AFP text or No Operation (NOP) records in the
A NOP record causes an application to move to the next instruction for processing without taking any other action. Page group NOPs are found outside the logical AFP pages--they are contained in structured fields that are in the page group but not on the current page. NOP records in the AFP file are not viewable or printable, but you can use the RICOH Visual Workbench to create index tags from the data contained in them.
To make an index tag from AFP text, the AFP text must be in a constant physical (print) location or area, and in the same sequence in the case of multiple text blocks in that location. If parsing is required, the parsing rules must apply consistently to the index data for every document in the file.
Presentation Text data is the only type of data in an AFP page that is supported for use as an index tag. AFP Image, Draw Rules, BCOCA objects, or PTOCA in page segments or overlays are not supported as index tag data.
Sample index tag:
BPG PTX TRN (index text here) BPG