Nuix Discover SaaS/Hosted Release Notes

Support for SQL Server 2022

Nuix Discover now supports SQL Server 2022.

Support for Windows Server 2022

Nuix Discover now supports Windows Server 2022.

Introducing the Case-to-case migration feature

This release introduces the ability to copy, or “migrate,” base documents from one case to another. When a document is migrated, the original document remains in the source location. The migration process creates a copy of the document in the destination location.

Note: The source case and the destination case must be in the same portal, and the administrator must have the appropriate permissions for both cases.

Case administrators migrate documents using the Migration window, which is available on the Document page in the Tools menu.

Information about migrating fields and objects

The following information relates to the migration of fields and objects.

Fields and objects available for migration

The following fields are mandatory and are always migrated:

Note: You can choose to migrate or not migrate any system fields that are not included in the following list.

• Document ID: The application maintains the Document ID throughout the migration process. If a document is migrated but its Document ID already exists in the destination case, the application updates the document in the destination case based on the setting selected for updating existing documents.

Note: After a document is migrated, if the Document ID is changed in either the source case or the destination case so that they no longer match, and then the document is migrated again to a new destination case, the application creates a new document in the new destination case.

• Levels: All documents are assigned the same levels in the destination case that exist in the source case.
• Source/attachment relationships: If a user migrates partial families, only direct source/attachment relationships are maintained. For example, Document C is attached to Document B, and Document B is attached to Document A. If the user migrates only Document A and Document C, the documents do not have a source/attachment relationship in the destination case.
• Portal Document Globally Universal ID (GUID): Use this value to track documents that have been migrated between cases. If a document in the source case does not have a value for Portal Document GUID, the application assigns a value for Portal Document GUID before the document is migrated.

Note: You cannot edit this field.

• Pages: When migrating documents that do not already exist in the destination case, the application migrates all page records, including those that are visible in the Image Viewer on the Documents page. When migrating documents that already exist in the destination case:
• If the user selects the option to update pages in the Migration window, the application updates the page records in the destination case to match the source case.
• If the user does not select the option to update pages in the Migration window, page records in the destination case do not change.
• Files: When migrating documents that do not already exist in the destination case, the application migrates all files associated with the source document. When migrating documents that already exist in the destination case:
• If the user selects the option to update files in the Migration window, the application migrates all files associated with the document in the source case and overwrites any files already in the destination case.
• If the user does not select the option to update files in the Migration window, the application does not copy any files.
• The application does not delete files from the destination case, even if they no longer exist in the source case.

The following fields and objects are migrated based on the user's selections:

• User-created fields: These include all fields found in Case Setup > Fields.
• Document fields: These include Document Date, Document Type, Document Title, Document Description, and Estimated Date.
• Annotations: Users can select specific annotation types to migrate.
• Notes: Users can select specific note categories to migrate.
• Binders: When creating migration column templates in preparation for migrating documents, users can migrate either all binders or no binders. Users cannot currently select specific binders to migrate. This is configured when creating your migration column template. For more information, see Create migration templates.
• Issues: When creating migration column templates in preparation for migrating documents, users can migrate either all issues or no issues. Users cannot currently select specific issues to migrate. For more information, see Create migration templates.
• People and Organizations: Users can select specific correspondence types to migrate, including custom correspondence types. Only values directly assigned to a document are migrated. Values that are associated with a document only through a link are not included. For example, Person A is coded to a document; Person A is linked to Organization A; Organization A is not coded to the document. Only Person A is migrated for the document. If a document is coded to a Person and an Organization, and the two are linked to each other, both values are migrated and linked in the destination case.

Fields and objects not available for migration

The following are examples of the types of data that are not available for migration:

• System fields that contain information specific to a case, such as:
• Fields that contain a job ID, such as Import ID and Evidence Job ID.
• Fields that contain status messages such as Document OCR Status.
• Fields that indicate when and how a document was added to a case, such as Document Created Type and Date Added to Case.
• Fields that display information derived from other fields or data, for example, Page Count.
• Entities (Data Models). Entities that are normally created when importing data, such as People, Organizations, and Custodians, are created in the destination case and are not copied from the source case.
• Productions (including renditions, which are not available to migrate at this time).
• Predictive coding data
• Search term families
• Audit history data
• Private binders
• Transcripts
• Suppressed documents

Fields and objects that do not exist in the destination case

The following applies when you migrate objects that exist in the source case but do not exist in the destination case:

