Type Info

Structure:

The Info type consists of several attributes:

• id: Unique identifier of the index found
• name: Name of the index found
• numPage: The number of the page where the index was found
• idUnit: number that determines the instance to which this date belongs (Useful if the index multiplies e.g.: HT1, HT2, HT3 will have the same index information (name and id) but with a different idUnit:1, 2 or 3
• marker: An object that determines the marker found. Consisting of:
  • text: marker found on document
  • rectangle: rectangle(x1,y1,x2,y2): where the marker was found
  • sourceValue: the original text found on the document
• value: An object that determines the value found on the document. Consisting of:
  • text: value found
  • rectangle: rectangle(x1,y1,x2,y2): where the value was found
  • sourceValue: the original text found on the document
• customZonePage: If there is a customization : number of the page where this customization is located
• customZone: rectangle(x1,y1,x2,y2): If there is a customization : area corresponding to the customization

Example:

{  
   "marker":{  
      "text":"facture",
      "sourceValue":"facture",
      "rectangle":{  
         "x1":724.0,
         "y1":641.0,
         "x2":876.0,
         "y2":665.0
      }
   },
   "value":{  
      "text":"31/10/2015",
      "sourceValue":"31.10.2015",
      "rectangle":{  
         "x1":683.0,
         "y1":779.0,
         "x2":805.0,
         "y2":798.0
      }
   },
   "idUnit":1,
   "id":"DATE_INDEX",
   "name":"Date",
   "numPage":1
}

Type ArticleLineInfo

Structure:

An article line is simply a slightly more advanced Info type containing a list of info:

• ID: The unique identifier of the index row found. Works in the same way as an index ID
• name: Name of the index row found
• numPage: The number of the page where the row was found
• idUnit: Row instance number Ex: If Open Bee™ Scan Capture finds 27 rows, all rows will have the same index information (id and name) since they come from the same row pattern. But each one will have a different idUnit: 1, 2, 3, 4, 5, … 27
• indexInfo: List of Info Objects Found in the Current Row : A row is made up of values to be found, each value corresponds to an Info object found.

Example:

{  
   "indexInfos":[  
      {  
         "marker": voir info,
         "value": voir info,
         "idUnit":8,
         "id":"MONTANT_ARTICLES_INDEX",
         "name":"Montant",
         "numPage":3
      },
      {  
         "marker": voir info,
         "value": voir info,
         "idUnit":8,
         "id":"DATE_ARTICLES_INDEX",
         "name":"Date",
         "numPage":0
      },
      {  
         "marker": voir info,
         "value": voir info,
         "idUnit":8,
         "id":"SITE_ARTICLES_INDEX",
         "name":"Site",
         "numPage":3
      }
   ],
   "idUnit":8,
   "id":"ARTICLES_INDEX",
   "name":"Articles",
   "numPage":3
},