December 20, 2019 Release: Search deduplication, Primary Language visualization, and more!

Expected US release: 20 December 2019

Expected AU, CA, EU, and UK release: 30 December 2019

In this release, you can now deduplicate within your search results! This allows you to search for documents more precisely, while also increasing clarity and understanding of your search results. Additionally, we’ve added the ability to view the primary language of documents in your database in Data Visualizer and added the ability to export Chronology details to PDF. 

Search deduplication 

With this release, you have the option to deduplicate within your search hits. You can now select “Deduplicate within search hits” in the More options tab.

releaseNotes52_1.png

Selecting this option means that only one copy of each document on the platform will be returned within your search results. If your search returns two or more documents that belong to the same duplicate group, search hit deduplication will return only one copy in your search. 

Note that the previous “Exclude” and “Include” duplicates options have been changed to “Hide all project duplicates” and “Show all project duplicates,” respectively. "Hide all project duplicates" will continue to be a setting disabled by default on new projects. It can be enabled by Everlaw support upon request. 

releaseNotes52_2.pngreleaseNotes52_3.png

Left image shows the original dialog box; right image shows new dialog box:

Note: If your project already has duplicates hidden, you may experience a change in prior search results or Search Term Reports. Previously, documents that have been coded, have a note applied, and/or have a hot or warm rating were NOT removed from search results, even if you choose to exclude duplicates. Now they will be removed and hidden as any other project duplicate. 

To learn more about search deduplication, check out this help article.

Better understanding of More options search settings

In addition to new deduplication functionality, we’ve updated the More options dialog box to better clarify how each setting will apply to your search.  This will make leveraging search deduplication in your review workflows can be as seamless as possible. 

First, as you apply each setting - deduplication, sampling, grouping, and removal - you will receive a real-time update of your document count. You will be able to identify exactly how many documents were added/removed from your search as a result of that setting. 

releaseNotes52_4.png

Second, you can walk through an example of how your grouping and removal settings will apply to duplicate groups. Deduplication and grouping are understandably complex topics, so we’ve made it easy for you to visualize both behaviors. Click “Show walkthrough of your search settings” in the More options dialog to reveal a walkthrough of your currently selected settings.

more_options_1.gif

For more information about the More options in search, read this article.

Export Chronology details to PDF

You can now export Chronology details (document name, Chronology date, labels, description, and relevance) from both the Chronology page and results table. In the PDF export dialog, you can now click a box that says “Chronology details.”

In addition to Chronology details, you can now export the document images and other details to PDF from the Chronology page. Just like the results table, you can include annotations (highlights, notes, redactions), metadata fields, and more.

export_to_chron.gif

Learn more about exporting in the results table in this article and Chronology exports in this article.

Primary Language filter in Data Visualizer

Users will now be able to visualize and filter documents based on their primary language. The Primary Language filter can be found in Data Visualizer under the Document tab. Simply add languages to your Expected Languages list in Project Settings to start visualizing!

releaseNotes52_5.png

You can learn more about data visualization in this article.

Unified view of document sets in one results table column

It’s now easier to refer to your document sets in the results table. In one column, you can see the type of document set (e.g. native, processed, production) followed by the name of the document set. For example, if a document was uploaded as part of a processed upload called “Example 1,” then this column will read “Processed: Example 1.”

releaseNotes52_6.png

View our full list of columns available on the results table. 

Standardizing dialog box button order and placement

To improve long term user experience and to support the logical flow of performing particular tasks, we are standardizing call-to-action button placement across the platform. Call-to-action buttons are now located in the bottom right of dialog boxes and any pages with call-to-action buttons. The primary buttons are now on the rightmost side, and any secondary buttons are on the primary button’s left.

           Original button placement                                        New button placement as of this release

releaseNotes52_7.pngreleaseNotes52_8.png

A notable change is on the Search page, where the “Begin review” button is now on the rightmost side, and the “Open data visualizer” button is on the left.

Original button placement

releaseNotes52_9.png

New button placement:

releaseNotes52_10.png

[Organization Administrator] Data type changes for email metadata

With this release, the “To,” “From,” “Bcc,” and “Cc” fields for emails will now be treated as “AddressList” or “AddressFrom” datatypes instead of “Text”. These two new datatypes will allow for email metadata to be better differentiated between email domains, email addresses, and contact names. This change is in anticipation of an exciting new feature that will leverage this parsed data for robust email metadata searches. 

releaseNotes52_11.png

For more information on metadata mapping and Processed Uploads, read this help article

[Organization Administrator] Loadfiles will be retained in the Processed Uploads table

You can now download a copy of the loadfile that was used for a processed upload. This will allow you to know exactly which loadfile was used for any given dataset should you ever need to review your upload. The download will contain all loadfiles used for the upload.

releaseNotes52_12.png

To learn more about Processed Uploads, check out this article.




Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.