communications-mining
latest
false
- Getting started
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields (previously entities)
- Labels (predictions, confidence levels, hierarchy, etc.)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Reviewed and unreviewed messages
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Create a data source in the GUI
- Uploading a CSV file into a source
- Create a new dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amend a dataset's settings
- Delete messages via the UI
- Delete a dataset
- Delete a source
- Export a dataset
- Using Exchange Integrations
- Preparing data for .CSV upload
- Model training and maintenance
- Understanding labels, general fields and metadata
- Label hierarchy and best practice
- Defining your taxonomy objectives
- Analytics vs. automation use cases
- Turning your objectives into labels
- Building your taxonomy structure
- Taxonomy design best practice
- Importing your taxonomy
- Overview of the model training process
- Generative Annotation (NEW)
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and recall
- How does Validation work?
- Understanding and improving model performance
- Why might a label have low average precision?
- Training using Check label and Missed label
- Training using Teach label (Refine)
- Training using Search (Refine)
- Understanding and increasing coverage
- Improving Balance and using Rebalance
- When to stop training your model
- Using general fields
- Generative extraction
- Using analytics and monitoring
- Automations and Communications Mining
- Licensing information
- FAQs and more
Communications Mining User Guide
Last updated Nov 19, 2024
Create a data source in the GUI
User permissions required: 'Sources admin'.
Note: If you have the Sources Admin permission, you can also create a new source when you Create a new dataset.
Creating a Source in the GUI essentially sets up an empty source with defined properties (as shown below), that data can then be uploaded to via the API. The setup of this source can also be done via the API (see here), however, this method may be easier for non-technical users to easily define their source properties, before a technical user uploads the data.
Note:
This does not cover how to upload data to a source via the API. For details on this, please see the relevant section of the API docs here.
To create a data source in the GUI:
- Navigate to the 'Sources' page via the Admin console
- Select the 'New Source' button at the top of the page
- Fill in the required source properties, which include:
- Source project
- Source name
- Source title
- Source description
- Sensitive properties (that require the View sensitive data permission to view)
- Language
- Translation enabled or disabled (required Create translated sources permission)
- Select Create source.
Create source modal