• In general, if an object such as a field, binder, issue, annotation type, note category, correspondence type, or level is migrated with a document, but the object does not exist in the destination case, the application creates the object in the destination case.

Note: The migration process does not assign group permissions to new objects.

• The application creates “Family rank” pick list fields as regular pick list fields. A user can change the field properties in the destination case.
• The application creates security override binders as regular shared binders and not security override binders.
• The application does not migrate descriptions for binders and issues.
• The application does not migrate level labels.
• In most cases, migration does not retain data associated with users and dates. For example, migrated field values reflect the user performing the migration and the date the data was migrated. However, the following exceptions apply:
• Annotations retain the user and date information from the source case. If the user does not exist in the destination case, the values reflect the user performing the migration.
• Notes retain the user and date information from the source case. If the user does not exist in the destination case, the values reflect the user performing the migration.

Prepare to migrate documents

Before migrating documents, administrators must enable the Migrations feature and should create a column template to define the specific fields and objects to be migrated.

Enable the Migrations feature

To enable the Migrations feature, administrators must grant users access to the Processing - Migration feature.

To grant or deny access to this feature:

1. On the Case Home page, under Security, click Features.
2. In the row for Processing - Migration, under a group column, click the Allow or Deny option.

Note: You must be a Case Administrator to create a migration template.

To create a migration template:

1. On the Case Setup > Column Templates page, click Add to open the Add column template window.
2. On the Properties page, enter a name for the template. Templates are listed by name when you create a migration job.
3. In the Type list, select Migration.
4. Click Next.
5. On the Fields page, use the checkboxes to select fields and other objects to migrate. Click the checkbox at the top of the page to select all fields and objects. Click the checkbox for a grouping to select everything in the group. Use the search box to find specific fields.
6. Click Next.
7. The Annotations page displays all redaction and highlight types in the case. Use the checkboxes to select the redactions and highlights to migrate.
8. Click Next.
9. On the Security page, select which groups can use the template.
10. Click Save to create the template.

The new template appears on the Case Setup > Column Templates page.

Migrate documents

To migrate documents:

1. On the Documents page, in the List pane, select the check box next to the documents that you want to migrate.

Note: The greater the number of documents migrated, the longer the migration process takes. Best practices dictate migrating no more than 500,000 documents at a time.

2. On the Tools menu, under Output, select Migration.



The Migration window appears.

3. At the top of the Properties page is a message indicating how many documents you have chosen to migrate. Select the checkboxes next to the options to set the properties related to these documents:
• Include missing source or attachment documents
• Description
• Update group coding fields
• Run indexing and enrichment after migration



4. Click Next.
5. On the Destination page, select the destination for the migrated documents.

Note: The original document remains in the source location. The migration process creates a copy in the destination location.



6. Click Next.
7. On the Existing Documents page, use the following options to determine if the documents you have chosen to migrate already exist in the destination location and what should occur if they do.



• Check destination case for existing documents: Click Run check to determine whether the documents you have chosen already exist in the destination location.
• Action:
• Select Abort migration, if it contains an existing document ID to cancel the migration job if any of the documents you selected for migration shares the same document ID as a document in the destination location.
• Select Migrate new documents and update existing documents in the destination case if you want the migration to continue.



Select Append or Update to determine how the migration process handles field values. Selecting Append adds the new value to the end of the existing value. Selecting Update updates the value with the contents of the migrated field.

If you choose to update the fields, select any of the following elements to update:

• Source and attachment relationships
• Pages
• Files

Note: The migration process overwrites existing files. For more information on appending and updating, see Append vs. Update existing documents.

8. Click Next.
9. On the Fields page, select your migration template or choose to migrate all fields.

Note: The greater the number of fields and objects migrated, the longer the migration process takes.



Note: If you select All Fields in the migration window instead of a custom template, all fields that are available to add to a migration template are included, except Annotations and [RT] Family MD5 Hash. [RT] Family MD5 Hash is recalculated based on the [RT] MD5 Hash values that are migrated. If you want to include the family hash instead of recalculating it, use a custom migration template.

10. Click OK.

Append vs. Update existing documents

The following general rules govern the differences between updating and appending existing documents in the destination location:

