Rosette Server can support multiple profiles, each with different data domains (such as user dictionaries, regular expressions files, and custom models) as well as different parameter and configuration settings. Each profile is defined by its own root directory, thus any data or configuration files that live in the root directory of an endpoint can be part of a custom profile.
Using custom profiles, a single endpoint can simultaneously support users with different processing requirements within a single instance of Rosette Server. For example, one user may work with product reviews and have a custom sentiment analysis model they want to use, while another user works with news articles and wants to use the default sentiment analysis model.
Each unique profile in Rosette Server is identified by a string, profileId. The profile is specified when calling the API, by adding the profileId parameter, indicating the set of configuration and data files to be used for that call.
Custom profiles and their associated data are contained in a <profile-data-root> directory. This directory can be anywhere in your environment; it does not have to be in the Rosette Server install directory.
Table 1. Examples of types of customizable data by endpoint
Endpoint |
Applicable data files for custom profile |
/categories |
Custom models |
/entities |
Gazetteers, regular expression files, custom models, linking knowledge base |
/morphology |
User dictionaries |
/sentiment |
Custom models |
/tokens |
Custom tokenization dictionaries |
Note
Custom profiles are not currently supported for the address-similarity, name-deduplication, name-similarity, and name-translation endpoints.