SaaS / Hosted Monthly Release Notes - February 2021 (10.6.001 - 10.6.002)

Manage Documents > Imports: Option to automatically ignore unmapped fields in imported flat files

When creating a new Imports job using a flat file, users can choose to ignore imported fields that they do not want to map or match to existing import fields. This functionality allows organizations to map only the fields they need and ignore the rest.

Field Map page showing New field

To access this functionality, go to the Manage Documents > Imports page and click Add. In the Import window, on the Field Map page, the following message appears: Update all Action values of New to Ignore if no Case field is chosen. Click the Apply button to ignore fields that have no value in the Case field column.

Import page showing Action column

Portal Management > Cases and Servers: Case creation date and time

The creation date and time for a case now appear in a new column on the Cases and Servers > Cases page, as shown in the following figure. This column is still available on the Cases and Servers > Deleted Cases page.

Cases page showing the Creation date column

SaaS / Hosted Monthly Release Notes - January 2021 (10.5.011 - 10.6.000)

Imaging: Support for Microsoft Publisher and Microsoft Project files

The Imaging feature now supports the .pub (Microsoft Publisher) and .mpp (Microsoft Project) file types. Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Note: Only files created using Microsoft Publisher 2000 or later are supported.

SaaS / Hosted Monthly Release Notes - January 2021 (10.5.009 - 10.5.010)

New search operator: not w\0

Nuix Discover now supports the not w\0 search operator.

For example, to find all documents that include Word01 or Word02 or Word03 but exclude documents that include Word04, you can run the following search:

Word?? not w\0 Word 04

The application finds all words in the index that meet the criteria for Word?? and excludes words after the not w\0 proximity operator (in this case, Word 04).

OCR: Updated OCR engine

Nuix Discover now uses ABBYY FineReader Engine for Optical Character Recognition (OCR) processing. This update affects the OCR processing option on the Tools menu on the Documents page, the Production Print feature, and the Exports feature.

The requirements and options available for OCRing image files in each of these areas have not changed. Only the OCR engine has changed. The following differences are due to how ABBYY processes files:

  • ABBYY cannot access secured PDF files.
    • If a user submits a secured PDF for OCR using the Tools menu on the Documents page, an error appears. In this instance, the Document OCR Status field contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • If a user produces a secured PDF as an image but no endorsements (redactions, headers, footers) appear on the image and the option to embed text in PDFs is selected, then a message appears on the Production > History page indicating that an error occurred during processing. Users can click a link on the page to access the rendition documents that generated the error. The Document OCR Status field for those rendition documents contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • Note: If endorsements are applied to the image, ABBYY attempts to make the file searchable.

    • If a user exports a secured PDF file, ABBYY is unable to embed text in non-searchable pages within the file if the following conditions exist:
      • The option selected for image format is Convert to Searchable PDF or Embed Text in Existing PDFs, and
      • No endorsements are applied on the image.
      • If non-searchable pages are present in the PDF, a message appears on the Export > Warnings page indicating which documents contain searchable files that were not exported.

  • ABBYY recognizes text within files using languages selected by users. Users must select at least one language. While selecting all languages that may be present in the document set could provide more accurate results, we recommend that users select no more than 10. Selecting more languages increases processing time and may result in lower quality results.
  • If a user submits a document for OCR using the Tools menu on the Documents page and any page in the document fails in the process, the application does not create a .txt file. Additionally, if the option to embed text in a PDF is selected, the application does not return an updated PDF file. The same is also true if a user chooses to embed text in a PDF using the Production Print or Export features.
  • Note: In previous versions, the application was able to work around these issues using Nuance, but there are no workarounds with ABBYY at this time. However, we have found that ABBYY does not encounter errors on pages that Nuance was unable to successfully OCR. For example, Nuance failed to OCR any pages that were missing content. ABBYY does not encounter this failure.

Case Setup > People Identity (Names Normalization)

Enhancements have been made to Names Normalization jobs so that non-similar names are more likely to be linked to different identities.

Manage Documents > Imports: New default delimiter on the Field Map page

When creating a new Imports job using a flat file, on the Field Map page, the default Delimiter value is now "; (59)" when one of the following is selected in the Case field column:

  • People - To
  • People - CC
  • People - BCC

Manage Documents > Ingestions: NIST list updated - September 2020

The Ingestions feature now uses an updated version of this list, released in September 2020. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl/nsrl-download/current-rds.

SaaS / Hosted Monthly Release Notes - December 2020 (10.5.005 - 10.5.008)

Password requirement indicators on the login page

When you change your password in Nuix Discover, the application now displays the password strength requirements, as configured by your administrator, and alerts you if passwords do not match. An example is shown in the following figure.

Nuix Discover login page showing the password requirements.

Note: This applies to Ringtail authentication.

An administrator sets the password requirements on the Portal Management > User Administration > Account Settings page.

Translate documents into Russian

The Translate feature now supports Russian as a target language for both the Google and Microsoft translation services. Russian is also included as a choice for the Translation Languages system field. You can include Russian translations in productions.

Manage Documents > Exports > Update Image settings for exports

When converting images to PDF or from PDF to single-page TIFF, administrators now have the option to select the image size during export. When converting from PDF to single-page TIFF, administrators also have the ability to convert color PDFs to JPG files, as opposed to black and white TIFF files. You can access both options on the Image settings page in the Export window, as shown in the following figure.

Export window > Image settings page
  • To access the new Paper size option, in the Image settings window, click the Settings icon. You can select either Letter or A4. The default selection is based on default settings for Automated Imaging, but can be changed for each export.
  • Note: Only files that are converted to another file type based on what you selected in the Image format list will be affected by this setting.

  • To convert color PDFs to JPG files, in the Image format list, select Convert PDFs to TIFF, and then select Auto-detect color and render to JPG. The default selection for this option is based on the default settings for Automated Imaging, but can be changed for each export.
  • You can then enter the appropriate values in the Image resolution (DPI) and JPG quality (%) boxes. You can change the default values in these fields for each export.

Note: Footers, headers, redactions, and highlights are endorsed on the original image. If that image is converted at export (an image to PDF or a PDF to TIFF or JPG), the resulting files will have Letter or A4 dimensions. However, because the footers and headers were applied on the original image, they may not be positioned in the footer or header of the exported image file.

Manage Documents > Imaging: Support for .ics and .xps file types

The Imaging feature now supports the .ics and .xps file types.

  • An .ics file is a calendar file saved in a universal calendar format that is used by several email and calendar programs, including Microsoft Outlook.
  • An .xps file is a document that contains fixed page layout information written in the XPS page description language. This file type defines the layout, appearance, and printing information for a document. XPS files are similar to PDF files, but are saved in Microsoft’s proprietary XPS format.

Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Manage Documents > Ingestions: Group multi-segment AD1 files

When running an ingestions job, multi-segment AD1 files are now grouped in the same processing task.

An AD1 file is a Forensic Toolkit FTK imager Image file.

Cases and Servers: New case option to set the maximum unique word count for an index for content searching

On the Portal Management > Cases and Servers > [Case] > Case Options page, shown in the following figure, you can now use the following option to set the maximum unique word count that can be retrieved from an index for content searching: Search max unique word count.

Case option: Search max unique word count.
  • The default value is 256,000.
  • The minimum value is 16.
  • The maximum value is 4,096,000.

SaaS / Hosted Monthly Release Notes - November 2020 (10.5.001 - 10.5.004)

Tools menu: Custom tools

Your administrator can now add custom tools, for example, a calculator, to the Tools menu using the UI extensions feature.

Use the following procedure to access custom tools.

  1. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  2. Select a UI extension tool.
  3. The tool appears in a standalone window. You can minimize, maximize, resize, and close the window. You can also reposition the window within your application browser window.

    Note: You must close the window before you can open a different UI extension tool.

    UI extension tool stand-alone window

Custom UI extensions for the Tools menu

The user interface extensions (UI extensions) feature allows application administrators and service providers to extend the functionality of the application by embedding custom third-party applications directly into the application interface. A third-party application that loads within the application is called a UI extension.

In addition to being able to add a UI extension to the Portal Home page, the Case Home page, or as a workspace pane on the Documents page, system administrators and portal administrators can now add a custom UI extension to the Tools menu on the Documents page using the Workspace tools UI extension.

Note: System administrators can add UI extensions in a portal for any organization or user, and portal administrators can install extensions for the organizations and users that they manage.