• One-to-many fields: Append only adds values and never deletes values from the existing document in the destination case.
• One-to-one fields: Append updates a field to a different value if there is one in the source case. Append does not update a field to have no value, even if it has no value in the source case.
• People and Organizations: Same behavior as one-to-many fields.
• Group coding fields (All Custodians, All File Paths, and All Evidence IDs): These always act like an Append action even if you select Update.
• Binders: The migration process adds existing documents to any additional binders but never removes documents from binders.
• Issues: The migration process adds existing documents to any additional issues but never removes documents from issues.
• Annotations: New annotations are added but annotations are never removed as part of the migration process. If an annotation already exists with the same type, name, and location, a duplicate annotation is not added.
• Notes: New notes are added but notes are never removed as part of the migration process. If a note already exists with the same category, date, text, and private designation, it is not added again. New replies to the note are added. If a note that is also an annotation already exists with the same category, date, text, private designation, page number, and location, it is not added again.

View Migration job properties

Administrators can view the properties and progress of migration jobs on the Migration page.

To view information about Migration jobs, on the Case Home page, under Manage Documents, click Migrations.

Case Setup > People Identity: Date columns added to the People Identity page

Date columns now appear on the Case Setup > People Identity page for each of the three tabs: Non-normalized, Normalized, and All. These columns were added to help users view newer items more easily.

• On the Non-normalized tab, the Person created date column was added. This is the date that the person value was added to the case. Users can sort and filter on this column. This column is also added to the CSV when users download a report.



• On the Normalized and All tabs, the Person created date and Link created date columns were added.
• Person created date: This is the date that the person value was added to the case. Users can sort and filter on this column. This column is also added to the CSV when users download a report.
• Link created date: This is the date and time that the person value was associated with the Identity. Users can sort and filter on this column. This column is also added to the CSV when users download a report.



Note: Sorting these columns uses the latest date in a grouping to determine where the group should be sorted. Filtering displays the entire group if any of the person values have a date that is responsive to the filter.

Tools menu > OCR processing: Option to generate text files without page links in the footers

In previous versions, when users generated text files using OCR processing but did not embed that text in a PDF, the application added page number links to the footers of the resulting text files. In this version, users who submit OCR processing jobs can include or exclude page number links for each job. To access this functionality, on the Documents page, select one or more documents to OCR, select Tools > OCR processing, and select the Enable page links in OCR text check box in the OCR processing dialog box.

Case Options: Option to generate text files without page links in the footers

In previous versions, when users generated text files using OCR processing but did not embed that text in a PDF, the application added page number links to the footers of the resulting text files. In this version, Administrators can set the default behavior for this functionality by selecting the check box for the Enable page links in OCR text option on the Portal Management > Cases and Servers > [Case] > Case Options page.

Search: New behavior for Page Count searches

This release includes the following new behavior for Page Count searches on the Search page:

• When you perform a search for the Page Count field with the has a value operator, the application returns documents for which one or more of the pages records has a page count greater than zero.
• When you perform a search for the Page Count field with the does not have a value operator, the application returns documents for which one or more of the pages records has a page count of zero or is missing a page count. This search also returns documents that have no pages records.
• When you perform a search for the Page Count field, with the is operator, and a value of 0, the application returns documents for which one or more of the pages records has a page count of zero or is missing a page count.

Conditional Coding: Notes field now available

The Notes field is now available in the Conditional Coding pane. Previously, this feature was available only in the Code pane.

You can communicate with other reviewers by adding and replying to notes in a document. For example, you can use a note to ask your review lead a question about a document, and your review lead can add a reply to the note.

Tip: You can search for documents that include notes using the Note Content or Note Category fields on the Search page.

You can add a note to a document or to a document page.

Add a note to a document

To add a note to a document:

1. On the Documents page, in the List pane, select a document.
2. In the Conditional Coding pane, select the Notes template or the All Values template. Or if your case administrator included the Notes field in your conditional coding template, select that coding template.
3. Next to the Notes field, click Add note.



4. In the Add note dialog box:
• (Optional) From the Category list, select a category or leave the Uncategorized option.
• (Optional) By default, other users can view notes. If you want to hide the note from other users, select the Private check box.

Note: Administrators can view private notes.

• Enter the note text.

Tip: You can add a link to a document, an object, a transcript or a transcript page, or a website to your note.



• Click OK.

The note appears in the Conditional Coding pane.

Reply to a note in a document

To reply to a note in a document:

1. In the Conditional Coding pane, in the note, click Reply.



2. In the Reply to note dialog box, enter your note, and then click OK.



The reply appears in the Conditional Coding pane.

Edit a note in a document

