Build one accurate metadata sheet for a metal release

Start with separate work and recording entries

Give every composition a work title and every recorded version a recording title. They may match, but keep them as distinct entries: one song can have several recordings, edits, or releases. Include a stable internal reference for each entry so a title change or alternate mix does not break the link.

For example, a band might list the composition “Ash Circuit” as W-014, then connect it to the album version R-021 and a shorter edit R-022. The internal codes are organizational labels, not official identifiers.

Record contributors and roles precisely

List each credited person or organization with the spelling they have approved, plus the role relevant to that entry. Composition contributors belong with the work; performers, engineers, producers, and other recording credits belong with the recording. If a person has more than one role, record each one clearly rather than compressing them into a vague credit.

Use a dedicated field for names and another for roles. A note such as “M. Lee—guitar on track 3” is more useful than an unexplained name in a general comments column. Preserve agreed credit wording where the distinction matters.

Add identifiers and source records

Include identifiers only when assigned, and label what each one identifies. A work identifier, recording identifier, and release product identifier are not interchangeable. Leave a field blank or mark it “not assigned” instead of inventing a number. Record who supplied or issued an identifier and when it was checked.

Add a source-document field for each important claim: approved credit email, signed agreement, session sheet, distributor delivery record, or final track list. If a name differs between documents, note the conflict and who is resolving it.

Make the sheet usable at handoff

A practical sheet also names the release, track number, version, status, and last-updated date. For a release with several tracks, filter by track or recording code and compare the sheet with the audio filenames and delivery form. If track three is “Ash Circuit (Edit)” in the master folder but “Ash Circuit” in the delivery form, resolve that mismatch before submission.

Keep one controlled current copy, limit editing to designated collaborators, and save a dated export with the release package. The sheet is useful when another person can trace a credit or identifier back to its source without guessing.

List contributor names, roles and agreed credits

A band can maintain a private lyric document for checking without putting the words in a public release note or article. Identify each document by composition title, recording version, and date, and limit access to the people who need to verify it. The private working record helps resolve track associations; it does not determine what a distributor will accept for public display.

For an album with a standard track and an instrumental version, record clearly which version has lyrics and which does not. That prevents words from being attached to an instrumental recording simply because the titles are similar.

Compare each lyric record with the approved track list and composition credits. Check spelling of the title, whether the recording is an edit or alternate version, and who has confirmed the association. If a track was renamed during production, retain a note linking the earlier working title to the final title.

Use a checklist with track number, final title, version, internal document reference, and verification status. A reviewer can confirm that the correct record is linked without copying the lyric text into the checklist itself.

Delivery services differ in what they accept, where information appears, and whether a particular release or territory supports a field. Read the distributor’s current instructions at the time of submission. Submit only through the method it specifies, and do not assume that a public-facing lyrics field is required or available for every release.

If a form asks for information the band does not have permission to provide, or its requirements are unclear, ask the distributor for guidance before sending it. Keep a copy of the submitted metadata and note the date, so the band can compare the delivery record with what was approved internally.

The final package can include a track-to-document index without embedding lyric text. For example, it can say “Track 2—‘Iron Orchard’—album version—lyric file L-02 verified by writer on 14 May.” Store the source document separately with appropriate access controls. This makes the association auditable while avoiding unnecessary reproduction.

Before delivery, compare the index against the final audio names and track order, then record any service-specific choices. The goal is accurate linkage and a clear trail of approval, with public submission governed by the distributor’s current rules.

Attach identifiers to the entity they identify

Keep the recording version beside its identifier

The sheet distinguishes the musical work from each recording and release edition. These internal examples are fictional and are not registered identifiers. Download the blank metadata CSV from the listening notebook and replace the examples with approved release information.

Sources and the limits of this exercise

The references below support the named research method, instrument explanation or release process. The worked exercise in this guide is our own example; it is not a quotation, a recovered interview, a real concert observation or an analysis of an unidentified recording. ^[1]