Explore by topic
Implementation
Getting from a shared drive to something searchable. Folder paths are metadata in a bad encoding and extracting them is the migration; the file copying is a weekend. Also the two decisions, an unavoidable surface and a named taxonomy owner, that determine whether anyone uses the result.
-
How to retry failed media processing jobs automatically with a DAM-first workflow
Learn how to implement idempotent media retries with clear architecture, failure controls, measurements, and current Cloudinary documentation.
-
How to upload files over 100MB with progress tracking with a DAM-first workflow
Learn how to implement large-file upload design with clear architecture, failure controls, measurements, and current Cloudinary documentation.
-
Migrating off shared drives without losing twenty years of history
The file copying is a weekend. The reason migrations run a year late is that folder paths contain most of your metadata and nobody planned to extract it. Here is the order of operations that works, and the two decisions that determine whether anyone uses the result.