To edit a note in a document:

1. In a note or reply, click Edit.



Note: Group Leaders and Group Members can edit only the notes that they created.

2. In the Edit note dialog box, make edits.
3. Click OK.

Delete your original note

To delete a note that does not yet have a reply:

• In the note, click Delete.

Delete a reply to a note in a document

To delete a reply to a note in a document:

• In the latest reply to a note, click Delete.

Note: The Delete button is available only for the latest reply to a note.

Add a note to a document page

You can add a note to a specific page in a document if the document has a PDF or image file.

To add a note to a specific document page:

1. Select a document.
2. In the View pane, on the toolbar, click the Image viewer button.
3. In the Image viewer, on the vertical toolbar, click the Note button.



4. Click the location in the document where you want to add the note.
5. In the Add note dialog box:
• (Optional) From the Category list, select a category or leave the Uncategorized option.
• (Optional) By default, other users can view notes. If you want to hide the note from other users, select the Private check box.

Note: Administrators can view private notes.

• Enter the note text.

Tip: You can add a link to a document, an object, a transcript or a transcript page, or a website to your note.

• Click OK.

The note appears in the Conditional Coding pane with a page icon that identifies the page number. When you click the page icon, the application takes you to the document page with the note.

Note: If you add a note to a document page in the View pane, you can edit or reply to that note in the Conditional Coding pane or the View pane. However, you can delete a note only in the View pane.

Delete a note on a document page in the View pane

To delete a note on a document page in the Image viewer in the View pane:

1. In the View pane, in the Image viewer, go to the page with the note.
2. Select the note.
3. On the vertical toolbar, click the Delete button.

Notes about notes

The icons in the Conditional Coding pane help you to identify if a user added a note to a document or to a document page.

• If a user added a note to a document from the Conditional Coding pane, the icon appears as a white page on a black circle.
• If a user added a note to a specific page in a document from the Image viewer in the View pane, the icon appears as a blue page.

Case Setup > Conditional Templates: Add a Notes field

Administrators can now add a Notes field to a conditional template, which allows users to work with this field in a coding template in the Conditional Coding pane.

To add a Notes field to a Conditional Template:

1. On the Case Setup > Conditional Templates > Coding fields page, in the Add field lists, select Document in the first list and Notes in the second list.



2. Click the Add button (plus symbol).

The Notes field appears in the Coding field table.

Case Setup > Grant access to Note Categories

Note categories provide a way for users to organize their notes to make them easier to find. For example, users can search for notes based on the note category. Administrators and Group Leaders can manage note categories.

To grant users access to a note category:

1. On the Case Setup > Note Categories page, click the link for a note category.
2. In the navigation pane, click Security.
3. Set the security for user groups to Allow or Write.

• Allow permission lets users in the group view and search for notes in the category.
• Write permission lets users in the group add, edit, reply to, and delete notes in the category.
• Administrators can edit and delete notes created by other users.

Note: Group Leaders and Group Members can edit and delete only notes that they created.

Introducing the Bulk Annotations feature

The Bulk Annotations feature allows users to apply highlights or redactions to multiple documents simultaneously.

Apply bulk annotations on the Documents page

You can apply annotations to multiple documents at the same time.

To apply bulk annotations:

1. On the Documents page, in the List pane, select the check box next to the documents that you want to apply bulk annotations to.
2. On the Tools menu, under Processing, select Bulk annotations.



The Bulk annotations window appears.

3. On the Exclusions page, the documents that you selected for bulk annotation are sorted by the number of documents that will be submitted for bulk annotation and the number of documents that will not be submitted. In the Document must be excluded area, you can search for documents that will not be annotated using the Bulk Annotations feature. Click a number to see the list of affected documents. Click Next.



Note: Documents must be imaged in PDF format prior to using the Bulk Annotations feature.

4. On the Terms page, in the Option list, select one of the following:
• Advanced query syntax: Enter the search terms and operators to identify the text that you want to highlight or redact.



• Search Term Families: Select the search term family that identifies the terms you want to highlight or redact.



Note: The Document count column displays only the number of base documents and not renditions.

5. Click Next.
6. On the Annotation page, select either of the following options:
• Redaction: Click the box for the color of the redaction. You can select only black or white. Select the label for the redaction in the list.



• Highlight: Select a highlight option from the list.



7. Click OK.

The application submits the annotation job.

View documents displaying bulk annotations

