You can customize the behavior of the extraction for individual query actions by specifying the configuration settings as query parameters in the ACI request. For example:
http://localhost:7000/?action=EduceFromFile&MatchCase=True&Grammars=place_albal.ecr
If you specify a parameter as part of a query, it overrides the configuration file settings for the parameter.
You can specify a comma-separated list of grammar files to load as the value of the Grammars
parameter. For example:
Grammars=GrammarFile[,GrammarFile2]
This corresponds to the ResourceFiles
setting in the configuration file.
You can specify a comma-separated list of entities to use as the value of the Entities
parameter. If no entities are specified in the configuration file, all public entities from the grammar files that you configured are available.
Alternatively,if your query uses several grammar files or entities, you can use wildcard expressions in the Grammars
or Entities
parameters. You can use the * wildcard to match any number of characters, or the ? wildcard to match a single character. For example:
action=EduceFromText&Text=I thought it was a bad idea. Es ist nicht gut.&Grammars=sentiment_*.ecr
This example uses all the available sentiment grammars for the extraction without you having to type a lengthy comma-separated list.
Note: The grammar files and entities must already be specified in the configuration file. There must be no space before or after a comma.
You can specify the following parameters as part of your query:
AllowMultipleResults
|
MatchWholeWord
|
AllowOverlaps
|
MaxEntityLength
|
CaseNormalization
|
MinScore
|
CJKNormalization
|
NonGreedyMatch
|
EnableComponents
|
RedactionOutputString
|
EnableUniqueMatches
|
RedactionReplacementCharacter
|
Locale
|
TangibleCharacters
|
MatchCase
|
TokenWithPunctuation
|
These parameters behave in the same way as the parameters of the same name in the configuration file. See Configuration File Settings for more information.
A query parameter takes the value of the corresponding parameter in the configuration file as its default. If that parameter is not set in the configuration file, the query uses the default value for the parameter as described in the Eduction SDK User Guide. See Eduction Parameters for more information.
|