Two of us are behind Tetrak, the tools and the services: one from data engineering, one from collections. The work sits where those two meet.
Tetrak is the two of us. We publish open-source tools
that turn scans of old print into searchable text and make catalogues
searchable across scripts, and we work with collections teams
directly on assessment, search sites and grant applications.
The pairing is deliberate. Reading a scan, scoring the result and routing
each file to the engine that handles it best are pipeline problems, the kind
that turn up wherever unreliable input has to be made trustworthy. What
counts as a usable transcript, how a catalogue is really kept, and what a
collection needs in order to be findable are not pipeline problems at all.
Stevie brings the first set; Yvette brings the second.
Pipelines and engineering
Stephen Masters
Stevie has spent close to three decades building software that turns messy,
real-world data into something trustworthy; from foreign exchange pricing and
compliance systems in banking, to power trading and generation platforms for
energy companies, to the commodities data platforms he builds today. That work
has given him a specific kind of expertise: designing pipelines that take in
unreliable input, clean and validate it, and route each piece to wherever it’s
handled best — the same problem Tetrak OCR solves for scanned archives. He works across the
stack, from cloud architecture down to the code itself, mostly in Python and
data engineering these days, with Java, Angular and React still in the toolkit.
He’s drawn to problems where messy signals (market data, sensor readings,
satellite images) turn out to predict something useful, and Tetrak’s unruly
archives are simply the latest iteration of that.
Yvette has spent over two decades running the systems that hold cultural
institutions’ collections together — taxonomy and metadata, permissions, ingest
and delivery, upgrades, integrations, and the documentation that keeps it all
usable. That’s taken her through the Walt Disney Company, managing digital image
assets and later building a taxonomy and metadata framework from scratch for
Imagineering’s R&D collection; the Natural History Museum of Los Angeles County;
and the Academy of Motion Picture Arts and Sciences, where she led the migration
of the public collections catalogue to a new platform and now administers the
systems behind roughly 2.6 million cataloguing records. Across all of it, she’s
worked on both sides of the same problem: what a collection needs to be
findable, and what a system needs to make that possible. That grounding —
knowing exactly what curators and archivists deal with day to day, in real,
unruly collections — is what Tetrak is built on.