After the bulk annotation job is completed, you can view the annotations in the Annotations List pane, which you can access from the Image viewer in the View pane.

Administer the Bulk Annotations feature

The Bulk Annotations feature allows users to apply highlights or redactions to multiple documents simultaneously. This section describes how to administer this feature.

Enable the Bulk Annotations feature

To enable the Bulk Annotations feature, administrators must grant users access to the Processing - Bulk annotations feature.

To grant or deny access to this feature:

1. On the Case Home page, under Security, click Features.
2. In the row for Processing - Bulk annotations, under a group column, click the Allow or Deny option.

Enable bulk annotation system fields

Administrators can make bulk annotation system fields available to user groups. The fields appear as search criteria that the user can select on the Search page and as columns to display in the List pane.

The following system fields are available:

• Bulk Annotation ID: The job ID of the bulk annotation job that was submitted.
• Bulk Annotation Reverted ID: The job ID of the reverted bulk annotation job that was submitted.
• Bulk Annotation Reverted Status: The current status of the reverted bulk annotation job.
• Bulk Annotation Status: The current status of the bulk annotation job.

View documents displaying bulk annotations

To view the annotations in your document:

1. On the Manage Documents > Bulk Annotations page, on the Bulk annotation jobs tab, click the number displayed next to your job ID in the Documents column.
2. On the Documents page, in the List pane, select the document in which you want to view the annotations.
3. In the View pane, in the Image viewer, click the Annotation List button. The Annotation List pane displays the number of annotations and the page on which those annotations appear.

View Bulk annotation job properties

Administrators can view the properties and progress of bulk annotation jobs on the Bulk annotation jobs and Reverted jobs pages.

To view information about bulk annotations and reverted jobs:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. Select the Bulk annotation jobs or Reverted jobs tabs to view a list of jobs.



The columns that appear on these pages provide information such as Job ID, the number of documents annotated, the search terms or search term family used, the number of search terms identified, the number of annotations applied, and the name of the user who created the job.

Revert previously annotated documents

If you have applied bulk annotations to a selection of documents, you can revert the bulk annotations job such that the annotations are removed. When you revert a bulk annotation, the application does the following:

• Removes the highlights or redactions from the document.
• Adds information about the reverted job to the Reverted jobs tab.

To revert a bulk annotation job:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. On the Bulk annotation jobs page, select the check box next to the bulk annotation job that you want to revert.

Note: You can revert annotations only for documents that were previously annotated using the Bulk Annotations feature. If you revert a bulk annotation job, all annotations that were applied using the Bulk Annotations feature are removed, including annotations modified manually.

3. On the toolbar, click Revert.
4. In the Revert bulk annotations dialog box, click OK.

The application reverts the bulk annotations in the chosen document set. A dot appears in the Reverted column on the Bulk annotations page, and a new line appears on the Reverted jobs page that displays the details of the reverted job.

Download a bulk annotations report

To download a bulk annotations report to an .xls format:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. On the toolbar, click Download report.

Manage Documents > Ingestions and Imports: New system fields for Exif format

This release includes the following three new system fields to support the Exchangeable image file format (Exif):

• [Meta] Exif Date Time: The date and time value from the Exif photo metadata.
• [Meta] Exif Date Time Digitized: The date and time of the digitized image value from the Exif photo metadata.
• [Meta] Exif Date Time Original: The date and time of the original image value from the Exif photo metadata.

Note: If an ingestion includes these fields, the application selects them by default on the Customize Fields page in the Advanced settings window. If an import includes these fields, you can update these fields on the Field Map page in the Import window.

Conditional Coding pane and Memo Editor pane: New user interface when linking to transcripts or transcript pages from a memo field

When you add a link to a transcript from a memo field in the Conditional Coding pane or the Memo Editor pane, the Link transcript dialog box now has a new user interface. The functionality is the same.

To access this dialog box from the Conditional Coding pane, in a memo field in a coding template in the Conditional Coding pane, double-click text, and then click Transcript link on the inline menu.

To access this dialog box from the Memo Editor pane, double-click text, and then click Transcript link on the inline menu.

Find and view hash duplicate documents in the Similar section in the Related pane

When you select documents in the List pane, the application includes hash duplicate documents that you can now view in the Similar section in the Related pane.

Hash duplicate documents have a similarity of 100.

The master duplicate document appears as the first document in the list in the Similar section.

In the Similarity column, the bold green type indicates the master duplicate document.

