Short answer
A DAM for media and publishing must ingest wire and staff content at speed, keep rights metadata intact across millions of archive assets and feed editorial and syndication systems. DAMSelection assessment: weight rights and licence management, search and ingestion at 40 percent or more of the total score when the archive exceeds one million assets or syndication earns revenue.
Asset types in media and publishing
A media and publishing DAM holds editorial photography, video, audio, page output and archive scans, and each item carries its own licence terms. News publishers, magazine groups, book publishers and broadcasters share the pattern, with different speed and archive needs.
Typical asset families:
- Editorial photography: staff, freelance, agency and wire images, each with a different licence.
- Video and audio: raw footage, edited packages, podcasts and clips for social channels.
- Page and product output: page PDFs, e-book files, covers and print-ready layouts.
- Archive: digitised photographs, negatives, historic pages and scanned illustrations.
- Graphics: illustrations, infographics, maps and data visualisations.
- Synthetic content: AI-generated or AI-edited images, which need a clear source label.
Archive scale changes the cost model. Worked example: 3,000,000 images at an average of 15 MB need 45 TB of storage before renditions and video. DAMSelection assessment: storage, egress and AI credit consumption drive five-year DAM cost more than licence fees, and an archive makes that visible. Run your own figures through the TCO Calculator.
Rights, metadata standards and regulation
Rights metadata is the core requirement in media and publishing, and the IPTC Photo Metadata Standard is the common language for it. A DAM must read, store, edit and write these fields back into files on export.
Fact: the IPTC Photo Metadata Standard 2025.1 (revision dated 26 November 2025) includes these rights-related properties:
| IPTC property | What it records | DAM requirement |
|---|---|---|
| Copyright Notice | The copyright statement | Preserved on every rendition |
| Credit Line | The credit to display with the image | Shown in the editorial system at pick-up |
| Licensor | Who licenses the image | Linked to the licence record |
| Model Release Status and Property Release Status | Whether releases exist | Blocks commercial use without a release |
| Web Statement of Rights | URL of the rights statement | Written into exported files |
| Data Mining | Data mining prohibition or permission, optionally with constraints | Set per collection and written on export |
| Digital Source Type | The type of source of the digital image | Separates camera, edited and synthetic images |
Fact: Directive (EU) 2019/790 on copyright in the Digital Single Market sets two rules that touch publisher DAMs. Article 4(3) lets rightholders reserve text and data mining, by machine-readable means for content made publicly available online. Article 15 gives press publishers rights for online use of their press publications by information society service providers, and Article 15(4) ends those rights two years after publication.
Provenance metadata is a growing requirement. The Coalition for Content Provenance and Authenticity (C2PA) publishes technical standards for certifying the source and history of media content. Read the Content Credentials and C2PA guide and the EU AI Act guide for generated assets before you set requirements.
Fit criteria and weights
Media and publishing buyers should weight rights, search and ingestion highest, followed by API depth for editorial systems. The table uses the twelve DAMSelection scoring criteria.
| Criterion | Weight (DAMSelection assessment) | What to look for |
|---|---|---|
| Rights and licence management | 15 | Licence records, territory and time limits, embargoes, usage counts |
| Search and AI discovery | 14 | Sub-second search over millions of assets, visual similarity, face grouping |
| Asset ingestion and processing | 12 | Wire feed ingest, IPTC mapping, video proxies |
| Metadata and taxonomy flexibility | 12 | IPTC and XMP mapping, controlled vocabularies, subject codes |
| Distribution and CDN | 10 | Syndication packages, partner feeds, metadata kept on export |
| API and extensibility | 10 | Editorial CMS, print layout and planning integrations |
| Creative tool integration | 7 | Layout and video editing handover |
| Workflow and approvals | 6 | Picture desk selection and legal check |
| Security, hosting and compliance | 5 | Access control for embargoed and sensitive material |
| Administration and total cost profile | 5 | Storage and egress pricing at archive scale |
| Brand portal and sharing | 3 | Press and partner sharing |
| PIM integration depth | 1 | Relevant for book metadata in some publishers |
| Total | 100 |
Score candidates with the scoring matrix, and compare with other industries in DAM by industry. The candidate table on this page lists platforms from the enterprise content platforms and European specialists segments, and the media and publishing shortlist adds scored scenarios.
Scenarios to script
Media and publishing demos should test ingest speed, rights enforcement and syndication on your own content. DAMSelection assessment: ask each vendor to load your sample set before the demo, because archive search quality only shows on real metadata. Generate the scripts in the Demo Script Generator.
Scenario 1: Wire ingest burst
Send 5,000 images with embedded IPTC metadata in one hour, from two wire feeds and one photographer upload. Ask the vendor to show when each batch becomes searchable, how IPTC fields map to the DAM schema and how duplicates from two agencies are grouped.
Scenario 2: Rights-restricted reuse
An editor searches the archive for a 2019 photograph for a new story. The licence allows print in the Netherlands only and expired for online use. Ask the vendor to show the restriction at search, block the online rendition and log the attempt.
Scenario 3: Syndication package with rights metadata
Build a package of 40 images and two videos for a partner publisher. Ask the vendor to embed Copyright Notice, Credit Line and Data Mining values in every exported file, keep Content Credentials intact and record which partner received which asset.
Integrations
A media and publishing DAM sits at the centre of the editorial system chain. The integration test is whether metadata survives every hand-off.
| System | What flows | Test |
|---|---|---|
| Editorial CMS | Picked images, credits, captions | Credit Line appears on the published page |
| Print layout | High-resolution files and placement data | Usage count updates after print |
| Wire and agency feeds | Incoming images with IPTC data | Ingest speed and field mapping |
| Video editing | Proxies and final packages | Round trip without metadata loss |
| Syndication platform | Packages and licences | Licence terms travel with files |
| Rights and royalty accounting | Usage records | Monthly usage export per licensor |
Check IPTC and XMP handling in every integration, and read the rights management guide for the licence data model.
Archive migration
A media archive migration is a metadata project first and a file transfer second. DAMSelection assessment: plan the cleaning of captions, credits and rights before booking transfer capacity, because legacy rights data decides what the newsroom may reuse.
- Profile the archive: count assets per source, format and decade, and sample 500 records for metadata quality.
- Map legacy fields to the new schema and to IPTC properties, including credit, licensor and restrictions.
- Classify rights per collection: owned, licensed with terms, unknown. Block reuse of the unknown class until reviewed.
- Migrate in waves, newest content first, because newsrooms reuse recent material most.
- Verify a sample per wave: file integrity, embedded metadata, search results and rendition quality.
- Keep the legacy system read-only until the last wave passes verification.
Read the migration plan guide for the full method.
Pitfalls
Media and publishing DAM projects fail most often on metadata loss and archive cost. Five pitfalls recur in DAMSelection practice:
- Renditions or CDN delivery strip embedded IPTC metadata, so credits and rights disappear downstream.
- Archive migration is planned by file count, without time for cleaning legacy captions and rights.
- Per-asset or storage-tier pricing is accepted at today's volume and breaks when the archive is digitised.
- Face recognition runs on staff and public photos without a GDPR assessment. Biometric data used to identify a person is a special category under Article 9.
- AI-generated images enter the archive without a Digital Source Type value, so editors cannot filter them.
Candidate vendors
| Vendor | Segment | Industry fit score |
|---|---|---|
| Adobe AEM Assets | Enterprise content platforms | Scoring pending |
| Aprimo | Enterprise content platforms | Scoring pending |
| OpenText | Enterprise content platforms | Scoring pending |
| Orange Logic | Enterprise content platforms | Scoring pending |
| Sitecore Content Hub | Enterprise content platforms | Scoring pending |
| Hyland Nuxeo | Enterprise content platforms | Scoring pending |
Case pattern
Pending An anonymised selection pattern from a PIMvendors engagement in this industry publishes here after client approval.
Frequently asked
What is the best DAM for a newspaper archive?
The best DAM for a newspaper archive combines fast search over millions of assets, full IPTC support, rights records per image and storage pricing that holds at archive scale. Test candidates on a sample of your own archive. The [media and publishing shortlist](/dam/vendors/shortlists/media-publishing/) lists candidates with scored scenarios.
Does a publishing DAM need IPTC support?
A publishing DAM needs full IPTC Photo Metadata support, both reading embedded fields at ingest and writing them back into exported files. Without write-back, credits and rights restrictions disappear when images leave the DAM for partners and channels.
How do I reserve text and data mining rights in a DAM?
A DAM can record a data mining reservation per asset or collection with the IPTC Data Mining property and write it into exported files. Article 4(3) of Directive (EU) 2019/790 accepts machine-readable reservation for content made publicly available online. Legal sets the policy and the DAM applies it.
How much storage does a media archive need?
Storage depends on asset count, file size and video share. Worked example: 3,000,000 images at 15 MB need 45 TB, and video adds far more per asset. Model storage and egress for five years before comparing licence quotes.
Should a publisher run DAM and editorial CMS as one system?
A publisher can run one system when the editorial CMS includes adequate asset management, but archive scale, licence records and syndication usually justify a separate DAM. DAMSelection assessment: decide on the metadata model first, then choose the architecture.