<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aura – </title>
    <link>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/</link>
    <description>Recent content on Aura</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
	  <atom:link href="/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: </title>
      <link>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages/</guid>
      <description>
        
        
        &lt;h1 id=&#34;catalog-of-nlp-stages&#34;&gt;Catalog of NLP stages&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;NLP stages to compose the NLP pipeline&lt;/p&gt;

&lt;/div&gt;

&lt;p&gt;Aura Platform Team has implemented a set of natural language processing (NLP) stages in order to configure different pipelines.&lt;/p&gt;
&lt;p&gt;Select your intended stage in the left menu. Each of them is characterized by its description, path, files and configuration.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Section&lt;/th&gt;
&lt;th&gt;Content&lt;/th&gt;
&lt;th&gt;Role in the NLP process&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Identification and objective of the stage in the recognition process&lt;/td&gt;
&lt;td&gt;Descriptive purpose of the stage in the recognition process&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Path&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Class path (Python class) of an element (stage or connector)&lt;/td&gt;
&lt;td&gt;The path of each stage of the pipeline must be included in the file &lt;code&gt;pipeline.json&lt;/code&gt; for building up the NLP dynamic pipeline&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;File&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Specific training files and test set files for the NLP stage required to train and validate the NLP model&lt;/td&gt;
&lt;td&gt;Linguists must generate these files for the training and the validation of the NLP model during the data resources definition&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Configuration&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Required configuration for each NLP stage&lt;/td&gt;
&lt;td&gt;Configuration of each stage of the NLP model&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages-connectors/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages-connectors/</guid>
      <description>
        
        
        &lt;h1 id=&#34;catalog-of-nlp-connectors&#34;&gt;Catalog of NLP connectors&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;NLP connectors to compose the NLP pipeline&lt;/p&gt;

&lt;/div&gt;

&lt;p&gt;Aura Platform Team has implemented different types connectors to  join NLP stages in order to configure the pipeline.&lt;/p&gt;
&lt;p&gt;Select your intended connector in the left menu. Each of them is characterized by its description, path, files and configuration.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Section&lt;/th&gt;
&lt;th&gt;Content&lt;/th&gt;
&lt;th&gt;Role in the NLP process&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Identification and objective of the stage in the recognition process&lt;/td&gt;
&lt;td&gt;Descriptive purpose of the stage in the recognition process&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Path&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Class path (Python class) of an element (stage or connector)&lt;/td&gt;
&lt;td&gt;The path of each stage of the pipeline must be included in the file &lt;code&gt;pipeline.json&lt;/code&gt; for building up the NLP dynamic pipeline&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;File&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Specific training files and test set files for the NLP stage required to train and validate the NLP model&lt;/td&gt;
&lt;td&gt;Linguists must generate these files for the training and the validation of the NLP model during the data resources definition&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Configuration&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Required configuration for each NLP stage&lt;/td&gt;
&lt;td&gt;Configuration of each stage of the NLP model&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-normalization-pipelines/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-normalization-pipelines/</guid>
      <description>
        
        
        &lt;h1 id=&#34;catalog-of-nlp-normalization-pipelines&#34;&gt;Catalog of NLP normalization pipelines&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Catalog of NLP normalization pipelines to compose the NLP pipeline&lt;/p&gt;

&lt;/div&gt;

&lt;p&gt;Aura Platform Team has implemented a set of &lt;strong&gt;normalization pipelines&lt;/strong&gt; in order to be nested in the NLP model pipeline. They are built joining different &lt;strong&gt;normalization stages (normalizers)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In every use case, it is necessary to choose the most adequate normalization pipeline.&lt;/p&gt;
&lt;p&gt;For example, if numbers are expected to be expressed with text characters (i.e., &amp;ldquo;one&amp;rdquo;), it is useful to include the normalization stage CardinalityNormalizer to turn them into digits (&amp;ldquo;1&amp;rdquo;).&lt;/p&gt;
&lt;p&gt;Another example refers to the fact that written requests are required. In this situation, it can be important to include a normalization stage that reduces transcription mistakes.&lt;/p&gt;
&lt;p&gt;Select your intended normalization pipeline in the left menu. Each of them is characterized by its description and configuration.&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Section&lt;/th&gt;
&lt;th&gt;Content&lt;/th&gt;
&lt;th&gt;Role in the NLP process&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Identification and objective of the stage in the recognition process&lt;/td&gt;
&lt;td&gt;Descriptive purpose of the stage in the recognition process&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Configuration&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Required configuration for each NLP stage&lt;/td&gt;
&lt;td&gt;Configuration of each stage of the NLP model&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

      </description>
    </item>
    
  </channel>
</rss>