Sample UI extension applications:

  • An administrator might add a UI extension to the Tools menu to allow users easy access to external websites, for example, to an online calculator, as described in this document.
  • Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  • A Workspace tools UI extension could also be configured to submit a selection of documents in the List pane for a reporting, processing, or other task.
  • Another possible application could be a custom tool that combines multiple steps into one process. For example, you could build a custom tool that would allow you to take Predictive Coding score ranges and tag them with different review priority levels. Users could then search for documents by the review priority and tag those documents with the correct priority level.

For detailed information about UI extensions, see the following topics in the Nuix Discover online help.

  • UI Extension SDK: The UI Extension SDK provides an API that UI extensions can use to communicate with the application. The UI Extension SDK also includes steps to build and configure an extension, reference documentation, and an example extension. To get access to the UI Extension SDK, contact Discover.Sales@Nuix.com.
  • Administer UI extensions: This topic describes how to add a UI extension to the Case Home page, the Portal Home page, and as a workspace pane on the Documents page. The following procedure describes how to add a UI extension to the Tools menu manually.

The workflow consists of the following main steps described in more detail in the following sections:

  1. Manually add a UI extension to the Tools menu
  2. Enable a UI extension for an organization and cases
  3. Set group security for a UI extension
  4. Test the UI extension on the Tools menu

Manually add a UI extension to the Tools menu

Use the following procedure to manually add a UI extension to the Tools menu.

Note: To install a UI extension using a manifest file, see the above-mentioned topics in the online help.

  1. On the Portal Home page, under Portal Management, click UI Extensions.
  2. On the UI Extensions page, on the toolbar, click Add.
  3. The Add UI extension window appears, as shown in the following figure.

    Add UI extension window
  4. On the Settings page, in the Settings editor area, leave the Basic option selected.
  5. Note: If you are using a manifest file, select Advanced. The advanced procedure is not described in this document. For more information about how to add a UI extension using a manifest file, see Administer UI extensions in the Nuix Discover online help.

  6. Type a Name for the UI extension.
  7. In the Location list, select Workspace tools.
  8. Under Default window size, you can set the following:
    • Width: The minimum value for the width is 200 pixels and the maximum value is 1280 pixels.
    • Height: The minimum value for the height is 150 pixels and the maximum value is 768 pixels.
    • Require document selection: If the tool involves working with documents, select this option to require document selection before using the tool.
    • Display the OK and Cancel buttons: This check box is selected by default. Clear the check box if you do not need to include OK and Cancel buttons in the window, for example, when adding a calculator tool.
  9. Type an optional Description of the extension. The description appears on the UI Extensions page.
  10. Scroll down to display additional settings, as shown in the following figure.
  11. Add UI extension window showing description
  12. In the URL box, enter the URL of the web application that you are adding as an extension. The URL must include http or https.
  13. Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  14. In the Authentication secret box, click the Generate a random authentication secret button.
  15. Click Next.
  16. On the Review page, review the settings for the extension, and then click Save.

Enable a UI extension for an organization and cases

System administrators can enable UI extensions for the organizations in a portal.

Note: For portal administrators, when organization security is enabled, the list of available items depends on membership in a provider or client organization.

Use the following procedure to enable a UI extension for organizations.

  1. To access the UI extensions that are installed in the application, on the Portal Home page, under Portal Management, click UI Extensions.
  2. The UI Extensions page appears.

  3. On the UI Extensions page, shown in the following figure, click the name of an extension.
  4. UI Extensions page
  5. In the navigation pane, click Organizations.
  6. Depending on which organizations you want to enable the extension for, do the following:
    • To enable the extension for a single organization, hover over the row for the organization, and then click Allow.
    • To enable the extension for all organizations, click the Allow button in the heading row.
  7. After a UI extension is enabled for an organization, system administrators and portal administrators can enable the extension for the cases that are assigned to the organization. In the navigation pane, click Cases.
  8. Depending on which cases you want to enable the extension for, do the following:
    • To enable the extension for a single case, hover over the row for the case, and then click Allow.
    • To enable the extension for all cases, click the Allow button in the heading row.

Set group security for a UI extension

To allow groups in a case to access a UI extension on the Tools menu, administrators must grant access to the following security option on the Security > Features page in the case: UI Extension – [UI Extension Name]. Example: UI Extension - Calculator.

Test the UI extension on the Tools menu

Use the following procedure to test the UI extension.

Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  1. Log into a case.
  2. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  3. Select a UI extensions tool.
  4. Ensure that the tool appears as expected in the standalone window.
  5. UI extensions tool stand-alone window

New portal option to address potential performance issues when streaming media files

Web servers become highly consumed by the FFmpeg process running at 100% when streaming media files, which causes performance issues in the environment. To address this issue, a new setting named View pane media thread count is now available on the Portal Management > Settings > Portal Options page to allow system administrators to limit the number of allowed threads.

SaaS / Hosted Monthly Release Notes - October 2020 (10.4.009 - 10.5.000)

Tools > Imaging: Image viewer support for Adobe Photoshop file formats (.psd and .psb)

In the Imaging window, you can now submit .psd and .psb files, which are Adobe Photoshop file formats, for imaging to a TIFF, JPEG, or PDF format, as shown in the following figure.

Once the files are imaged, you can view the imaged files in the Image viewer in the View pane.

Imaging > Properties page

Case Setup > Issues: Issue administration enhancements

The Issue administration feature has been enhanced in this release and include the following updates:

Note: Administrators grant group leaders access to issue management on the Security > Administration page by setting the Case Setup - Issues - Properties and Case Setup - Issues - Security functions to Allow.

Add a root issue with child issues at the same time

Use the following procedure to add a root issue and child issues at the same time.

Note: Previously, this was a two-step process.

  1. On the Case Setup > Issues page, on the toolbar, click Add.
  2. In the Add issues dialog box, as shown in the following figure, provide a Name for the root issue.
  3. Add issues dialog box
  4. In the Child issue name(s) box, provide the names of the child issue.
  5. Note: Create a new line for each issue.

  6. Click Save.
  7. The root issue appears on the Issues page, as shown in the following figure. In the Name column, click the name of the root issue.
  8. Case Setup > Issues page
  9. The Child Issues page appears. To add additional issues to the child issues that you created, click the Add issue button, as shown in the following figure.
  10. Child Issues page

Clone a root issue and include child issues

You can now clone an existing root issue, including all of its child issues.

Note: When you clone an issue, the application clones only the issue structure, but not the document membership, that is, documents that were coded to the issues that you cloned.

Use the following procedure to clone an existing root issue.

  1. On the Case Setup > Issues page, hover over the row for an issue, and then click the Clone Issue button, as shown in the following figure.
  2. Case Setup > Issues page showing the Clone Issues button
  3. In the Clone Issue dialog box, as shown in the following figure, leave the name of the cloned issue or edit the name.
  4. Clone Issue dialog box
  5. Click OK.
  6. The cloned issue appears on the Issues page.

Import issues

You can now import issues using a .csv file.

Use the following procedure to import issues.

  1. On the Case Setup > Issues page, on the toolbar, click Import issues.
  2. In the Import issues dialog box, as shown in the following figure, do one of the following:
  3. Import issues dialog box
    • If you have a .csv file with issues, click Browse to upload your .csv file.
    • If you do not have a .csv file prepared, click the Download template link to download and populate a .csv file, and then click Browse to upload your .csv file.
    • Note: In the .csv file, the parent and child issues must be separated by a comma.

    The following figure provides an example of the format for the .csv file (created in a text editor).

    Example of format for .csv file in text editor

    The following figure provides an example of the format for the .csv file (opened in Microsoft Excel). The root issue name is in column A, the parent issue name is in column B, and the child issue names are in column C.

    Example of format for .csv file in Excel
  4. After you upload your .csv file, click OK.
  5. Note: If the application encountered errors when importing the .csv file, a notification appears, with a link to the errors. Fix the errors, and upload the .csv file again.

Export issues

You can now export issue to a .csv file format.

Use the following procedure to export issues.

  1. On the Case Setup > Issues page, select the check box next to an issue.
  2. On the toolbar, click Export issues.
  3. In the Export issues dialog box, click OK.
  4. The application downloads the .csv file to your computer.

    If you open the .csv file in Microsoft Excel, the information in the .csv file will look similar to what is shown in the following figure.

    Example of export issues .csv file in Excel

    If you open the .csv file in a text editor, the information in the .csv file will look similar to what is shown in the following figure.

    Example of export issues .csv file in text editor

Move child issues to a different root issue

You can now move child issues from one root issue to another root issue. You cannot currently move child issues within the same root issue.

Note: When you move issues, the application maintains the document membership, that is, documents that are coded to issues.

