Back to database

Tim McAleer, Florentine Films's AI use case

Producer / post-production technologist at Florentine Films

Built AI workflows for documentary post-production at Florentine Films: a searchable media database for archival assets, an iOS field-research app for physical archives, and a Mac OCR tool for difficult historical documents.

The problem

What was broken before AI

Documentary teams often work with huge amounts of archival material. For the Muhammad Ali series alone, Florentine Films gathered more than 20,000 still images and hundreds of hours of footage. Every image, clip, audio file, and document needs context: what it shows, where it came from, what metadata it contains, and how it might connect to a story. That logging work is slow, manual, and easy to bottleneck.

What changed

What the use case made possible

Tim turned several of those bottlenecks into custom AI tools. A backend workflow uses vision models, metadata, transcription, and embeddings to catalog archival media. A custom iOS app called Flip Flop helps researchers photograph the front and back of physical archive materials while embedding descriptions and transcripts into the files. A Mac utility called OCR Party lets researchers select a specific region of a difficult document and extract cleaner text from it.

Why this matters

Why this use case is worth studying

Tim’s workflow is valuable because it uses AI to amplify research, not replace it. The creative work is still finding the story, making choices, and building the film. AI helps with the repetitive work that gets in the way: describing images, pairing front/back notes, transcribing audio, making documents searchable, and finding similar assets across a huge archive. That is a practical model for any field built on mountains of source material.

Use this when

When this pattern applies

Use this pattern when a creative or research team has too much source material to describe, tag, and search manually. It works especially well for archives, documentaries, museums, legal collections, historical research, oral histories, and any workflow where real material needs to become searchable without losing context.

Exponential Builder analysis

01

Build around the bottleneck, then widen the system.

Tim did not start with a grand AI studio; he started where archive work gets slow: logging, describing, pairing, transcribing, and searching source material.

02

Metadata is the guardrail.

Historical archives punish confident guesses, so the workflow puts known context—EXIF data, source URLs, dates, locations, collection notes—ahead of model-generated description.

03

Better retrieval expands creative options.

When stills, footage, audio, field photos, and document excerpts become searchable by meaning, researchers and editors can find connections that keyword folders often bury.

Who this is for

Best fit

Documentary filmmakers

Archivists and researchers

Museum and library teams

Historical researchers

Media production teams

Editors working with large footage libraries

Anyone managing images, video, audio, or documents at scale

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not let AI invent historical details that metadata does not support.

Avoid processing everything before proving the workflow on one asset type.

Keep uncertain OCR words flagged instead of silently guessed.

Do not separate images from their source and collection context.

Make the tool fit the researcher’s real field workflow, not an idealized office process.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Start with the archive problem

Tim focuses on the places where researchers spend hours logging, describing, and organizing material.

02

Add factual guardrails before asking AI to describe things

Embedded metadata, source URLs, dates, locations, and photographer details help keep descriptions accurate.

03

Process each media type differently

Images, video, and audio each get the kind of analysis that fits them best.

04

Make search semantic, not just keyword-based

Embeddings let researchers find visually or thematically similar assets even when the exact words differ.

05

Build field tools for real archive work

The Flip Flop app keeps front/back document photos paired and enriched before researchers return to the office.

06

Isolate hard document regions

OCR Party lets users crop only the section they care about, then extract cleaner text from damaged, faded, or handwritten material.

Copy the pattern

The reusable idea

Pattern in one sentence

Use AI to enrich real source material with descriptions, transcripts, metadata, and semantic search so creative teams can find the story faster.

Reusable idea

Tim’s use case is a reminder that AI is often most useful when pointed at the tedious parts of serious creative work. If a team has a mountain of source material, the first opportunity may not be generating new content. It may be making the real material easier to describe, search, connect, and reuse. Better access to the archive gives the creative team more room to find the story.

Steal this workflow

Archive AI workflow recipe

1

Pick one painful asset type first, such as still images.

2

Define the fields a useful record needs: visible content, source, date/location if known, people/objects, rights or collection context, search terms, uncertainty notes.

3

Extract embedded metadata before sending anything to an AI model.

4

Ask the model to describe only what is visible or supported by metadata.

5

Store the result in the same place researchers and editors already search.

6

Add semantic search once descriptions are consistent enough to trust.

7

Expand media-by-media: video gets frame captions plus audio transcription; physical archive items need front/back pairing; difficult documents need cropped-region OCR.

8

Keep a review path for uncertain names, dates, handwritten text, and any description that could affect historical interpretation.

Suggested prompt

“Analyze this archival asset for a documentary research database. Use the embedded metadata and provided source context as the factual ground truth. Describe what is visible or audible, list notable people/objects/places only when supported, include useful search terms, preserve any source or collection context, and flag uncertain details instead of guessing. Return the result in structured fields suitable for a searchable archive.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all