Organization
What the acronym means
DAM stands for Digital Asset Management. Applied to photography, a DAM is a system that centralises the ingestion, description, search, rights, and distribution of an image collection.
The term has become commercially elastic. It covers both a desktop application for a solo photographer and an enterprise platform costing tens of thousands a year. So before comparing products, work out which functions you actually need.
The functions that separate a DAM from a plain catalog
- Rights and licences attached to the image, with validity dates and usage restrictions.
- Roles and approvals: who may describe, who may publish, who signs off.
- Controlled distribution: shared selections, derivatives generated on demand, watermarks.
- Auditability: who changed what, and when.
- Interoperability: exports to documentary standards, harvesting by a third-party system.
A photo catalog covers description and retrieval. A DAM adds governance and circulation.
When the question becomes real
Three signals, more reliable than any volume threshold:
- Several people describe or distribute the same holdings, and you’ve already seen two diverging versions of the same caption.
- You deliver regularly to third parties, and “who may use this image, and until when” keeps coming up without a dependable answer.
- The holdings have heritage value: they will be transmitted, deposited with an institution, or must stay citable after you.
Below those signals, a rigorous catalog plus metadata discipline does the job for far less.
The criterion people forget to check
A DAM structurally concentrates all of a collection’s descriptive value. So the decisive question isn’t what it can do, but what it hands back the day you leave: a complete, readable, re-importable export — or a proprietary database and some screenshots.
Ask that before the sales demo, not after three years of data entry.
In practice
- List the functions you need today, separately from the ones that impress you.
- Check that metadata is written into files or sidecars, not only into the database.
- Request a full demo export and try re-importing it elsewhere.
- Weigh the cost of leaving as much as the cost of joining.
Obscura Flow owns the catalog-and-preservation scope, local-first, with exports in the clear (flat CSV, LIDO 1.1, CIDOC CRM) — designed to interoperate with an institutional DAM rather than claim to replace one.