Use the following procedure to move child issues.

  1. On the Case Setup > Issues page, click the link for a root issue.
  2. On the Child Issues page, select the check boxes next to one or more issues, as shown in the following figure. To select all child issues, select the top check box.
  3. On the toolbar, click Move.
  4. Cild Issues Move feature
  5. In the Move Issues dialog box, as shown in the following figure, under Root issues, click the link for a root issue.
  6. Move Issues dialog box
  7. Click OK.
  8. The application moves the selected child issue or issues from the current root issue to the destination root issue.

    Note: If a child issue with the same name already exists in the destination root issue, the application will notify you and the issue is not moved. Change the name of the child issue and repeat the previous steps.

Case Setup > People Identity: Names Normalization enhancements

There are enhancements to the Names Normalization feature on the Case Setup > People Identity page in this release, including:

  • People Identity page: Information header over the columns and a link to non-normalized people in the banner
  • Assign identity dialog box: Delete empty identities after identity assignment option
  • Delete identity conformation message

These enhancements are described in the following sections.

People Identity: Information header over the document count columns and link to non-normalized names in the banner

The People Identity page has a new informational header, Occurrences in documents, located above the document count columns, as shown in the following figure. The counts in these columns reflect the number of occurrences that names appear in documents. See the infotip located next to the header for more information.

There is a link to View non-normalized names, located in the banner, as shown in the following figure. If you click the link, the rows are filtered to show all Non-normalized people.

People Identity page showing non-normalized people

Assign identity: Delete empty identities after assigning identities

When you assign people to a new identity, there is now an option to delete the source identity after you make the assignment, if there are no remaining people linked to that identity. If the source identity has fields coded, the coding will also be deleted. This option, shown in the following figure, is not selected by default. If you decide to delete the empty identities, select the check box, and then click OK.

Assign identity dialog box

Delete identity: Confirmation when deleting an identity

When you delete an identity that has no people assigned to it, the Delete identity dialog box appears, as shown in the following figure. If you are sure you want to delete the identity, click OK.

Delete identity dialog box

If you try to delete an identity that has user-created fields with coded values, the Delete identity dialog box shows a warning and lists the fields that are coded, as shown in the following figure.

To delete the identity, click OK.

Delete identity dialog box showing message of user created fields warning

Manage Documents > Imports: Delimiter column removed from field map for Ringtail MDB load files

Ringtail MDB load files do not support using a delimiter to separate multiple field values.

Starting with this release, when you add an import job on the Manage Documents > Imports page, if you select the Ringtail - MDB job type on the Import Details page in the Import window, the Delimiter column no longer appears on the Field Map page in the Import window.

The Delimiter column still appears for a Flat file job.

Note: If you clone a previous Ringtail - MDB import job and the Delimiter value was set, the value is not applied to the new import job.

Case and Servers > Case Options: New case options for the Predictive Coding feature

The following case options for Predictive Coding have been added to the Portal Management > Case and Servers > [Case] > Case Options page.

Tip: Hover over an infotip to view additional information about an option.

  • Predict Large Document Truncation Length: Amount of characters to keep at the beginning of a long text after truncation.
    • Default value: 100000000
  • Predict Max Document Size: Maximum size (in MB) of a document allowed before its contents are truncated.
    • Default value: 500
  • Predict Tokenization Batch Max Size: Maximum size in bytes of a batch allowed when there is more than one document.
    • Default value: 300

Case and Servers > Case Options: New case option when translating with a Microsoft custom translation model

Portal administrators can now configure a custom translation model to be used for Microsoft translations for a specific case and for a specific language pair.

Note: You must work with Nuix to configure this feature in your SaaS environment. To request access to this feature, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support.

A custom translation model allows you to create a customized dictionary of domain-specific source language and target language terms for a specific language pair.

Microsoft refers to this feature as the Microsoft Custom Translator. Custom models will need to be created in Microsoft’s Custom Translator portal in Azure.

To use a custom translation model for a case, enter the Category ID, which is the unique identifier for the custom model, in the Translate with Microsoft custom model box on the Portal Management > Case and Servers > [Case] > Case Options page, shown in the following figure.

Translate with Microsoft custom model field box

Organizations: Note about changing case metrics settings

When you change the case metrics settings for an organization in the Case metrics settings dialog box on the Portal Management > Organizations page, a banner that indicates that the daily metrics are being saved for organizations will now appear at the top of the page while the scheduled jobs are being saved for cases in the organizations, as shown in the following figure. The banner will be removed after all jobs are saved.

Case metrics settings dialog box banner message

Important: You can continue working while the jobs are being saved, but do not log out of Nuix Discover until you see that the banner is removed.

The time that it takes for the jobs to finish saving depends on the size of your environment.

SaaS / Hosted Monthly Release Notes - September 2020 (10.4.005 - 10.4.008)

Tools menu: Introducing the redesigned Tools menu

This release includes a redesigned Tools menu that provides an enhanced user experience when working with various tools. The menu was redesigned based on user feedback. The tools are organized into logical groupings. The names of the tools have not changed.

All tools: Allows you to access the entire list of tools, as shown in the following figure. The tools in each section mirror the logical groupings.

Tools menu

Frequently used tools

Frequently used tools such as Report and Batch Print are now at the top of the menu, as shown in the following figure.

Tools menu Frequently used options

Find tools quickly

The search box at the top of the menu, shown in the following figure, allows you to find tools without having to scroll through the list.

Find search box

Logical groupings

The tools are organized into the following logical groups that you can access by clicking the buttons in the navigation pane on the menu:

  • Output
  • General
  • Results
  • Processing

Output: The tools in this grouping include Report, Batch print, Export, and Archive files, as shown in the following figure.

Tools menu Output option

General: The tools in this grouping include History, Load search file, Workflow, Quick code, Add document, Coding history report, Document count, and Theme, as shown in the following figure.

Tools menu General option

Results: The tools in this grouping include Base docs\Renditions, Find masters family, Find family duplicates, Find individual duplicates, Remove family duplicates, and Remove individual duplicates, as shown in the following figure.

Tools menu Results option

Processing: The tools in this grouping include Imaging, Reverse previous imaging, OCR processing, Extract text, Transcribe audio, Indexing and enrichment, Thread analysis, Convert page annotations, and Translate, as shown in the following figure.

Tools menu Processing option

Tools menu: Access to Transcribe audio and Translate options

Users can now use the Transcribe audio and Translate options on the Tools menu even if they do not have access to private binders.

Introducing the Hierarchies feature

This release includes a new feature that allows you to view Hierarchies in the Browse pane, for example, to view the folder hierarchy of a file path for a custodian.

An example is shown in the following figure.

Note: Your administrator must configure and grant you access to hierarchies.

Browse pane Hierarchies

Tip: You can also search for a Hierarchy on the Search page.

Introducing the Names Normalization feature

The names normalization feature allows administrators to link the various people names (email addresses and names) for an individual person to an identity. This is especially helpful, for example, when creating a privilege log because the normalized identity name can be used instead of the non-normalized people names.

For example, if John Doe is associated with the following people names in Nuix Discover, an administrator can consolidate these email addresses and names into a single identity on the Case Setup > People Identity page.

  • john.j.doe@gmail.com
  • john.doe@gmail.com
  • jdoe@aol.com

After your administrator creates identities, you can work with the identities in the following ways on the Search page, in the List pane, and in the Communication Network pane.

Note: To use identities on the Search page and in the List pane, the user’s group must have permissions set to Allow for People\Organizations on the Security > Objects > Document Fields page. To access the Communication Network pane, the user’s group must have permissions set to strong for the Communication network feature on the Security > Features page.

  • Search for documents using identities on the Search page.
    • If an administrator has created identities, you can search for documents based on their connection to those identities using the following fields on the Search page:
      • Identity
      • Identity - BCC
      • Identity - CC
      • Identity - From
      • Identity - To
  • Add identity fields to the List pane column templates.
    • You can add the following identity columns to the List pane when documents are in the search results:
      • Identity
      • Identity - BCC
      • Identity - CC
      • Identity - From
      • Identity – To

      Tip: Adding these columns and using the Download feature in the List pane allows you to quickly generate a privilege log or other report showing the normalized names associated with documents.

  • Use identities to view normalized names in the Communication Network pane.
    • In the Communication Network pane, in addition to viewing communications for non-normalized person names, you can now also view information based on the normalized Identity names. To view the communications for an Identity, for example, for William S. Bradford, on the toolbar in the Communication Network pane, select Identity from the list, as shown in the following figure.
    • Communication Network pane Identity selection

Conditional Coding: Add a binder

