{"_id":"584aeea99588370f00608aac","category":{"_id":"584aeea89588370f00608a4d","version":"584aeea89588370f00608a3b","project":"559ae8ec7ae7f80d0096d813","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-07-07T21:06:47.726Z","from_sync":false,"order":17,"slug":"configure","title":"Configure"},"user":"559ae88c7ae7f80d0096d812","project":"559ae8ec7ae7f80d0096d813","__v":0,"version":{"_id":"584aeea89588370f00608a3b","project":"559ae8ec7ae7f80d0096d813","__v":1,"createdAt":"2016-12-09T17:49:28.502Z","releaseDate":"2016-12-09T17:49:28.502Z","categories":["584aeea89588370f00608a3c","584aeea89588370f00608a3d","584aeea89588370f00608a3e","584aeea89588370f00608a3f","584aeea89588370f00608a40","584aeea89588370f00608a41","584aeea89588370f00608a42","584aeea89588370f00608a43","584aeea89588370f00608a44","584aeea89588370f00608a45","584aeea89588370f00608a46","584aeea89588370f00608a47","584aeea89588370f00608a48","584aeea89588370f00608a49","584aeea89588370f00608a4a","584aeea89588370f00608a4b","584aeea89588370f00608a4c","584aeea89588370f00608a4d","584aeea89588370f00608a4e","584aeea89588370f00608a4f"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"4.2.3","version":"4.2.3"},"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-07-07T21:42:01.988Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"A configuration in Semantria is a combination of language, API settings and NLP tuning. It represents a way you want documents to be processed. This means you can have different configurations for different industry verticals (\"sick\" is not a sentiment bearing word in drug research for instance), or for different types of documents (tweets can be treated differently than news documents).\n\nEach configuration is identified by a unique ID assigned by Semantria at creation time. When you first sign up for Semantria, we create a number of configurations by default with some examples of what you can have in a configuration such as queries, categories and so on.\n\nOne configuration in the account is the primary configuration. You can change which configuration is primary, but you can never delete the one that is the current primary configuration. If you send documents for processing without specifying a configuration ID, they go to the primary account.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Language\"\n}\n[/block]\nThe most important configuration setting is language. Each configuration can have only one language specified, and that language cannot be changed once the configuration is created. This is because not all settings and features are supported for every language. You must determine the language of the documents you send to a configuration. Although Semantria can detect languages, we do not route documents based on language, we merely send back to you what language we thought the document was. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"One Sentence Mode\"\n}\n[/block]\nThe next most important setting in a configuration is one_sentence mode. When a configuration is in one_sentence mode, it adapts to the language commonly used in very short pieces of content such as tweets, Instagram updates, and many other types of status updates. In these types of content, punctuation and capitalization is often missing and there is common use of acronyms, emoji, and other types of shorthand. One_sentence mode is designed to deal with these issues. We recommend not turning one_sentence mode on for content longer than 3 sentences. \nNote: One_sentence mode is not available for Tier 2 languages.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Processing Settings\"\n}\n[/block]\nSemantria supports multiple ways of interacting with the API. More information is available about this in the Integration Scenarios section. One important thing to note is that if you plan to use Excel with this configuration, it must be in polling mode, not auto-response or callback.\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Thresholds\"\n}\n[/block]\nMost of the other settings in a configuration are thresholds. These control how many of a particular output is returned, or how confident we have to be in a match before we return it to you. If you set unwanted outputs to zero, your documents will process a little bit faster and you won't have to parse the unwanted output.","excerpt":"","slug":"why-configurations","type":"basic","title":"Configurations"}
A configuration in Semantria is a combination of language, API settings and NLP tuning. It represents a way you want documents to be processed. This means you can have different configurations for different industry verticals ("sick" is not a sentiment bearing word in drug research for instance), or for different types of documents (tweets can be treated differently than news documents). Each configuration is identified by a unique ID assigned by Semantria at creation time. When you first sign up for Semantria, we create a number of configurations by default with some examples of what you can have in a configuration such as queries, categories and so on. One configuration in the account is the primary configuration. You can change which configuration is primary, but you can never delete the one that is the current primary configuration. If you send documents for processing without specifying a configuration ID, they go to the primary account. [block:api-header] { "type": "basic", "title": "Language" } [/block] The most important configuration setting is language. Each configuration can have only one language specified, and that language cannot be changed once the configuration is created. This is because not all settings and features are supported for every language. You must determine the language of the documents you send to a configuration. Although Semantria can detect languages, we do not route documents based on language, we merely send back to you what language we thought the document was. [block:api-header] { "type": "basic", "title": "One Sentence Mode" } [/block] The next most important setting in a configuration is one_sentence mode. When a configuration is in one_sentence mode, it adapts to the language commonly used in very short pieces of content such as tweets, Instagram updates, and many other types of status updates. In these types of content, punctuation and capitalization is often missing and there is common use of acronyms, emoji, and other types of shorthand. One_sentence mode is designed to deal with these issues. We recommend not turning one_sentence mode on for content longer than 3 sentences. Note: One_sentence mode is not available for Tier 2 languages. [block:api-header] { "type": "basic", "title": "Processing Settings" } [/block] Semantria supports multiple ways of interacting with the API. More information is available about this in the Integration Scenarios section. One important thing to note is that if you plan to use Excel with this configuration, it must be in polling mode, not auto-response or callback. [block:api-header] { "type": "basic", "title": "Thresholds" } [/block] Most of the other settings in a configuration are thresholds. These control how many of a particular output is returned, or how confident we have to be in a match before we return it to you. If you set unwanted outputs to zero, your documents will process a little bit faster and you won't have to parse the unwanted output.