Connector Framework Server 24.3

# HeaderEntityMatchLimitN

The maximum number of columns to match with the entities specified by the corresponding HeaderEntityN parameter. After Eduction finds this number of columns with headers that match the header entities, it stops searching subsequent columns, so Eduction does not spend time looking for further matches.

You might set this parameter if you want to see some matches for a particular entity but would prefer to ignore further matches in favor of reducing the processing time.

If the HeaderEntityN parameter specifies multiple entities, using a wildcard or a comma-separated list, the limit applies separately to each entity. For example, the following configuration would permit up to three matches for English date landmarks, and up to three for French date landmarks, and so on:

    HeaderEntity0=pii/date/dob/landmark/eng,pii/date/dob/landmark/fre,pii/date/dob/landmark/spa
    HeaderEntityMatchLimit0=3

Eduction applies the limit after post-processing, so any matches that are discarded by post-processing do not count towards the limit.

The limit applies only to matches in a single table. Eduction resets the limit when it encounters a table delimiter.

Type: | Integer
Default: | No limit
Required: | No
Configuration Section: | Any section that you have defined for Eduction settings
Example: | With the following configuration Eduction finds a maximum of three columns that match the `pii/date/dob/landmark/all` entity. `HeaderEntity0=pii/date/dob/landmark/all HeaderEntityMatchLimit0=3`
See Also: | HeaderEntityN CellEntityMatchLimitN MaxSearchHeaderRow

Copyright 2024 Open Text
Version 24.3 | Last updated June 2024

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: IDOL Connector Framework Server 24.3

Topic Title: HeaderEntityMatchLimitN