In the Conditional Coding pane, group leaders with permissions to work with binders can now add a binder and apply security to that binder.

Use the following procedure to add a shared binder.

  1. In the Conditional Coding pane, in the list on the toolbar, select the Binders template.
  2. On the toolbar, click the Add binder button, as shown in the following figure.
  3. Conditional Coding pane Add binder button
  4. In the Add binders dialog box, as shown in the following figure, on the Properties page, provide a name and an optional description.
  5. Add binders dialog box
  6. Under Type, leave the Shared binder type option selected.
  7. Optionally, under Use as, set the binder to be used as a Security override or Mobile binder.
  8. Click Next.
  9. On the Security page, set the user group security for the shared binder.
  10. Click Save.
  11. The binder appears in the Conditional Coding pane.

Use the following procedure to add a private binder.

  1. In the Conditional Coding pane, in the list on the toolbar, select Binders.
  2. On the toolbar, click the Add binder button.
  3. In the Add binder dialog box, on the Properties page, provide a name and an optional description.
  4. Under Type, select Private.
  5. The Owner list appears, as shown in the following figure.

    Add binders dialog box Owner list
  6. In the Owner list, select an owner.
  7. Click Save.
  8. The binder appears as a private binder in the Conditional Coding pane.

Note: If you are a group leader with permissions and need to delete a binder, you can do that on the Case Setup > Binders page, but not in the Conditional Coding pane.

Analysis > Search Terms: Term query column added

The Analysis > Search Terms page now includes a new column named Term query, as shown in the following figure. This column contains the term query value or values for a Search Term Family.

You can use the information in the Term query column to effectively determine how to modify the search to increase or decrease the number of hits.

Analysis page Term query column

Case Setup: Introducing the Hierarchies feature

This release includes a new feature on the Case Setup > Hierarchies page that you can use to set up hierarchies, for example, to browse the folder hierarchy of a file path for a custodian.

Once you have set up hierarchies and granted access to user groups, users can view the hierarchies in the Browse pane.

Note: Administrators can grant group leaders access to this feature by setting the Case Setup - Hierarchies to Allow for Leaders on the Security > Administration page.

Use the following procedure to add a hierarchy.

  1. On the Case Setup > Hierarchies page, on the toolbar, click Add.
  2. In the Add hierarchy window, shown in the following figure, on the Properties page, do the following:
    • Provide a Name.
    • Select a Field, for example, All File Paths.
    • Select a Delimiter.
    • Click Next.
    Add hierarchy > Properties page
  3. On the Security page, shown in the following figure, set the security for groups, and then click Save.
  4. Add hierarchy > Security page

    The hierarchy appears on the Hierarchies page, as shown in the following figure.

After you create a hierarchy, you must run an indexing and enrichment job to populate and update the hierarchy.

Note: As documents are added to the case and submitted or resubmitted for indexing and enrichment, the hierarchies are updated as part of those jobs.

Use the following procedure to run an indexing and enrichment job for a hierarchy.

  1. On the Case Setup > Hierarchies page, select the check box next to a hierarchy, as shown in the following figure.
  2. On the toolbar, click Run.
  3. Case Setup > Hierarchies page

Use the following procedure to delete a hierarchy.

  1. On the Case Setup > Hierarchies page, select the check box next to a hierarchy, as shown in the previous figure.
  2. On the toolbar, click Delete.

Security > Administration: Enable the People Identity feature for group leaders

If you want group leaders to use the People Identity feature, you must enable it for them.

Use the following procedure to enable the People Identity feature for group leaders.

  1. Go to the Security > Administration page.
  2. In the Leaders column, click the Allow button next to Case Setup - People Identity, as shown in the following figure.
  3. Click Save.
  4. Security > Administration page

Case Setup: Introducing the Names Normalization feature

You can now use the Normalize feature on the Case Setup > People Identity page to normalize new non-normalized people names in a case. You can also use the Assign identity feature to change the connections between people and identities.

Using this feature, you can:

  • Run the Normalize job to create identities and link non-normalized people names
  • Assign (or reassign) people to an identity
  • Edit the identity name and description
  • Delete identities
  • View the identities and people for a specific document set
  • Download an identity report

You can find the Names Normalization feature on the Case Setup > People Identity page.

Note: Case administrators have access to this feature by default. If you want group leaders to have access to this feature, you must enable it first. See the Security > Administration: Enable the People Identity feature for group leaders section for more information.

Normalize people names

Use the following procedure to normalize names.

  1. Go to the Case Setup > People Identity page.
  2. If there are non-normalized names, a banner appears at the top of the page telling you that new people have been added and to click Normalize to normalize the people names to an identity. The following figure shows the data before it is normalized. Click the Normalize button.

    Case Setup > People Identity page
  3. In the Normalize dialog box, the following message appears, as shown in the following figure: The normalize job will link non-normalized people to an identity. People that are already linked to an identity will not be affected. To confirm, click OK.
  4. Normalize dialog box
  5. The application will run a Normalization RPF job to analyze the people name data and logically group the people under a unique identity. The banner at the top of the page lets you know that the normalization job is running, as shown in the following figure.
  6. Note: The job only operates on non-normalized people names. People that were linked to an identity before running the job are not affected.

    Case Setup page with Normalization job processing message
  7. Refresh the page to see the updated results. The banner at the top of the page lets you know that the normalization job is complete and that all people are linked to an identity, as shown in the following figure.
  8. Note: In the tree view in the Name column, the identities are the parent rows (shown in bold font) and the people are the child rows (in non-bold font).

    Case Setup page Name column

Working with the table on the People Identity page, you can:

  • Filter by the Name column to return specific people and their linked identities.
  • Note: When filtering by the Name column, the text you enter will match on people names (in child rows), and the filtered results will include the identities (parent rows) for those people that match your filter as well as all other people that are linked to those identities.

  • Sort the columns in ascending or descending order.
  • Note: No matter how you sort the columns, if there are non-normalized people names, they will always appear under the Non-normalized section at the bottom of the last page.

  • Click the plus and minus sign to collapse and expand the people beneath each identity.
  • Click a number link in the Total, From, To, CC, or BCC columns to view the documents that are associated with a person or identity.
  • Note: The counts in the Total column and identity rows reflect the number of occurrences that the identity or person name appears in documents. The counts do not represent the actual number of documents. For example, if Jane Smith sends an email and copies (CCs) herself, her name will appear in the same document two times (From and CC), so the Total column will show a count of 2 but the link will only return one document on the Documents page.

Assign an identity

The Assign identity feature allows you to change the identity that is assigned to people. You can reassign people to an existing identity or create a new one.

Use the following procedure to assign an identity.

  1. Select the check box next to a person, and then click Assign identity.
  2. Note: You can assign an identity to multiple people at one time by selecting more than one person and then clicking Assign identity.

    The Assign identity dialog appears, as shown in the following figure.

  3. Under Assign identify, select one of the following options:
    • Select an existing identity: Select an existing identity from the list.
    • Add new identity name: Select this option and enter a name in the box.
    Assign Identity dialog box
  4. Click OK.
  5. The person (or people) are then listed under the identity.

Edit identity name and description

You can edit the identity name or the identity description.

Note: The system Data Model now includes a new entity named Identity, shown in the following figure. The Identity entity was created to support the Names Normalization feature. The Identity entity has a one-to-many connection to the Person entity.

System > Entities page

For the Identity name and Identity description to be editable on the Case Setup > People Identity page, the user’s group must have Write access to these fields.

Use the following procedure to set make the identity name or identity description fields editable.

  1. Go to the Case Setup > Data Models > System > Entities > Identity > Fields page.
  2. On the Fields page, click the link for the Identity Description or Identity Name, as shown in the following figure.
  3. Identity > Fields page
  4. In the navigation pane, click Security.
  5. Set the security to Write for a user group, as shown in the following figure.
  6. Identity Name > Security page

Tip: On the Case Setup > Data Models > System > Entities > Identity > Fields page, click the Add button to add new fields to use for coding identities. Set the appropriate group permissions for your new fields on the field’s Security page. You can use your new fields in Column Templates or Conditional Templates for the Identity entity. You must enable the Conditional Template.

Use the following procedure to edit the identity name.

  1. Click on the Identity name or Identity description. An editable field appears, as shown in the following figure.
  2. Identity name or Identity description editable field
  3. Type the new identity name or description.
  4. To save your changes, click outside the field.

Delete identities

You can delete an identity that does not have any people assigned to it.

