The Semantria service doesn't support any templates for configuration. When the user creates a new configuration, the service will setup the configuration according to the provided parameters. Parameters that are not passed will stay on default settings/values. See frontend API document for details.
Is there an interface where customers can access their configuration?
There is no interface for customers on the API. Wrappers provide the core functionality on a communication level, in which customer developers then build their code over the wrappers.
Is it possible to help us create best practice configuration for templates (Distilled best practices Lexalytics has learned from its customers)?
Helping create best practice configuration would be outside of our standard product support and require a professional services engagement.
I tried running tests.py with the keys that I was sent but got the following. Any idea what the problem is? Is there any information on what unittest.py is supposed to do?
The test.py file is a set of unit tests aimed for the automation code verification. Use this file to run the sample test of API usage. In detail, it makes two status calls, creates a custom configuration, then it fills it with two fake categories, queries and blacklisted items. To test the processing, it queues and cancels a few tasks and requests the processed data, if present on server.Processed data can be obtained if you queued the tasks beforehand. The Server doesn’t process queued tasks in real-time so you will need to wait a minute or two. All of the wrappers are implemented using the same approach, therefore the above is true for all Semantria wrappers.
After calling the method ‘QueueTask’ with a string to analyze, and with no errors reported, the results do not retrieve any data after several minutes.
The QueueTask method guarantees the queuing of the task on the server for processing but doesn’t return any processing result. To get processed data, the customer may use the OnAutoResponse event or request the data manually through the GetProcessedData method. See Wrappers integration guide for details.
How long is an ‘expected’ response for this method?
The Semantria service isn’t a real-time solution. This means that the server doesn’t start processing tasks immediately. It keeps all the pushed tasks in a queue and schedules the queued tasks for processing every 30 seconds. If there are not enough tasks to start processing, Semantria starts analyzing the tasks of the same customer in a configured interval. Pushing of lot of tasks will lead the server to start processing faster. Depending on the server configuration, tasks may be processed in up to 10 minutes interval. By default the processing time is less than 30 seconds if a bunch of tasks are queued.
What is the default user configuration, including parameters?
|concept_topics_limit||Limits the number of concept topics responded from the service.||5|
|query_topics_limit||Limits the number of query topics responded from the service.||5|
|named_entities_limit||Limits the number of named entities responded from the service.||5|
|user_entities_limit||Limits the number of user entities responded from the service.||5|
|entity_themes_limit||Limits the number of entity themes responded from the service.||5|
|doc_themes_limit||Limits the number of Document themes responded from the service.||5|
|summary_limit||Limits the number of sentences for the document summary feature.||5|
|facets_limit||Limits the number of facets which will be responded from the server.||15|
|facet_atts_limit||Limits the number of facets which will be responded from the server.||5|