Configuration Routes allow for the use of a consistent identifier for API document processing.
In previous versions of Semantria, users were required to change the call made to the API if they wished to change the configuration documents were being sent to. With configuration routes, that no longer has to happen. Users can now add configurations to a route to allow for the swapping of configurations or routing to different languages.
The use of Configuration Routes is not mandatory. If using the Semantria API, you can specify a particular configuration's ID; if using Excel or Spotlight, you can specify the configuration name when processing. However, we recommend creating and using configuration routes for simplicity of configuration management.
The use of Configuration Routes is not mandatory
If using the Semantria API, you can specify a particular configuration's ID; if using Excel or Spotlight, you can specify the configuration name when processing.
However, we recommend creating and using configuration routes for simplicity of configuration management.
- Configuration routes can include 1 configuration per language
- Configurations can be in more than one configuration route
- Configuration routes are group specific, that is a route in a Semantria user group can only include configurations from within the same group
With Configuration Routes, Semantria users can promote configurations to production without having to make any code changes. A simple change to the configuration route can swap out an older configuration for a newer, updated version.
A Configuration Route can contain 1 configuration from each language. Previously users had to specify a specific configuration per language, now users are able to place different languages into a route, and all they need to specify when sending content is the route and a language code. The route will then send the content to the configuration that matched the language specified. If no language is specified, language detection will be run and the content routed to the configuration associated with the detected language. If no configuration is specified for the language detected, or the language is unsupported, Semantria will use the default language for the configuration route. Output will likely not be optimal.
In Spotlight, under Menu is the new option for Configuration Routes.
Creating a new configuration route by clicking on the '+'.
In the configuration route panel users can select from available configurations within their group to add to the configuration route. A route can have one configuration per language.
Once an account has configuration routes they are listed on the left hand side of the configuration route page. Here they can be expanded or collapsed to show the configurations within them.
Clicking on a configuration within a route shows the information about that configuration. Clicking on a feature (entities, sentiment, etc.) takes you to the configuration management page for that item in that configuration.
To edit an existing route hover over the name of the route and click on the pencil icon. This will open the same editor as the creating a configuration route and here configurations can be swapped out as needed.
Updated 16 days ago