Redacting Roadmap – User Scenarios

September 21, 2018

As part of the TSG Product Roadmap and based on clients requests, we are currently in the midst of adding additional redaction capabilities across our product set. This post will discuss the different user redaction scenarios and how our products (OpenAnnotate, OpenMigrate and the OpenContent Search and Case) are being updated to satisfy these requests. These capabilities are being added for Alfresco, Documentum, Hadoop and potentially Amazon DynamoDB as supported repositories. Other repositories or just file stores (ex: Amazon S3) will be added as required by customers.

The current user scenario available now in OpenRedact (part of the OpenAnnotate product) focuses on manual redaction for documents in the repository or during document ingestion. In this scenario, a user would like to redact key information from a document and, with the OpenRedact interface, can either have these redactions made permanent replacing the new document or have a new redacted document created with security to the new and old document updated to only allow most access to the newly redacted document.

Redaction Roadmap – Bulk redaction across the repository – The right to be forgotten

One of the first user scenarios we are focused on is redacting a name across the repository, typically one of the main requirements for GDPR(download our GDPR readiness guide). While documents can always be redacted manually in the scenario above, this scenario involves:

A customer or other party requests all information about their name be redacted.

A user initiates a full-text search against a document repository and finds 1 to many documents that contains the name.

The user selects all the documents and the bulk action Redact.

The name is redacted on all the selected documents.

The initial scenario will focus on just the name but we would envision that later scenarios will include the ability to add ad hoc fields (ex: address) as well as do some analysis of the documents themselves to suggest other values to redact (family member names, patterns…..).

Redaction Roadmap – Bulk redaction within a Case Folder

Similar to the bulk redaction across the repository, another scenario would provide the bulk action within a folder. In this scenario, a user would want to redact specific case information from the documents in the case. A folder action Redact would provide the ability to suggest to the user both redaction values based on information about the case. For example, in an insurance claim scenario, the interface would suggest information about the claim (Claimant Name, Address, birthday….) to be redacted across the claim folder. This scenario involves:

A user decides to redact a case folder and selects the folder action Redact from within the case folder.

The interface prompts the user for values to be redacted based on the case folder.

The user selects the values to be redacted.

The documents are redacted within the case folder either permanently or by creating a copy with appropriate security around the new and original unredacted document.

Once redaction values are created for a case folder, TSG is anticipating saving these values for ongoing redaction for new documents entering the case folder. This redaction could happen upon manual upload or in a bulk upload scenario.

To support the migration of production documents to test environments, TSG is envisioning automating a case folder redaction scenario (with manual review) based on case folder data.

Redaction Roadmap – Video Redaction

For 2019, we are considering adding redaction not just to documents but also to videos. The ability to blur or redact faces, licenses plates for other personal information from a video or series of video is something we are currently considering for clients.

Summary

User scenarios around redacting in bulk are being added for both repository as well as folder redaction. While OpenRedact will always provide manual capabilities, more and more of the redaction capabilities are being added in bulk for specific values based on user queries or case folder date, patterns and soon additional AI analysis of the document itself. The TSG Redaction roadmap plans are for most of the folder and repository redaction to be complete and in beta release within the 4th quarter of 2018. Updates will include new capabilities for the Open Content Search and Case as well as OpenMigrate.

Let us know your thoughts and any additional scenarios you would like us to consider below.

[…] Annotations AND Redaction – with documents being distributed, the ability to protect the information contained becomes more important. Couldn’t help but see the news about Paul Manafort’s lawyers the improperly redacting documents (and not the underlying text). We are seeing ECM 2.0 clients do automation of redactions. […]

One of the goals of most claims processing/member service departments for Auto, Health or any type of insurance is how to improve the efficiency of the claim document access and processing for a better customer experience, satisfaction and retention. In regards to documents, more and more insurance clients are looking to make claim document access […]

Earlier in the Capture 2.0 series, we discussed how modern capture solutions would improve the metadata extraction process when processing documents. Capture 2.0 solutions will expand on existing zonal as well as key/value pair methods for extracting metadata by incorporating machine learning algorithms to improve accuracy over time. This post will explore how users can […]