When learning column mapping, the user trains the engine on how to map the data from the extracted lines to the user's table data. For primary lines, this mapping can diverge for different line classes.
Example
A user learned two different line samples that went to two different line classes internally in one document.
- Mapping rules #1: The user maps “Unit Price” in the document to the “Unit Price” data column and the “Total Price” to the “Total Price” for the first line sample.
- Mapping rules #2: For all lines of the second line type, the user maps “Unit Price” to “Total Price” and “Total Price” to “Unit Price”.
After applying these mapping rules, the BTE engine always uses mapping rules #1 for the lines classified to the first line type and mapping rules #2 for the lines classified as the second line type.
If you have several BTE tables in one BIC class, the engine uses the same learnset for these tables. In other words, if you used interactive learning for one BTE table, the cross-document learning, which happens if the system added the document to the learnset after document validation, applies to all BTE tables in the document.
Likewise, mapping of the column data in the lines can be done in column mapping learning (or columns highlighting) mode. The user can switch between learning (highlighting) modes through the Switch Table Highlighting (Ctrl + Q) menu option in Verifier or through pop-up menu options Show Lines and Show Columns of the document viewer in Verifier or Designer.
The user can map the column data in the lines in column mapping learning or column highlighting mode. The user can switch between the learning (highlighting) modes through the Switch Table Highlighting (Ctrl + Q) menu option in Verifier or through pop-up menu options Show Lines and Show Columns of the document viewer in Verifier or Verifier Train Mode in Designer.