Metadata Best Practices

Good metadata answers four practical questions: What is this release? Which recording is on it? Who created and controls the underlying works? Where should each use, credit, and payment be matched? Treat metadata as a connected record rather than a form you complete once. Keep the same facts consistent across your distributor, collaborators, composition registrations, recording registries, and catalog files—but keep compositions, recordings, and releases distinct.

This guide explains the main fields, how identifiers work, how to handle versions, and how to audit a release before delivery. It is educational information, not individualized legal or royalty advice. Some practices are global industry guidance; references to The MLC, SoundExchange, the U.S. Copyright Office, and 37 CFR 210.27 are U.S.-specific. Requirements can also differ by distributor, DSP, territory, and delivery profile.

Start with the three-layer model

A song can involve at least three records:

1. The composition: the musical work—the underlying song, generally associated with writers and publishers.
2. The sound recording: a particular recorded performance or production of that composition, associated with performers, producers, and recording rights holders.
3. The release or product: an album, EP, single, or other package containing one or more recordings.

These layers are related, but they are not interchangeable. The U.S. Copyright Office distinguishes musical compositions from sound recordings and describes different typical authorship categories for each. Musical Compositions and Sound Recordings explains that distinction. If you copy a recording-level identifier into a composition record, or treat an album identifier as though it identifies the audio itself, matching can fail.

A useful working map is:

Composition record → writers, writer roles, publishers or administrators, ownership shares, work title, and composition identifiers where applicable.

Recording record → main artist, recording title, version, duration, recording owner, producer, performers or other credits, ISRC, and recording-specific dates or notes.

Release record → release title, display artists, label, distributor, release date, territory or localization data, UPC/EAN or another product identifier, cover asset, track sequence, parental-content status, genre, and links to the recording records.

The exact fields exposed by a distributor may have different names, but the underlying questions remain the same.

Know what each identifier identifies

An ISRC identifies an individual sound recording or music video. It does not identify the underlying composition and does not identify the release product. The International Standard Recording Code handbook and the International ISRC Registration Authority’s usage guidance describe that scope. International Standard Recording Code (ISRC) Handbook, 4th Edition and Using ISRC are the primary references.

For each ISRC, retain enough reference information that another system can recognize the recording. IFPI’s minimum reference-data guidance includes the main artist, track title, version or alternative title, duration, content type, and publication date. Using ISRC identifies these fields. In practice, also keep the source audio or delivery file, the credited recording owner, the release or releases in which the recording appears, and a change history in your internal catalog.

The same recording should normally keep its existing ISRC when it is reused across formats, releases, territories, or an unchanged compilation. A format, bit-rate, territory, or package change does not by itself turn the audio into a new recording. The ISRC handbook describes retention for the same recording across formats and compilations. International Standard Recording Code (ISRC) Handbook, 4th Edition sets out that principle.

A new ISRC is required when the recording itself is distinct or materially changed. The handbook identifies live versions, different takes, edited versions, remixes, extended versions, and materially changed recordings as examples. Materially creative remastering may also require a new code, while routine remastering and ordinary format or bit-rate changes may retain the existing one. Apply the specific IFPI rules to the recording in question; do not decide from the marketing name alone. International Standard Recording Code (ISRC) Handbook, 4th Edition provides the detailed cases.

A UPC/EAN is a release or product identifier, not a substitute for an ISRC. U.S. blanket-license reporting rules list UPCs alongside recording and musical-work fields, which illustrates that product and recording identifiers serve different matching purposes. The same rule also warns us not to treat one statutory reporting list as a universal distributor checklist. 37 CFR § 210.27: Reports of usage and payment for the blanket license is the relevant U.S. source. For allocation, reuse, or other product-identifier decisions, follow your distributor’s current instructions, applicable product-identification guidance, and the recipient platform’s specifications.

Build the release record carefully

Release metadata is the information a store or DSP uses to present a product and connect it to its component resources. DDEX’s Electronic Release Notification guidance models releases and resources with structured fields for artist roles, titles, explicit status, genre, sequence, cover images, and relationships between a release and its resources. Electronic Release Notification Message Suite: Rules for Releases and Resources describes these structures.

Start with the official release title. Enter the title exactly as the official title, then place subtitle or version information in the appropriate field or format supported by the recipient. DDEX distinguishes official titles from additional or informal titles and requires the official title in ERN. Communicating Titles in ERN and MEAD explains the distinction.

Do not use title text to carry every fact. A track called “Song (Live)” should correspond to a genuinely live recording, and a title such as “Song (Remix)” should correspond to the correct remix recording and ISRC. If a distributor provides a version field, use it consistently. If it does not, follow that distributor’s formatting instructions rather than inventing punctuation, brackets, or extra descriptors.

Enter display artists in their actual roles. DDEX separates main artists from additional artist roles and supports sequenced display artists. Electronic Release Notification Message Suite: Rules for Releases and Resources provides the industry-standard model. Confirm spelling, capitalization, featured-artist treatment, and artist identity with the people involved before delivery. Avoid adding a person as an artist merely to force a credit into a storefront field.

Sequence matters. Track numbers, disc numbers, and the relationship between release and resource records should agree. A release-level track list that differs from the audio files, embedded metadata, lyric or credit files, or distributor spreadsheet creates opportunities for mismatches. DDEX guidance includes release/resource sequencing and relationships; use that structure as a checklist even if your distributor presents only a simple upload form. Electronic Release Notification Message Suite: Rules for Releases and Resources supports this approach.

Classify clean or explicit content honestly and consistently. Genre should describe the release or recording using the available controlled choices. Cover images and other linked assets should be attached to the correct release and meet the recipient’s quality and formatting requirements. A standard field may exist even when a particular DSP displays it differently or does not require it in every case.