Use the following procedure to delete an identity.

  1. Hover over the row of the identity you want to delete and click the Delete identity button, as shown in the following figure.
  2. Delete identity button
  3. A message appears, confirming that the identity has been deleted.
  4. Note: You cannot delete an identity that has people assigned to it or delete the individual people.

View the identities and people for a document set

Select a Document set to view the identities and people that are associated with those documents.

Use the following procedure to view the identities and people for a specific document set.

  1. In the Document set list, select the type of document set you want to use, and then select the document set in the field that appears to the right.
  2. The page will refresh when the document set is changed, and the displayed identities will be filtered to only those that have people connected to documents in the selected set.

Note: All people are displayed for identities that have at least one person connected to documents in the selected set, even if some people in those identities are connected to 0 documents. The counts in the columns reflect the number of occurrences within the selected set. Your selected document set will be selected by default the next time you return to the People Identity page.

The Normalize job always operates on all documents in the case, regardless of which document set is selected on the page.

Download an identity report

You can download an identity report to a .csv file.

Use the following procedure to download an identity report.

  1. Click the Download report button. Nuix Discover saves the identity information to a .csv file under your Downloads folder.
  2. Note: The Download report feature will respect the document set that is selected. The report file name has a time stamp with the local time so that each time you download a new report with a new time stamp the report will be saved and will not overwrite a previous report.

  3. To view the report, open the .csv file in Microsoft Excel.

Manage Document > Ingestions: NIST list updated - June 2020

The Ingestions feature now uses an updated version of this list, released in June 2020. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl/nsrl-download/current-rds

Security > Features: Allow group leaders to add binders in the Conditional Coding pane

To allow group leaders to add binders in the Conditional Coding pane, you must set the Case Setup - Binders and Case Setup - Properties features to Allow on the Security > Features page.

Security > Features: Set security for the Documents Added section on the Case Home page

You can set security for the Documents Added section on the Case Home page. You can choose to display or hide the Documents Added section by enabling or disabling the Case Home - Documents added feature for groups on the Security > Features page, as shown in the following figure.

Note: This feature is set to Deny by default for all newly added groups. When a group is cloned, access to the Documents Added feature is carried over from the group it was cloned from.

Security > Features page

When this feature is set to Deny for a group, the users in that group do not see the Documents Added section on the Case Home page, and the Results History section appears in that location, as shown in the following figure.

Case Site Map page Results History section

When this feature is set to Allow for a group, the users in that group see the Documents Added section on the Case Home page, as shown in the following figure.

Case Site Map page Documents Added section

Cases and Servers: Database and Analysis servers prepopulated for Organizations when adding or cloning a case

When you add a new case, the Database and Analysis servers for that Organization are prepopulated on the Servers page in the Add case window, as shown in the following figure.

Add case > Servers page

When you clone a case, the Database and Analysis servers for that Organization are prepopulated on the Servers page in the Clone case window, as shown in the following figure.

Clone case window showing pre-populated fields

Cases and Servers: Clone a case from one Organization to another Organization

When you clone a case, you can now select a different Organization than the Organization that is currently associated with the case that you are cloning, as shown in the following figure.

Clone case > Case Details page

Cases and Servers > Clone Case: Audit for coding history is enabled by default for new cases

If the coding history audit feature is enabled for a portal, when you clone a case and leave the Clear data option unselected, as shown in the following figure, auditing is now automatically enabled.

The benefit of this is that you do not have to request for the coding history audit feature to be enabled by a system administrator after you create a case.

Clone case > Case Details page showing Clear data field

After you clone a case, a new elastic index is created for the new case, and audit is enabled for coding history.

User Administration > Account Settings: Increase the password history maximum setting to 24

On the Portal Home > User Administration > Account Settings page, in the Password History box, administrators can enter the number of times users must create a unique password before it can be reused. In previous versions, administrators could select 1-20 unique password entries. Now, administrators can select 1-24.

Cases and Servers: Enable Linux\Docker Ingestions option relocated to the portal level

The Enable Linux\Docker Ingestions option has been removed from Case Options and relocated to Portal Options. On the Portal Home > Settings > Portal Options page, if you select the Enable Linux\Docker Ingestions check box, all cases in the portal will use this setting.

Note: Cases that were configured in previous versions will respect the prior setting. To change the case setting for an existing case, you must use a SQL query.

Connect API Explorer: OneGraph GraphiQL Explorer API query builder

The Connect API Explorer now contains the OneGraph GraphiQL Explorer plug-in. This plug-in is a query builder that assists users, both new and advanced, in quickly and easily generating queries and mutations with a graphical representation of the data fields and objects and helps avoid the frustration of incorrect syntax.

The Connect API Explorer window now contains four panes, as shown in the following figure, and described in the following table.

Connect API Explorer window now showing four panes
  • 1  Explorer pane: New query builder for automated assistance in constructing queries and mutations.
  • Note: To close the Explorer pane, click the X button. To reopen this pane, click the Show explorer button in the Editor pane.

  • 2  Editor pane: Area for constructing, formatting, and running queries and mutations.
  • 3  Results pane: Contains query and mutation results.
  • 4  Documentation Explorer pane: Documentation details for all query and mutation endpoints and their associated arguments and fields.

Each time you enter the Connect API Explorer, the Explorer pane will begin with a default query under the Me argument related to data associated with you, the user.

Use the following procedure to manipulate any query or mutation.

Note: This example creates a basic query filtering on all active cases and sorts them by case name in ascending order.

  1. To create a new query or mutation, in the Add New field, at the bottom of the Explorer pane, select Query or Mutation from the list, and then click the + sign, as shown in the following figure.
  2. Explorer pane Add New button

    The new blank query or mutation will appear in the Explorer and Editor panes with a default name.

  3. To copy an existing query or mutation, to the right of the Name field, hover over and click the Copy button, as shown in the following figure.
  4. Explorer pane Copy button

    A duplicate copy will appear under the existing queries and mutations in the Explorer and Editor panes.

    Note: You can manipulate multiple queries and mutations simultaneously.

  5. Enter a unique Name.
  6. The change appears in the Explorer and Editor panes.

    Note: It is best to give your query or mutation a unique name to help identify their function.

  7. In the Explorer pane, expand the cases list by clicking the expand arrow, as shown in the following figure.
  8. Explorer pane showing expanded field option

    The cases argument is added to the Editor pane with the proper syntax.

    Note: Filter fields appear in purple and are used for filtering the returned data by a specified value you enter. Fields that appear in blue are used for returning any data value within that field.

    Important: If you close an expanded list in the Explorer pane, and already have several fields and filters selected, closing the list will delete the selections from the query or mutation. However, those selections are cached, and by expanding the list again, the selected fields and filter data will reappear.

  9. Select the check boxes for the id and name fields shown in blue text, shown in the following figure in step 7.
  10. The fields appear in the Editor pane in the proper location and surrounded by the correct syntax.

    Note: If you manually enter these fields in the Editor pane, the check boxes are automatically selected in the Explorer pane.

  11. Select the check box for the active field shown in purple text, shown in the following figure in step 7, and then select true.
  12. Note: When filtering with multiple values, such as multiple IDs, the builder does not support arrays. You must enter the multiple filtering values manually in the Editor pane.

  13. Expand the sort field shown in purple text, and then do the following.
    • Select the check box for the dir field, and then select Asc.
    • Select the check box for the field* field, and then select name.
    • Important: The asterisk (*) following a field name indicates a required field. If selected, this field must contain a data value to filter on.

    The query now contains all of the selected fields and filter options, as shown in the following figure.

    Explorer and Editor panes showing example query
  14. To delete the query or mutation and start over, hover over the name in the Explorer pane, and then click the X button, as shown in the following figure.
  15. Explorer panes Delete button

    The query or mutation is deleted from both the Explorer and Editor panes.

  16. To run a query or mutation, in the Editor pane, click the Execute query button.
  17. Note: If you have multiple queries and mutations, a list will appear where you can select one for execution. However, all queries and mutations must be valid to run that selection successfully.

    The results will appear in the Results pane.

SaaS / Hosted Monthly Release Notes - August 2020 (10.4.001 - 10.4.004)

List pane: Download a report to an .xlsx format and add a report title

In the List pane, you can now download a report to an .xslx format and give the report a title, as shown in the following figure. Previously, you could download the report only to a .csv format.

Download dialog box

Enhancements to Workspace panes

This release includes the following enhancements to all workspace panes, as shown in the following figure:

Change-Maximize-Close pane enhancements

Change a pane

To change a pane, on the pane menu, select a different pane from the list, as shown in the following figure.

Note: Changing a pane changes your current workspace configuration.

Change pane enhancement