Tip: Hover over the number to in the Similarity column to display the tooltip for the Master duplicate document.

The individual duplicate documents appear after the master duplicate document. The number in the Similarity column appears in bold black type to indicate an individual duplicate document.

Tip: Hover over the number in the Similarity column to display the tooltip for an Individual duplicate document.

Note: The application displays other similar documents and the similarity scores after the individual duplicate documents.

Connect API Explorer: importJobAddDocuments mutation updated for creating links

The importJobAddDocuments mutation now allows users to create links between person values and organization values within a case. To successfully import these links, you need to create and execute the following three mutations: The first to create the import job, the second to import the data containing the links, and the last to run the import job request.

Sample mutation to create the import job and retrieve a job ID:

mutation MyJobCreateMutation {
  importJobCreate(caseId: 6077
    input: {
      name: “Import People and Organization Links”
    }
  )
  {
    rdxJobId
  }
}

Results of the import job creation with needed job ID:

{
  “data”: {
    “importJobCreate”: {
      “rdxJobId”: 68
    }
  }
}

Sample import mutation using the created job ID:

mutation MyJobAddMutation {
  importJobAddDocuments(
    caseId: 6077
    input: {
      rdxJobId: 68,
      documents: {
        documentId: “POLinks_00000002”,
        correspondence: [
          {type: “From”,
            people: “fromme@from.com”,
            action: InsertUpdate},
          {type: “To”,
            people: “tome@to.com”,
            orgs: “I work at To”,
            action: InsertUpdate,
            linkPeopleOrg: Insert},
          {type: “To”,
            people: “justme@me.com”,
            orgs: “Me”,
            action: InsertUpdate},
          {type: “CC”,
            orgs: “Copy for everyone”,
            action: InsertUpdate},
          {type: “CC”,
            people: “aperson@everywhere.com”,
            orgs: [“Everywhere”, “Nowhere”],
            action: InsertUpdate,
            linkPeopleOrg: Insert}
        ]
      }
    }
  ) {
    documentCount
  }
}

Results of importing the link data:

{
  “data”: {
    “importJobAddDocuments”: {
      “documentCount”: 1
    }
  }
}

Sample mutation for running the import job:

mutation MyExecuteImportJobMutation {
  importJobSubmit(
    caseId: 6077,
    input: {
      rdxJobId: 69
    }
  )
  {
    rpfJobId
  }
}

Audio: Updated language models for the audio transcription feature

Nuix Discover uses the IBM Watson™ Speech to Text service for the audio transcription feature.

On September 15, 2022, IBM will deprecate the previous-generation language models and support only the next-generation language models.

Per IBM, “Next-generation models have higher throughput than the previous-generation models, so the service can return transcriptions more quickly. Next-generation models also provide noticeably better transcription accuracy.”

In preparation for this change, we migrated the previous-generation language models to the next-generation language models in Nuix Discover. We also added four new language models.

For information about the IBM Watson™ Speech to Text next-generation language models, see Next-generation languages and models | IBM Cloud Docs.

As of this release, the following next-generation language models are available in Nuix Discover:

• Arabic (Modern Standard)
• Chinese (Mandarin)
• New: English (Australian)
• English (UK)
• English (US)
• French
• New: French (Canadian)
• German
• New: Italian
• Japanese
• Korean
• Portuguese (Brazilian)
• Spanish
• New: Spanish (Latin America)

The following previous-generation language models were available in Nuix Discover until version 10.11.001:

• Arabic (Modern Standard)
• Brazilian Portuguese
• Chinese (Mandarin)
• English (UK)
• French
• German
• Japanese
• Korean
• Spanish

Portal Management > Processing > Enhancements to the data filtering stage of an Ingestions job

As part of the ongoing effort to enhance the processing performance of Ingestions, to optimize the performance of the Data Filtering stage of an Ingestions job, the following four individual tasks are now a single data filtering task:

• Filter by Date Range
• Filter by excluded files
• Filter by NIST
• Filter by De-duplication

Portal Management > Settings: New portal options for Linux/Docker Ingestions to reduce preprocessing time

As part of the ongoing effort to enhance the processing performance of Ingestions in SaaS environments, the following two new portal options are available on the Portal Management > Settings > Portal Options page.

Note: These options apply only if you use the Linux/Docker Ingestions feature. If you configure the following two new portal options, verify that the Enable Linux/Docker Ingestions check box is selected.

