The Media Nuix Indexed but Cannot Read Aloud

What you can do together

• Transcribe and search the audio and video a Nuix run identified, which a document index cannot read.
• Redact media at volume in Redactor before it reaches reviewers.
• Keep case identifiers on the media so the document review and the media review remain one matter.
• Size the media volume before a deadline does, which is the risk when Nuix is involved at all.

How it connects

Media identified during Nuix processing would come across over its API or as exported output, and the case identifiers would travel with it as attributes so the review stays joined up rather than becoming two parallel exercises. Audio and video would then be transcribed and indexed, and redacted in Redactor where that is required, which is the work Nuix does not do.

Scale is the thing to scope, because Nuix is used precisely when volumes are large. A processing run that identifies tens of thousands of media items is a different integration from one that identifies a few hundred: the first needs the ingest paced and the transcription capacity sized, and an engagement would settle that rather than discovering it during a matter with a deadline.

Nuix would stay the processing and indexing platform, and its index stays authoritative for the document set. Where redacted or transcribed output needs to return, the documented export destinations are AWS storage and SharePoint, so output lands in a destination the organization controls rather than being written back into Nuix directly; wiring it further is scoped work.