If you select a pane that is already included in your current workspace configuration, the current pane is exchanged with the pane you selected.

For example, if your workspace configuration includes a Browse pane, a List pane, and a Conditional Coding pane, if you change the List pane to a Conditional Coding pane, the List pane appears where the Conditional Coding pane used to be, as shown in the following figures.

Before

Change pane before example

After

Change pane after example

Maximize a pane

All workspace panes now include a new option to maximize the pane, as shown in the following figure.

Maximize pane selection

When you select the Maximize option, the application maximizes the pane and hides all of the other panes in the workspace configuration.

To restore the hidden panes, click the Restore all hidden panes button on the toolbar of the pane, as shown in the following figure.

Maximize pane button

Close a pane

All workspace panes now include a new option to close the pane, as shown in the following figure.

Note: Closing a pane changes your current workspace configuration.

Close pane selection

When you select the Close option, the application removes the pane from the current workspace as well as from the pre-set workspace configurations.

To add the pane that you closed back to a workspace, on the workspaces menu, shown in the following figure, edit the workspace.

Return a closed pane example

Tools > Imaging: Auto-detect color and render to JPG option added to Imaging > Properties window

When submitting documents for imaging, you can now select an option to automatically detect color and render to JPG. The Auto-detect color and render to JPG check box is located in the Imaging window on the Properties page, as shown in the following figure.

Note: This option is available only if the TIFF option is selected from the Image type list.

The default value for the option is based on the Imaging settings found in Manage Documents > Imaging - Automated > Settings.

Imaging Properties page

Case Setup > Binders: New workflow to add a binder

On the Case Setup > Binders page, the workflow to add a binder has been streamlined. When you add a binder, you can now set the properties and the security in a wizard-like fashion. Previously, you had to add a new binder, and then access the new binder to set the security.

Note: If you need to edit an existing binder or a newly created binder, you must do that on the Case Setup > Binders > Properties and Security pages for a binder.

Use the following procedure to add a new binder and set the security for the binder.

  1. On the Case Setup > Binders page, on the toolbar, click Add.
  2. In the Add binders window, on the Properties page, set the properties for the binder, and then click Next, as shown in the following figure.
  3. Add binders Properties page
  4. On the Security page, set the security for the binder, and then click Save, as shown in the following figure.
  5. Add binders Security page

    The new binder appears on the Case Setup > Binders page.

Manage Documents > Imaging - Automated: Update default brightness setting to 15

In previous versions, when a file contained text with a background that was similar in color, converting the file to a black and white image could result in text and background that were the same color. We have updated the brightness setting to increase the likelihood that the text and background will be distinguishable in the resulting images.

In the Manage Documents > Imaging - Automated > Settings window, on the PDF page, the default brightness setting for new cases is now 15, as shown in the following figure. For existing cases, if the setting was previously 85, the value has been changed to 15. If the setting was previously anything other than 85, the value has not been changed.

Settings PDF page

Manage Documents > Ingestions: Upgrade to the Nuix Engine 8.4.7

Ingestions now uses the Nuix Workstation 8.4.7 processing engine.

SaaS / Hosted Monthly Release Notes - July 2020 (10.3.009 - 10.4.000)

Coding History Search: New operator to search for previously coded values

A new operator named previous value ever was is now available for advanced searches on the Search page, as shown in the following figure.

Search page showing new operator

Note: The previous value ever was operator is available to users who are in a group with permissions to access the Coding History pane.

The following field types support coding history searches using the previous value ever was operator:

Note: Memo field types are not supported.

  • Pick list
  • Date
  • Number
  • Yes\no
  • Text
  • Binder - Shared
  • Issue
  • Production
  • Population
  • Sample
  • Highlight
  • Redaction
  • People - correspondence type
  • Organizations - correspondence type

When using this operator, you can search for previously coded values, which are the values captured by the Coding History feature and found in the Previous value column in the Coding History pane, as shown in the following figure.

Coding History pane showing Previous value column

Use the following procedure to search for previously coded values.

  1. Navigate to the Search page.
  2. In the Select a field box, select the field for your search criteria.
  3. In the Select an operator box, select previous value ever was.
  4. In the Select a value box, select or enter the value.
  5. Note: Not all values for your selected field may be available in the Select a value list. Values are not available for previous value ever was searches until they have been stored in coding history (for at least one audit record).

    When searching for a text field value using the previous value ever was operator, the text field value must be an exact match.

  6. Optionally, to include Coded by or coded on date parameters in your search criteria, click the Add additional criteria button.
  7. Note: Coded by and coded on date parameters will be evaluated against the user and date corresponding to the original coding action for the value.

  8. To run the search, click the Search button.

Coding history report on the Tools menu

The Tools menu on the Documents page now includes a Coding history report option that allows you to download a .csv report with the history for a field for all documents selected in the List pane.

Note: To see this option, your administrator must grant you access to the Coding - Coding History feature on the Security>Features page.

Use the following procedure to generate a coding history report.

  1. In the List pane, select one or more documents.
  2. On the Tools menu, select the Coding history report option.
  3. In the Download coding history report dialog box, shown in the following figure, from the Field list, select a field, and then click OK.
  4. Note: The available fields depend on the permissions granted by your administrator.

    Download coding history report dialog box

    A processing window appears, as shown in the following figure.

    Note: Do not close this window or exit the case until the report downloads.

    Downloading coding history report completion message
  5. After the .csv report downloads, open or save the file.

Updates to the Renumbering feature

The following updates have been made to the Renumbering feature, which is available on the Tools menu:

  • When endorsing headers, more space is now provided between the endorsement and the edge of the page. This reduces the potential for the endorsement to be cut off when printing documents to paper.
  • The following updates have been made to the Document ID page in the Renumbering window, as shown in the following figure:
    • Suffix delimiter: This character is used before the page number during endorsement. The default character is a hyphen.
    • Override validation: If you select this option, the application assigns Document ID values starting with the selected value, even if there is an existing Document ID with a higher number.
    • Note: This option is not selected by default. Selecting this option could result in a job failure if a Document ID already exists. Selecting this option could also cause the application to assign page numbers that already exist on other documents. If you select this option, the application does not validate whether there is a Document ID in the expected range for the settings.

      Renumbering - Document ID page
  • On the Endorsement page in the Renumbering window, if you select the Document ID plus page number endorsement option, as shown in the following figure, the Start numbering on page 2 check box appears. If you select this check box, the first page of a document includes only the Document ID, but not the page number. The page numbering starts on the second page of the document.
  • Renumbering - Endorsement page

Manage Documents>Exports: Ability to apply headers

Administrators now have the option to apply headers to base images in Custom and MDB Classic export types. In previous releases, only footer settings were available.

You can access header options on the Headers\footers page in the Export window, as shown in the following figure. The options available for footer values are also available for header values. You can select any combination of headers and footers.

Headers\footers page in the Export window

Note: The width, height, and font size are the same for both headers and footers. As with footers, the Header height setting allows you to add space to the top of the image when endorsing headers such that the header text does not overlap with image text.

Manage Documents>Productions: New productions numbering options

The Attributes page of the Productions feature now includes new options for setting the numbering convention for production documents and files, as shown in the following figure.

Attributes page of the Productions feature

The following options are available under Numbering on the Attributes page of a production:

  • Standard: This option offers a new, simplified way to set the Production Document Label and Production Page Label. You can enter information directly into the Prefix, Start number, and Padding boxes. Under Number by, select either Page or Document. If you choose to number by document, you can enter a value for page numbering padding and choose a delimiter to use between the document and page number, if required.
  • The following list provides examples of page and document numbering.

    • Doc 1 - page 1
      Number by page: ABC-00000001
      Number by document: ABC-00000001-00001
    • Doc 1 - page 2
      Number by page: ABC-00000002
      Number by document: ABC-00000001-00002
    • Doc 2 - page 1
      Number by page: ABC-00000003
      Number by document: ABC-00000002-00001
    • Doc 2 - page 2
      Number by page: ABC-00000004
      Number by document: ABC-00000002-00002
    • Doc 2 - page 3
      Number by page: ABC-00000005
      Number by document: ABC-00000002-00003
    • Doc 3 - page 1
      Number by page: ABC-00000006
      Number by document: ABC-00000003-00001
  • Custom: This option is the same as in previous versions. It allows administrators to enhance customization by using the variable builder to define values.
  • For productions that were locked or were created but not locked prior to this update, the selections you made for Production Document Label and Production Page Label appear in the Custom numbering section of the Attributes page.

