Skip to main content
Skip table of contents

Version 2.3.7

Product: Cognitive Toolkit

Version: 2.3.7

Date: July 27, 2020

  • Combined Add Hash and Extracted Text Tool: We have consolidated a number of individual tools in favor of the combined AddHashAndExtractedText tool, which can be used to calculate the hash of a file, or extract text from a file, or do both at the same time. The –action-keyword is used to determine which mode the tool is operating in and –source-settings is used to specify the connector file (leave blank for file system). Supported sources are currently File System, Content Server, SharePoint, FileNet and Box. See –help for available parameters and options. Note that with this release, the following tools are deprecated (as they are now replaced by this combined tool):

    • AddHashAndExtractedTextFromContentServer

    • AddHashAndExtractedTextFromSharePoint

    • AddHashAndExtractedTextFromFileNet

    • AddHashFromBox

    • AddExtractedTextFromBox

(Ref: CT-334, CT-1047, C-1048, CT-1049, CT-1050, CT-1062)

  • Migration Validation: The Cognitive Toolkit now ships with a tool that can be used to compare 2 indexes – something that would typically be used to validate that everything that was in a source system and then migrated, was actually migrated as expected. See –help for IndexCompare for available parameters and options. (Ref: CT-475)

  • Add Classifications: The Cognitive Toolkit now ships for a tool for adding Classification and/or RM Classification data to an already crawled Content Server Shinydocs Index. See –help for AddClassifications for available parameters and options. (Ref: CT-486)

  • Path Validation for Additional Content Management Systems: The functionality of the AddPathValidation tool was expanded to support Content Server, SharePoint, FileNet and Box, in addition to existing support for File Shares. Note that for Content Server and Box, a path is considered valid if the Object ID still exists in the ECM (i.e. it has not been deleted). See –help for AddPathValidation for available parameters and options. (Ref: CT-807)

  • Migrate to Multiple Node IDs: The functionality of the MigrateToContentServer tool was expanded to support migration to multiple NodeIDs. See –help for MigrateToContentServer for available parameters and options. (Ref: CT-963)

  • Open Clustering – Narrowed Results: Improvements were made to our Open Clustering functionality to narrow results by ignoring short (1 or 2 letter) words, numbers and common English “stop” words. Note that you will need to update the visualization used if your Index name is something other than “shiny” (and just update this reference to the name of your Index). The dashboard works best when combined with a path-based filter (as the tool shows words used more in the selected path vs. what is in the rest of the Index). (Ref: CT-1017)

  • Support for “Future” Crawl Dates: The CrawlFileSystem tool was improved to support the crawling of “future” dates (i.e. files that somehow got date-stamped in the future). (Ref: CT-1027)

  • Visualization Improvements: Date Histograms: The 3 existing date histogram visualizations (e.g.: Number of Files by Created Date) were modified to report on yearly values. With this change the 3 previously included filters such as “Created in Past 7 Years” were removed. (Ref: CT-1004)

  • Support for Multiple Identities in Set File System Permissions: The functionality of the SetFileSystemPermissions tool was expanded to support multiple users and/or groups. See –help for SetFileSystemPermissions for available parameters and options. (Ref: CT-1045)

  • Bug Fix: Fixed an issue where when crawling Box, if a user cannot be fetched, the app will now fail gracefully with better error logging. (Ref: CT-879, CT-880, CT-914)

  • Bug Fix: Fixed an issue where, when extracting text from a MSG file, CC email addresses were incorrectly populated in the TO field. (Ref: CT-1028)

  • Bug Fix: Fixed an issue where ExportFromIndex was not exporting all values. (Ref: CT-1082)

  • Bug Fix: Fixed an issue where in some cases DisposeInBox was not deleting the expected items. (Ref: CT-1100)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.