- Introduction
- Setting up your account
- Balance
- Clusters
- Concept drift
- Coverage
- Datasets
- General fields
- Labels (predictions, confidence levels, label hierarchy, and label sentiment)
- Models
- Streams
- Model Rating
- Projects
- Precision
- Recall
- Annotated and unannotated messages
- Extraction Fields
- Sources
- Taxonomies
- Training
- True and false positive and negative predictions
- Validation
- Messages
- Access control and administration
- Manage sources and datasets
- Understanding the data structure and permissions
- Creating or deleting a data source in the GUI
- Preparing data for .CSV upload
- Uploading a CSV file into a source
- Creating a dataset
- Multilingual sources and datasets
- Enabling sentiment on a dataset
- Amending dataset settings
- Deleting a message
- Deleting a dataset
- Exporting a dataset
- Using Exchange integrations
- Model training and maintenance
- Understanding labels, general fields, and metadata
- Label hierarchy and best practices
- Comparing analytics and automation use cases
- Turning your objectives into labels
- Overview of the model training process
- Generative Annotation
- Dastaset status
- Model training and annotating best practice
- Training with label sentiment analysis enabled
- Understanding data requirements
- Train
- Introduction to Refine
- Precision and recall explained
- Precision and Recall
- How validation works
- Understanding and improving model performance
- Reasons for label 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™
- Developer
- Uploading data
- Downloading data
- Exchange Integration with Azure service user
- Exchange Integration with Azure Application Authentication
- Exchange Integration with Azure Application Authentication and Graph
- Fetching data for Tableau with Python
- Elasticsearch integration
- General field extraction
- Self-hosted Exchange integration
- UiPath® Automation Framework
- UiPath® official activities
- How machines learn to understand words: a guide to embeddings in NLP
- Prompt-based learning with Transformers
- Efficient Transformers II: knowledge distillation & fine-tuning
- Efficient Transformers I: attention mechanisms
- Deep hierarchical unsupervised intent modelling: getting value without training data
- Fixing annotating bias with Communications Mining™
- Active learning: better ML models in less time
- It's all in the numbers - assessing model performance with metrics
- Why model validation is important
- Comparing Communications Mining™ and Google AutoML for conversational data intelligence
- Licensing
- FAQs and more
Communications Mining user guide
Maintenance
Learn more about managing per-tenant quotas for Communications Mining™, and the model version deprecation process.
Quotas
To access quotas, navigate to the Administration page and then select the Maintenance tab, which will display the Quotas page.
The Quotas page allows you to view and manage quotas that are enforced for Communications Mining™ in the current tenant.
All users can view quotas by default. However, to request increases or decreases to each quota, they must have assigned the IXP Service Admin role as an Automation Cloud user or the Tenant admin permission as a legacy user.
For certain quotas, you will also be notified through the Notification Service that you are approaching the limit and should request an increase.
Modifying the quotas table view
To change the view of the Quotas in Current Tenant table, proceed as follows:
-
Select the ellipsis for each column header.
-
Select one or more of the following options from the ellipsis menu:
- Sort by ASC - Sorts items in ascending order.
- Sort by DESC - Sorts items in descending order.
- Pin to left - Pins the current column to the left.
- Pin to right - Pins the current column to the right.
- Filter - Allows you to filter through the current table by selecting the column, the action, and adding a value. In addition, you can select the following options:
- Add filter to add multiple filters to the table.
- Remove all to delete all filters that apply to the table.
- Hide column - Hides the current column.
- Manage columns - Allows you to hide current columns or reveal hidden ones by turning off or on the toggle for each column. In addition, you can select the following options:
- Hide all to hide all columns.
- Show all to reveal all hidden columns.
Modifying quotas
To change the limit for quotas, proceed as follows:
-
Select the Edit Sources quota limit icon for each table cell.
-
In the side panel that appears, set the new limit by selecting the spinner controls, which allow you to increase or decrease the value.
-
Select Update to save the changes, or Cancel to close the side panel, without applying any changes.
Note:An error message appears if your limit request is too high when changing the quota limit. For a further increase, contact your Account Manager.
Deprecated models
You must have assigned the IXP Service Admin role as an Automation Cloud user, or the Tenant admin permission as a legacy user.
The Deprecated Models page shows you any model versions for datasets in your tenant that will soon be deprecated. All the production datasets are using more recent, improved model versions.
Having an empty page is expected, because it means that no model is going to be deprecated soon.
Notice on model deprecation and update requirements
To ensure optimal functionality and security, older pinned model versions (which will be at least 12 months old) may be scheduled for deprecation.
Deprecation announcement
To ensure a smooth transition, all deprecated models are flagged well in advance. You can find early deprecation indicators both within this page and in the Models page of the relevant dataset. This proactive approach gives you sufficient time to adjust your work without disruption.
Transition period
Following the initial announcement, you have a transition period of no less than three months. After this period ends, deprecated versions will be deemed unsupported. Consequently, unsupported versions will not be accessible via the API.
Unpinning deprecated models
You have to unpin deprecated model versions after pinning a more recent model version within the same dataset. This ensures the smooth continuation of service and API calls during the transition.
Updating production automations
You should immediately update the production automations that utilized the deprecated models, to a more recent model version. These changes prevent any potential interaction with deprecated models.