Note: The Production Document Label determines the Rendition Document ID as well as the names of any native and content files. The Production Page Label determines the name of image files. The Production Page Label is also referred to as the Bates number. To set the Bates number as a footer, you must select the Production Page Label option, regardless of how you set up numbering on the Attributes page. Load file template field references to begin and end Bates and any other numbering values will not change.

Manage Documents>Updates to the Renumbering feature

The following updates have been made to the Renumbering feature:

  • The Suffix delimiter that you set on the Document ID page in the Renumbering window appears on the Manage Documents>Renumbering>Properties page in the Settings>Document ID section.
  • On the Endorsement page in the Renumbering window, if you selected the Document ID plus page number endorsement option and selected the Start numbering on page 2 check box, the setting appears on the Manage Documents>Renumbering>Properties page, in the Settings>Endorsements section.

Introducing the case archiving feature

Case archiving allows you to archive an entire case. Case archiving is available to system and portal administrators. You may want to archive a case if you no longer need the database to be readily available in Nuix Discover, but you want the option of restoring it in the future should the need arise.

When you archive a case, it is stored in a folder on the archive repository that is assigned to the case. The folder will include backup files of all three of the case databases, zip archives containing all files from the repositories assigned to the case, and a backup of the coding history index (if the case has audit enabled for coding history). After you archive a case, you can download the case files, recommission the case, or permanently delete the case.

Note: Portal and system administrators can do everything described in this section.

Archive a case

You can archive an entire case using the Decommission option, which is available on the More menu on the Cases page.

Use the following procedure to decommission and archive a case.

  1. On the Cases page, select the case you wish to archive.
  2. On the More menu, select Decommission, as shown in the following figure.
  3. Decommission option on the More menu

    The Decommission case window appears, as shown in the following figure.

  4. The Decommission case dialog box has been changed to a wizard-style window with two pages: Options and Summary. The Options page now includes a choice for Archive (selected by default) or Permanently delete, which was previously the only option available when decommissioning a case. Select Archive, and then click Next.
  5. Options page on the Decommission case dialog box
  6. The Summary page, shown in the following figure, displays the destination folder where the archived case will be stored, the total size of the case to be archived (as captured by the latest case metrics job), and a listing of the database and analysis servers, Elasticsearch index name, and the repositories that are assigned to the case. To archive the case, click OK.
  7. Summary page on the Decommission case dialog box

    Note: If files were archived while the case was live, the folders containing those file archives will remain adjacent to the new folder that is created for the case archive. The previously archived files will not be “re-archived” to the case archive destination folder.

    If the case does not have an archive repository currently assigned, the Destination field shown in the following figure will display a list of the available archive repositories. Select an archive repository to assign as the destination for the archived case.

    Summary page on the Decommission case dialog box showing Destination options

    Note: When organizations security is enabled for the portal, the archive repository that is assigned to the case must also be assigned to the case’s organization to allow for the case to be archived.

  8. After you click OK, a Case Decommission job will run in RPF and will archive the case. The worker processing window will open and display the progress of the job stages, as shown in the following figure.
  9. Note: You do not need to keep the worker processing window open while the job is running. You can also monitor the job progress in the Progress column for the case row on the Cases and Servers>Cases page, or by viewing the job on the Processing>Jobs page.

    Case Decommission processing progress dialog box

    Note: When the job begins, the case will be taken offline and users will no longer be able to access the case. Any scheduled RPF jobs for the case will be removed.

  10. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers>Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit the case for decommission, select the case, and on the More menu, click Resubmit, as shown in the following figure.
  11. Cases and Servers - Cases page - Resubmit option

After a case is successfully archived, it will appear on the Cases page with an Archived status, as shown in the following figure.

Cases and Servers - Cases page showing Archived status

About archived case files

When you archive a case, Nuix Discover saves a variety of case files. An example of the types of files that are stored for an archived case is shown in the following figure.

The types of files for your archived case include:

  • .bak files for all three of the case SQL databases.
  • Zip archives containing all files from the repositories assigned to the case.
  • Note: Zip file names include the top-level folder name from the repository. An empty .zip file will be created to represent a folder that does not contain any files in the case subfolder. Files are batched into .zip archives that are approximately 2 GB in size. Depending on the total size of files contained in a repository folder, this could result in multiple .zip archives for a top-level folder. In that case, each .zip archive will be named uniquely with a numeric suffix.

  • A .zip archive containing the coding history Elasticsearch index.
  • .csv files that contain a file inventory of each top-level folder from each repository. These inventory files are used for the validation stages of the decommission and recommission jobs.
  • File Manager window showing .csv files within the archive

When you archive a case, you also have three new options on the More menu.

The following options are available for an archived case on the More menu on the Cases page, as shown in the following figure:

  • Download files: This will download a copy of all files for the archived case.
  • Recommission case: This will restore the case and all files back to their original locations.
  • Delete: This will permanently delete the archived case with no backup.
  • Cases page More menu options

Download case files from an archived case

You can download case files from an archived case and save a copy of those files locally using the Download files option on the More menu on the Cases page.

Use the following procedure to download case files from an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Download files, as shown in the following figure.
  3. Cases page More menu option selection of Download files

    The Download files dialog box appears, as shown in the following figure.

  4. In the Download files dialog box, you will see the total size of the files for the archived case that will be downloaded. Click OK.
  5. Download files dialog box

    The worker processing window appears, as shown in the following figure.

  6. The worker processing window displays the status for the files being downloaded. Keep this window open, as all files will be downloaded through this window.
  7. Note: Depending on your browser settings, you may be prompted to allow for multiple files to be downloaded.

    Download files progress dialog box

Delete an archived case

After you decommission and archive a case, you can delete it permanently using the Delete option on the More menu on the Cases page.

Use the following procedure to delete an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Delete, as shown in the following figure.
  3. Cases page More menu option selection of Delete

    The Delete archived case dialog box appears, as shown in the following figure.

  4. In the Delete archived case dialog box, select the Delete this case and all associated files check box to enable the OK button, and then click OK to permanently delete the archived case with no backup.
  5. Delete archive case dialog box
  6. The Decommissioned Case Deletion job will run in RPF and will permanently delete the archived case. The worker processing window opens and displays the progress of the job stages, as shown in the following figure.
  7. Note: You do not have to keep the worker processing window open while the job is running. You can also monitor the job progress in the Progress column for the case row on the Cases and Servers>Cases page, or by viewing the job on the Processing>Jobs page.

    Decommissions Case Deletion job progress dialog box
  8. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers>Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit a case to be deleted, select the case, and from the More menu, click Resubmit.

After an archived case is successfully deleted, it will be logged to the Cases and Servers>Deleted Cases page.

Recommission a case

You can recommission an archived case by using the Recommission case option on the More menu on the Cases page.

Use the following procedure to recommission an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Recommission case, as shown in the following figure.
  3. Cases page More menu option selection of Recommission case

    The Recommission case dialog box appears, as shown in the following figure.

  4. The Recommission case dialog box displays the same repositories that were assigned to the case at the time it was archived. To recommission the case, click OK.
  5. Recommission case dialog box

    Note: The original servers and repositories that were assigned to the case at the time it was archived are selected by default. The selected Image, Index file, and File transfer repositories will be the destinations for restoring the files. The selected Archive repository is where the recommission job will look for the archived case files to be restored.

    Note: If an original repository is no longer available in the portal, a warning icon will appear next to that item, as shown in the following figure, and the field will display a list of the available repositories. Select a new repository to assign as the repository type to restore the files to.

    Recommission case dialog box Image field
  6. A Case Recommission job will run in RPF and will restore the case. The worker processing window will open and display the progress of the job stages, as shown in the following figure. You do not have to keep the worker processing window open while the job is running.
  7. Note: You can also monitor the job progress in the Progress column for the case row on the Cases and Servers>Cases page, or by viewing the job on the Processing>Jobs page.

    Recommission case job progress dialog box
  8. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers>Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit a case to be recommissioned, select the case, and on the More menu, click Resubmit.

After a case is successfully recommissioned, it will appear on the Cases page with a Valid status, as shown in the following figure.

Cases and Servers - Cases page

Note: The recommission job will attempt to reassign the same users to the case who were assigned at the time the case was archived, assuming those users are still available in the portal.

Report on decommissioned cases

You can see archived cases on the Reports>Hosted Details page by using the Status column filter to show or hide cases with an Archived status, as shown in the following figure.

Reports - Hosted Details page

Note: Case metrics are refreshed at the end of the case decommission job so that after a case is successfully archived the total size of the archived case will be represented in the Archive data (GB) column on the Hosted Details page.