Apple’s provider guidance highlights artist accuracy and formatting, localization, clean or explicit classification, and asset quality as critical delivery considerations. It also warns that misleading or rights-problematic content may be rejected. Apple Music Guidelines is Apple-specific, so treat it as a delivery example rather than a universal rule for every DSP.

Record rights and matching information separately

For the composition record, capture each writer’s correct name and role, the relevant publisher or administrator, and the agreed ownership or collection shares. Search before creating a new work record when the relevant system offers duplicate prevention. The MLC’s registration workflow describes searching for an existing work, entering writers and roles, adding publishers or administrators, and recording collection shares. It also allows optional recording information that can support automated matching. How to Register Works in the MLC Portal is the U.S.-specific reference.

The recording record should identify the particular audio, not merely the composition title. Link the ISRC, main artist, recording title, version, duration, release date or publication date, recording owner, producer, label, distributor, and the release or releases where the recording appears. Keep writer and publisher data linked to the composition record rather than assuming that the recording’s performer is the composition’s writer or publisher.

For U.S. blanket-license reporting, 37 CFR 210.27 identifies matching information that can include sound-recording owners, producers, ISRCs, UPCs, versions, dates, album titles, labels, distributors, songwriters, publishers, identifiers, and ownership shares. 37 CFR § 210.27: Reports of usage and payment for the blanket license lists these fields in a specific statutory reporting context. It is not a universal checklist for every platform, and it does not decide who owns a work or recording. Its practical lesson is that consistent, connected metadata makes reporting and matching more reliable.

SoundExchange provides registration, recording search and claim tools, catalog management, ISRC search, and the Music Data Exchange for sound-recording and publishing data and ownership claims. Register describes those functions. Registration or claiming is not a determination of ownership: enter accurate rights information, retain the agreements and source records that support your entries, and resolve disagreements through the appropriate parties and processes.

A pre-release audit you can repeat

Run the audit from the source of truth, not from memory. One person can gather the data, but the artist, producer, writers, publisher or administrator, label, and distributor should have a chance to confirm the fields relevant to them.

First, create one release sheet. Record the official release title, display artist order, release date, label, distributor, product identifier, genre, clean or explicit status, territory or localization data, cover asset, and complete sequence.

Second, create one row per recording. Include the final approved audio filename, recording title, version, duration, main artist, additional artists, ISRC, recording owner, producer, associated release, and any notes explaining whether it is the original, live, edited, remixed, extended, or remastered version.

Third, create one row per composition. Include the work title, every writer, each writer’s role, publisher or administrator, shares, and identifiers or registration references that your relevant system uses. Search for an existing work before adding a duplicate where the workflow supports it. The MLC’s instructions make this search-and-confirm step part of registration. How to Register Works in the MLC Portal

Fourth, reconcile the links. Every release track should point to exactly the intended recording. Every recording should point to the intended composition or compositions. The ISRC should match the final audio and remain stable wherever the same recording is reused. The product identifier should remain attached to the release record. Names, titles, versions, dates, and ownership shares should agree across your internal sheet and the delivery form.

Fifth, check presentation and delivery. Review artist formatting, title and version placement, sequence, genre, localization, explicit status, cover quality, and asset association. Apple’s guidance makes these concrete delivery checks and notes that misleading or rights-problematic material may be rejected. Apple Music Guidelines

Finally, save evidence of the submission. Keep the final metadata export, approved audio references, identifier list, artwork version, confirmation messages, and a change log. If a platform later displays the wrong version or misses a credit, you can compare the submitted record with the current catalog record instead of reconstructing the release from memory.

Worked example: one song, three products

Suppose a studio recording appears first as a single, later on an EP, and later in an unchanged compilation. The recording row keeps the same title, duration, final audio, and ISRC because the audio is the same. Each release row has its own release-level information, including its own title, sequence, cover asset, date, and product identifier. The ISRC connects all three products to the same recording; it does not turn the three releases into one product.

Now suppose the artist publishes a live performance, an edited radio version, and a remix. Each is a distinct recording scenario. The live, edited, remixed, or otherwise materially changed audio should be reviewed under the IFPI new-code rules, and a new ISRC may be required for each distinct recording. The version field and title should clearly identify the intended version, while the release metadata links each version to the correct resource. International Standard Recording Code (ISRC) Handbook, 4th Edition

If the composition has two writers and one publisher administrator, record those parties and their shares on the composition side. If the recording has a different owner, producer, or label, record those facts on the recording or release side. The composition and recording can share a familiar song title while still representing different rights records. That separation is the foundation for better matching.

Maintain the catalog after release

Metadata work continues after delivery. When a credit, ownership share, publisher relationship, title, version, label, or release association changes, update the authoritative catalog and then propagate the approved change through the relevant systems. Do not casually create a second ISRC because a release moved territories or appeared in a new package; first determine whether the recording changed. Conversely, do not retain an old ISRC when the audio is a genuinely new live, edited, remixed, extended, different-take, or materially changed recording.

Periodically search the relevant MLC and SoundExchange tools for unmatched or duplicate records, review claims and catalog entries, and compare platform displays with your submitted metadata. These services provide matching and catalog-management functions, but their interfaces and workflows can change. The MLC guidance and SoundExchange registration page were checked on 2026-08-07; verify current instructions before acting. Register How to Register Works in the MLC Portal

The simplest durable rule is: name the work accurately, identify the exact recording, identify the release package, preserve identifiers when the underlying object is unchanged, create new identifiers when the recording materially changes, and keep the people, companies, dates, shares, and relationships synchronized. Good metadata cannot resolve a disputed ownership question by itself, but it gives the systems and collaborators handling the music a much better chance of matching the right record to the right people.