In this update we have added the ability to alter some of the output that SSV provides.
Users can now:
- edit sentiment polarity ranges
- add and edit entities
- change document sentiment
SSV now supports customizing sentiment polarity range per project.
In the sentiment range editor users can find the option to set the range for both 3-point and 5-point sentiment scales.
Document vs. Feature sentiment
It is important to note that the sentiment ranges for documents and features are separate.
Changing the Document Polarity Ranges will only affect document sentiment score polarity.
Changing the Feature Polarity Ranges will affect all features (eg. sentiment phrases, entities, themes, etc.)
The above images show the default scales for Document Polarity Ranges and Feature Polarity Ranges in both 3 and 5 point scales. Note that Document Polarity and Feature Polarity have different ranges by default.
Editing scales is useful for situations where large numbers of features or documents are categorized as a polarity that might not fit with content. For example, if query hits that are obviously positive to a reader are being assigned a negative polarity users can adjust the neutral range so that more positively scored neutral items are then assigned a positive score.
Adding or editing entities in SSV will not apply any changes to configurations.
Adding and editing entities is per document only.
Manually adding an entity in a document will not result in that entity being automatically located in any other document.
In the document view users can now add and edit entities.
This is useful in cases like where an entity is misspelled or a new entity is located by a reader in a document.
To add an annotated entity to a document click on the Add new Entity plus icon on the right side of the Entities header.
Adding an entity will bring up the new entity view as seen below.
In this view users type the entity under Entity, then select the Type of the entity from the dropdown list.
Selecting one of the Sentiment Polarity levels will change the Sentiment Score to the middle score for that polarity.
For example, under the default values of feature sentiment, a negative polarity would be set to -0.5, neutral to 0, and positive would be assigned a 0.6 sentiment score.
The Comments section can be used to explain why a user is adding an entity. Please note that comments are not currently exposed once an entity has been added. Future functionality will expose these comments to users.
Below an example of an added entity can be seen.
In addition to being able to add entities to a document, we have added the ability to edit existing entities. Editing found entities is useful for correcting sentiment, misspellings or even deleting misidentified entities.
Editing an existing entity is as easy as clicking the edit icon that appears when hovering over an entity.
Edited entities are denoted by a *
Clicking on the edit button will pull up an edit view much like the add view.
In the edit view users can change Entity, Type, Sentiment Polarity and Sentiment Score for the entity.
Making any changes to the entity will bring up a comment section for a user to document why changes were made.
An option not found in the add entity view is the option to delete the entity. Clicking on delete will ask for confirmation of the delete an allow the user to enter a comment about why the entity is being deleted.
Changes are made to document sentiment are document specific and will not percolate across other documents, projects or configurations.
Editing document sentiment is useful for when a document contains nuanced sentiment that a reader can identify but NLP may have missed.
To edit the sentiment of a document hover over the document sentiment in the document view. This will bring up the edit icon.
Clicking on the edit icon will bring up the Edit Document Sentiment view on the right-hand side of the document view. Here users can set the sentiment of the document. Just as with the entity editor changing the Sentiment Polarity will place the Sentiment Score in the middle of that polarity range.
Users now have the ability to choose what columns are displayed in the document list widget. This allows for dashboards to be tailored to show exactly what information is pertinent to the end user.
The document widget has a new icon in the widget header as seen in the image below.
Clicking on the Column Chooser icon brings up the display view as seen in the below image.
In the Display view there are two sections, Available in data source and Not available in data source.
If all the data sources in a project have the same metadata mappings then there will not be anything in the latter section, regardless of data source. If data sources within a project have different mappings then depending on the data being displayed, different items will be in each section.
For example, in the above image the data source that is currently being displayed only has ID, Sentiment and Text. Other data sources (collections) have additional metadata, which is why they are listed in the Not available in data source section.
If a data source does not have a field that is being displayed then the column header will have a strike through the name. This can be seen in the above images in the Source column.
The new Crosstab widget allows pivot-line presentation of results. This widget allows for the display of collocations of multiple features.
The above image shows phrases compared to topics, which allows users to see the frequency of sentiment phrases occurring with a particular topic hit. One possible use could be comparing the entity type company to themes to see what themes are commonly occurring with mentions of certain companies.
Each cell contains the number of documents that hit on the column item and row item. In the above example, topics are being compared with phrases, so each number represents the documents that hit on the topic in a given row and the phrase in the column.
For example, the topic "Accommodations-Room-Cleanliness" appears in 96 documents with the phrase "clean". However it appears in 0 documents with the phrase "excellent".
The coloring is determined by the deviation from 0, and can be disabled under chart options.
Currently users can compare topics, entities (all or by type), phrases, themes or categories. Custom fields and metadata fields are coming soon.
Over time graphs now have an option to display over Quarters, adding additional functionality for business users.
The filter panel has been updated to allow for more than just the top 10 entries. Clicking Show More will add the next top 10 entries to the displayed items.
In addition to Show More, searching for filter now searches the entire set of analytic items instead of just the top 50.
The Explore option now available in most widgets. Exploring is useful for seeing things that collocate with the item being explored.
Clicking Explore under an item does two things:
- It adds the item being explored to the widget filter under "All of these"
- It hides the explored item from that widget
The item that is being explored is hidden because by adding that item to the filter list, the item will occur in every document that is now shown in the widget. If the item is not hidden it will dominate whatever widget being explored, as every document in the filtered document set will contain the item. By automatically hiding the item we eliminate the excess data for the user.
Remove the item from the filter panel and unhide the item.
Updated 4 months ago