• Enable Linux/Docker Ingestions Autoscale EC2 Instances: If you select this check box, the Coordinator automatically provisions a Linux Ingestions worker when you submit an Ingestions job.
• Ingestion AWS Lambda Function Name: Enter the name of the AWS Lambda function used to provision Linux Ingestions workers.

Connect API Explorer: Upgrade to case comparison operators

The Connect API Explorer now contains a new filter operator (op) when querying case data. Case operators used to support comparison patterns for LIKE, used for strings, and EQUALS, used for everything else. Now, a user can query case data using other comparison patterns against dates, strings, and numbers expanding upon the original operators.

String operators:

• Like
• StartsWith
• Equals
• NotEquals
• HasValue
• HasNoValue

Number and Date operators:

• Equals
• LessThan
• LessThanOrEqual
• GreaterThan
• GreaterThanOrEqual
• NotEquals
• HasValue
• HasNoValue

Sample query:

{
  cases(
    filter: {name: {op: Like, value: ”enron“}, 
      caseCreatedDate: {op: LessThanOrEqual, value: ”2020-02-12“}, 
      organizationId: {op: Equals, value: 6}}
  ) {
    id
    name
    caseCreatedDate
  }
}

Sample query results:

{
  ”data“: {
    ”cases“: [
      {
        ”id“: 6077,
        ”name“: ”Clean_Enron“,
        ”caseCreatedDate“: ”2017-10-16T17:44:04.95Z“
      }
    ]
  }
}

Connect API Explorer: Query saved searches

You can now query saved searches, using the savedSearches query, and retrieve their related data.

Parameters and filters available are:

• id
• name
• createdDate
• createdByUser

Sample query:

query cases {
  cases(ids: [1, 5]) {
    savedSearches {
      id
      name
      createdDate
      createdByUser {
        id
        userName
      }
    }
  }
}

Sample query results:

{
  ”data“: {
    ”cases“: [
      { ”name“: ”Acme6_PM2“, ”savedSearches“: [] }
      ,
      {
      ”name“: ”Clean_Enron“,
      ”savedSearches“: [
      {
      ”id“: 15,
      ”name“: ”[PERF] - RW - DO NOT DELETE FO FOO“,
      ”createdDate“: ”2016-03-15T22:48:46.743Z“,
      ”createdByUser“:
      { ”id“: 181, ”userName“: ”lsimpson“ }
      },
      {
      ”id“: 11,
      ”name“: ”[PERF] [WF] [VC] - DO NOT DELETE FO FOO“,
      ”createdDate“: ”2016-02-13T00:13:25.613Z“,
      ”createdByUser“:
      { ”id“: 2, ”userName“: ”abuckholt“ }
    }
    ]
  }
  ]
  }
}

Connect API Explorer: caseCreate mutation updates

The caseCreate mutation now contains a few new conditional updates based on the organizationId field.

• When running the caseCreate mutation, it uses the organization’s default settings for servers and file repositories. However, if an organization’s default settings are not set, a message appears stating Organization defaults are not set for required servers or repositories.
• If you do not provide an organization ID in the mutation, the application uses the user’s organization ID.
• But, if the provided organization ID is not valid, a message appears stating Invalid organizationID input.
• If the provided organization ID is valid, the application creates a new case under that ID. When the application creates this case, it schedules case metrics jobs based on the organization settings. But, if these settings do not exist, the case metrics job runs monthly.

Required fields:

• caseName
• organizationId

Optional fields:

• Description
• scheduleMetricsJob

Sample mutation:

mutation {
  caseCreate(
    input: {organizationId: 1, caseName: ”Cookie Monster“, description: ”nom nom nom&ld”quo;, scheduleMetricsJob: true}
  ) {
    case {
      id
    }
  }
}

Conditional Coding: Customize the layout and zoom

In the Conditional Coding pane, you can now customize the layout of the coding field names and values in the Single coding and Mass coding views.

To customize the layout in the Conditional Coding pane:

1. On the Conditional Coding pane menu, select Options.
2. In the Options dialog box, under Layout, select one of the following options:



• Auto: With this option, which is selected by default, the application automatically adjusts the layout (top and bottom or left and right) of the field name and field values depending on the width of the pane.
• Top and bottom: If you select this option, the application always displays the field values underneath the field name.



• Left and right: If you select this option, the application always displays the field name on the left side of the pane and the field values on the right side of the pane.



3. Click OK.