Portal Management>Settings: Portal Options: New setting to limit the size of an audio file in the View pane

A new option named View pane maximum audio file size is now available on the Portal Management>Settings>Portal Options page, as shown in the following figure. Use this option to set the maximum file size in bytes when streaming audio files in the View pane. This new option, which can be set to a maximum value of 31457280 bytes, addresses IIS performance issues for .wav files.

Portal Management - Settings - Portal Options page

Connect API Explorer: Identify archived cases using the decommissionStatus field

In the Connect API Explorer, the caseDecommissionStatusEnumType filter now includes the status Archived as a value by using the decommissionStatus field.

Sample query:

query {
  cases (decommissionStatus: Archived) {
    name
    caseDecommissionedBy
    caseDecommissionedDate
    decommissionStatus
  }
}

Sample query results:

{
  “data”: {
    “cases”: [
      {
        “name”: “Acme”,
        “caseDecommissionedBy”: “Doe, John”,
        “caseDecommissionedDate”: “2020-06-15T18:35:55.743Z”,
        “decommissionStatus”: “Archived”
      }
    ]
  }
}

Connect API Explorer: Search coding history values using the PreviousValueEverWas operator

The operator PreviousValueEverWas is now available in the API for searching on values in coding history.

Sample mutation:

mutation {
  searchRun (caseId: 2, input: {
    include: MatchingItems,
    renditions: false,
    singleQuery: {
      field: “Document ID”,
      operator: PreviousValueEverWas,
      value: “A”
    }
  }) {
    id
    label
    count
    dateRun
    entityId
    items {
      id
      itemId
    }
  }
}

Sample mutation results:

{
  “data”: {
    “searchRun”: {
      “id”: 742,
      “label”: “--/ “Document ID/” previous value ever was /“A/””,
      “count”: 0,
      “dateRun”: “2020-06-19T14:18:53.027Z”,
      “entityId”: 1,
      “items”: []
    }
  }
}

Login Service version 2.3.15 now includes an installer

This installer is intended for deployment on Windows servers. New versions of Nuix Discover will continue to be compatible with Login Service version 2.2.21, so you can upgrade at your convenience. The Login Service can be installed using the Nuix Discover Deployer version 2.5.94 and higher.

SaaS / Hosted Monthly Release Notes - June 2020 (10.3.005 - 10.3.008)

Analysis > Predictive Coding Templates: Select how date data is treated

We have added an option to Predictive Coding Templates that allows administrators to select how date type field data should be treated in the model.

To access the option, go to Analysis > Predictive Coding Templates and select a template. On the Fields page, click in the Date Value column, and then select a value for how date information should be treated in the template.

Predictive Coding Template - Fields page

The options are as follows:

  • Text: Date information is treated as a text string.
  • Day, month, and year: Date information is modeled without time. This option is the default.
  • Month: Date information is treated as a number with January = 1, February = 2, and so on.
  • Day: Date information is treated as a number.
  • Day of the week: Date information is treated as a number with Sunday = 1, Monday = 2, and so on.
  • Year: Date information is treated as a number.

Note: The application treats any date fields selected in templates created before this change as Text. If the template is used in any models, the date value cannot be changed. The choice of which Date Value option to use depends on the case data and what aspect of the date information has an impact on the model. For example, documents with dates clustered around the middle of January 2005 may be meaningful. Select the Day, month, and year value to model date information in that way. In a different example, which day of the week a date falls on (Monday, Tuesday, and so on) has some relevance. Use the Day of the week value to model date information in that way.

Manage Documents > Ingestions: Upgrade to the Nuix Engine 8.4.5

Ingestions now uses the Nuix Workstation 8.4.5 processing engine. The engine upgrade resolves the out-of-memory failures when processing some forensic images.

Manage Documents > Productions: Apply headers

Administrators now have the option to apply headers to production images. In previous releases, only footer settings were available.

You can access header options on the Endorsements page for a production. Click in any of the boxes for Left, Middle, or Right header to launch the variable builder.

Endorsements page

You can select any combination of headers and footers. Note that the width, height, and font size are the same for both headers and footers. As with footers, the Header height setting allows you to add space to the top of the image when endorsing headers such that the header text does not overlap with image text.

Manage Documents > Renumbering: Add option to number by document

When renumbering documents, administrators can now choose to increment page numbers by document or page. In the previous release, you could increment numbering by page only.

  • On the Document ID page, in the Format list, administrators can now select either Prefix, Box, Folder, Page - increment by page or Prefix, Box, Folder, Page - increment by document.
  • On the Endorsement page, for each header and footer option, administrators can now select Document ID plus page number.

Portal Management > Reports: New Max data (GB) column in Hosted Details report

The Hosted Details report includes a new column named Max data (GB), shown in the following figure.

This column displays the maximum active hosted data size for a case within a specified date range and captures the following data: sum value of base documents, production renditions, databases, the Elasticsearch index, the content index, and Predict data. This column also includes a calendar icon. Hover over the calendar icon to display the date of the maximum value.

Reports - Hosted Details page

If you download a report, it will now include the following two columns and values:

  • Max data (GB): The maximum active hosted data size for a case.
  • Max data (date): The date the maximum active hosted data size was captured.

Portal Management > Cases and Servers: Delete case record from the portal database for deleted cases

After a case is deleted, as a system administrator, you can delete the case record for the deleted case from the portal database. You can also then create a new case using the same case name.

Use the following procedure to delete the case record for a deleted case.

  1. On the Portal Management > Cases and Servers > Deleted Cases page, select the check box next to a case.
  2. On the toolbar, click Delete record.
  3. In the Delete record dialog box, shown in the following figure, select the Delete case record and all metrics check box.
  4. Note: Once you select this check box and click OK in the following step, the case record and all metrics are permanently deleted from the portal database.

  5. Click OK.
  6. Delete record dialog box

After you delete the record, the deleted case no longer appears on the Deleted Cases page or the Portal Management > Reports page.

Portal Management > Settings > Log Options: Multiple S3 bucket entries supported for the Telemetry archive configuration

The Telemetry archive configuration field on the Portal Management > Settings > Log Options page now has a new “S3Buckets” setting that supports multiple entries for the key, secret, region, and bucket values.

When telemetry is configured to store the logs in the database, and the configuration string includes multiple S3 buckets, the telemetry data is pushed to all S3 buckets.

The following example shows how to format the JSON configuration string with multiple S3 buckets.

{
“Checkpoint”: 0,
“CheckpointRPF”: 0,
“S3Buckets”: [
{ “Key”: “******”, “Secret”: “******”, “Region”: “us-east-1”, “Bucket”: “s3-bucket-1” }
,
{ “Key”: “******”, “Secret”: “******”, “Region”: “us-east-1”, “Bucket”: “s3-bucket-2” }
],
“CleanupMaxDays”: 3,
“ScheduleId”: 22,
“IntervalInMinutes”: 30,
“NRecentRecordsToReturn”: 10000
}

Connect API Explorer: maxActiveHostedSize and dateOfMaxActiveHostedSize case statistics

There are two new case statistics available through the Connect API Explorer that will return the maximum value of the aggregateActiveHostedSize and the date of that value within a specified date range.

Note: The aggregateActiveHostedSize statistic is the sum of sizeOfBaseDocumentsHostedDetails, sizeOfRenditionsHostedDetails, aggregateDatabases, sizeOfElasticSearchIndex, dtIndexSize, and sizeOfFolderData_Predict.

  • maxActiveHostedSize: Returns the maximum value of aggregateActiveHostedSize within a specified date range. This value calculates from the first minute of the startDate (12:00:00am) to the last minute of the endDate (11:59:59pm) in Coordinated Universal Time (UTC).
    • When only providing the endDate for the date range, the returned value is the highest value of the aggregateActiveHostedSize calculating from the beginning of the case to the last minute of the specified endDate.
    • When there is no startDate or endDate provided, the returned value is the highest of the aggregateActiveHostedSize over the entire life of the case, from the beginning of the case through the current day.
  • dateOfMaxActiveHostedSize: Returns the date of the maxActiveHostedSize within a specified date range.
    • When only providing the endDate for the date range, the returned value is the date of the maxActiveHostedSize calculating from the beginning of the case to the last minute of the specified endDate.
    • When there is no startDate or endDate provided, the returned value is the date of the maxActiveHostedSize over the entire life of the case, from the beginning of the case through the current day.

Sample query:

query {
  cases {
    name
    statistics(startDate: “2020-04-01”, endDate: “2020-04-30”) {
      maxActiveHostedSize
      dateOfMaxActiveHostedSize
    }
  }
}