Metadata Is Your New Defense

Metadata is the information that travels with your music: titles, versions, credits, identifiers, and release details. It helps the people and systems handling a release understand what they have received.

When those records disagree, even a carefully produced track can arrive with confusing credits, the wrong version label, or information that needs correcting after launch.

Calling metadata your new defense does not mean a spreadsheet proves ownership or guarantees payment. It means reliable records make it easier to identify your work, explain what was delivered, and investigate a mistake.

1. Give every recording a clear identity

Start with the exact track title, version description, approved audio file, and ISRC. Keep those details together so the person handling delivery can match the identifier to the correct recording.

IFPI explains that an assigned ISRC stays with a recording, including through ownership changes. A remaster generally retains its code unless significant new creative input justifies a new one. Source: IFPI’s ISRC guidance.

Our recommendation is to compare the actual audio with the catalog entry before approval. A perfectly formatted identifier attached to the wrong export still creates a problem.

Use filenames that make versions distinguishable. Keep superseded files in a clearly marked archive so an older master cannot quietly become the next delivery.

2. Connect the composition information

The recording and the underlying musical work need connected records.

An ISWC identifies the musical work, independently of a particular recording. It does not serve as a record of everyone’s ownership percentage. Source: ISWC International Agency.

Keep writer names, publisher information, relevant identifiers, and agreed shares alongside the work record. Store signed agreements as supporting documents.

When information is pending, label it pending and assign a follow-up. A blank field is a reason to investigate. It is never a reason to invent an identifier or assume a collaborator’s share.

3. Make contributor review part of metadata approval

Before delivery, send collaborators the exact credits you intend to submit.

Ask them to review their name, role, and the relevant track. A short request focused on their contribution is easier to answer than an invitation to inspect an entire release folder.

Agree on public spellings and artist names. Keep any legal names or private administrative details in the appropriate internal records.

G.U.M.M.’s recommended review includes:

• Primary and featured artist names.
• Songwriter and producer credits.
• Performer roles where supported.
• Track titles and version labels.
• The approved spelling of each public credit.

Record who approved the information and when. That gives the team a reference if a question appears months later.

4. Understand the delivery chain

DDEX’s Electronic Release Notification standard supports the exchange of release and resource metadata, together with information about when, where, and how music may be made available. Source: DDEX’s ERN overview.

A shared standard does not mean every distributor exposes every possible field or every service displays all supplied information.

Ask your delivery partner how it handles specialized credits, corrections, and any required declarations. Save an export or dated copy of the submitted information.

For a correction, record the original value, the replacement, the affected services, and the support reference. Keep the item open until the result is checked.

5. Compare the live release with the approved record

Launch day is the moment to inspect what listeners actually receive.

Listen to the recording. Check the artist profile, track order, visible credits, artwork, and version labels. Compare the live page with the information your team approved.

If something is wrong, collect the release URL and describe the exact mismatch. A specific correction request is easier to investigate than a general statement that the metadata is broken.

Maintain one catalog register with a clear owner and dated revisions. Keep a backup that can be opened independently of the original service.

Start with your current release, then work backward through the catalog. Consistent metadata becomes useful through maintenance: review it, deliver it, verify it, and update it when the facts change.

Related reading: ISRC / ISWC: What Actually Matters · DSP Declarations & Delivery Changes