Reference Glossary
News wire metadata
News wire metadata is the structured data — credit line, source, caption, Media Topic codes, urgency — carried with a wire-distributed photo or story, standardized largely through IPTC's NewsML-G2 format.
Why it matters in a DAM
Wire images ingested from services like AP or Reuters arrive with embedded IPTC fields (Credit, Source, Copyright Notice, Caption) that a DAM has to preserve on ingest rather than strip, because the Credit and Source fields are usually contractually required to display alongside the photo under the wire service's distribution terms — losing them during an automated resize or watermarking pass breaks the licensing condition even though the image itself looks unchanged to the eye.
A worked example
Common mistake
A DAM's automated derivative pipeline (resize, watermark, format conversion) regenerates the image file without preserving the embedded IPTC/XMP block, so the required wire credit line silently disappears from every resized derivative even though the master file still carries it correctly.
Wire services distribute news photos, text, and video with a layer of structured metadata attached, historically carried in the IPTC Information Interchange Model and increasingly wrapped in NewsML-G2, IPTC’s XML-based exchange standard for text, images, video, and audio. That metadata isn’t decorative — the Credit and Source fields typically identify the wire service and photographer in the exact form the distribution agreement requires a publisher to display, the Media Topic codes classify the story by subject for routing and search, and urgency flags how time-sensitive the item is for editorial triage.
- Credit — the wire service and photographer, in the exact form the license requires
- Source — the party currently supplying the item in the distribution chain
- Copyright Notice — rights holder and usage terms
- Media Topic — subject classification for routing and search
- Urgency — editorial triage signal for how time-sensitive the item is
The practical failure point in a DAM is derivative generation. A wire photo’s embedded IPTC block travels with the original file, but many image-processing pipelines — resizing for a responsive web layout, adding a watermark, converting to a different format — regenerate the file without carrying that metadata block forward, especially when the tooling wasn’t built with news workflows in mind. The result is a derivative that looks fine and publishes fine, but silently drops the required credit line, which is a breach of the distribution agreement even though nothing about the visible image changed. A DAM handling wire content needs its transformation pipeline explicitly tested to confirm IPTC/XMP metadata survives every derivative it generates, not just the original upload.
Frequently asked
What's the difference between NewsML-G2 and the IPTC Photo Metadata Standard?
NewsML-G2 is the wrapper format for exchanging any kind of news item (text, photo, video, audio) between systems; the IPTC Photo Metadata Standard defines the specific descriptive and rights fields embedded inside an individual photo file, and IPTC publishes a mapping between the two so fields carry over correctly.
Why does a DAM need to preserve wire metadata rather than replace it with its own fields?
Because the wire service's distribution agreement typically requires the original credit and source to be displayed exactly as supplied — overwriting it with the DAM's own metadata schema can strip the attribution the license legally requires.
Does resizing or watermarking a wire photo affect its metadata?
It can, depending on the tooling — many image-processing libraries don't preserve embedded IPTC/XMP metadata by default when generating a new file, so a DAM needs to explicitly verify metadata survives every derivative it creates from wire content.
What does the IPTC urgency field actually control?
It's an editorial triage signal indicating how time-sensitive an item is, letting newsroom systems and editors prioritize breaking or urgent items over routine coverage when processing incoming wire content.
Are Media Topic codes the same across all wire services?
IPTC's Media Topics is a shared, promoted taxonomy that many wire services and newsrooms use for subject classification, which is what makes cross-service search and routing by topic possible in the first place.
Can wire metadata be edited after ingest?
It generally shouldn't be, at least not the Credit, Source, and Copyright Notice fields, since those reflect the terms of the distribution agreement — a DAM should treat wire-supplied rights fields as read-only for most users, distinct from locally added descriptive tags.
Sources
- NewsML-G2 is IPTC's open XML standard for exchanging news content including text, pictures, graphics, video, and audio, with strong use of controlled taxonomies like Media Topics. checked 2026-08-07 — IPTC, "NewsML-G2"
- There is a guideline for mapping metadata between NewsML-G2 and the IPTC Photo Metadata standard, where descriptive properties in the NewsML-G2 Item's Content Metadata take precedence over equivalent embedded metadata. checked 2026-08-07 — IPTC, "Using NewsML-G2"