You can also change the zoom level to increase or decrease the display size of the content in the Single coding and Mass coding views. A smaller zoom level can be useful for showing more information on the screen.

To change the zoom level:

1. On the Conditional Coding pane menu, select Options.
2. In the Options dialog box, under Zoom (%), adjust the percentage. The default setting is 100. The zoom percentage range is 75-150.
3. Click OK.

Conditional Coding: New Issues - Custom field for conditional templates

If your administrator added the Issues - Custom field to a conditional template in the Conditional Coding pane, you can now code documents to the issues included in this field.

Conditional Coding: New Source/Attachments field for conditional templates

If your administrator added the Source/Attachments field to a conditional template in the Conditional Coding pane, you can use this field to see where a document is positioned within the tree of its related Source/Attachments documents.

The current active document appears in black type, and the related document IDs are links that you can click to open each document in a standalone window. The icon and tooltip to the left of a document ID indicate the document type, and the icon color represents the coded value of the quick code field (if configured).

The Source/Attachments field also appears in the System Fields section of the All Values template in the Conditional Coding pane.

Browse pane: New Identities section

The Browse pane now includes a new Identities section. The identities that appear in this section are related to the Identity entity in a data model.

Note: If the Identities section does not appear in the Browse pane by default, you can add it to the Browse pane. To do so, from the Browse pane, select Options. In the Browse settings window, select Identities, and then click Save.

Case Setup > Conditional Templates > Coding fields: Enhancements to the Binders - Custom field

As of this release, to modify the values in the Binders - Custom field on the Case Setup > Conditional Templates > Coding fields page, you can click the blue Binders - Custom link.

Previously, to modify the values in the Binders - Custom field, you had to delete the field and then add a new Binders - Custom field.

Case Setup > Conditional Templates > Coding fields: Add an Issues - Custom field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Issues - Custom field to a conditional template.

To add an Issues - Custom field to a conditional template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Issues - Custom.

Note: You can add only one Issues - Custom field to a coding template.

2. Click the Add button.



3. In the Issues - Custom dialog box, select one or more issues, optionally select the Include sub-issues check box before selecting a parent issue to include all of its child issues with it in the field, and then click Save.



The Issues - Custom field appears at the bottom of the list of coding fields.

Tip: You can click anywhere on the row to drag and move the field to a new location in the template. You can click the blue link to adjust the issues in the Issues - Custom field.



4. The Issues - Custom field is then available in the Conditional Coding pane for the template, and reviewers can code documents to the issues in this field.

To delete the Issues - Custom field from the template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, select the check box next to the field.
2. On the toolbar, click Delete.

Case Setup > Conditional Templates > Coding fields: Add a Source/Attachments field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Source/Attachments field to a conditional template.

The Source/Attachments field displays a tree view of the document IDs of all source/attachment documents that are related to the active document. The document IDs of the related documents are links to open each document in a standalone window.

To add a Source/Attachments field to a conditional template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Source/Attachments.
2. Click the Add button.



The Source/Attachments field appears at the bottom of the list of coding fields.

Tip: You can click anywhere on the row and drag and move the field to a new location in the template.

3. The Source/Attachments field is then available in the Conditional Coding pane for the template, and reviewers can use the field to learn about the Source/Attachments documents that are related to the active document.

To delete a Source/Attachments field from the template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, select the check box next to the field.
2. On the toolbar, click Delete.

Manage Documents > Ingestions: New system fields to support Nuix Engine multimedia file types

Three new system fields are now available on the Case Setup > System Fields page, as described in the following table. These fields are populated in Nuix Discover when you ingest the following multimedia file types using the Nuix Engine.

• Nuix Engine multimedia file type:
• ISO Media Type:
• Nuix Discover system field: [Meta] ISO Media Type
• Description: Type of media file
• Multimedia Video Codec:
• Nuix Discover system field: [Meta] Multimedia Video Codec
• Description: Compression standards used to code or decode a video file. Requires an FFmpeg plugin.
• Multimedia Audio Codec:
• Nuix Discover system field: [Meta] Multimedia Audio Codec
• Description: Compression standards used to code or decode an audio file. Requires an FFmpeg plugin.

Note: You can update to these fields when using the Imports feature.

Case cloning: Restricted user assignment setting now retained when cloning a case

When you clone a case, the application now retains the setting for the Restricted user assignment, which is available on the Properties page for a case.

Note: The application also retains the setting when you clone a case—even if you select the Clear data check box on the Case Details page in the Clone case window.