Classical music metadata: prepare composers, works, movements and performers

Build the programme before entering the release

Start from the music actually recorded, the approved running order and a reliable programme or score reference. Identify whether a track contains a complete piece, a movement or an excerpt. A short filename such as “Adagio final” is not enough to distinguish works or versions when several recordings are being prepared.

Give the project one current repertoire sheet. The person reviewing the music should be able to check every audio file against one row. Keep unresolved catalogue numbers, spellings or arrangement details visibly unresolved until they are checked; do not fill a gap with a plausible-looking value.

Use one row for each recorded track

• The final track number, audio filename and precise performance or session reference.
• The work title, composer identity and the source used to verify them.
• Any relevant catalogue or opus reference, key and movement or selection information.
• The actual performers, ensemble, soloist and conductor where relevant.
• The arrangement, transcription, language or edition information that applies to this performance.
• Existing recording identifiers and original release history where the same master has been released before.
• The reviewer, the approved metadata version and any remaining question.

This is a preparation sheet, not a promise that the portal has a separate field for every item. A work-level reference describes the composition; an ISRC describes the recording. Keep the source of each identifier with its entry and use the recording-identifier guide when the catalogue is moving.

Check the destination’s classical conventions

Apple’s classical guidance distinguishes composer from performing artist, calls for consistent complete work and movement titles, and has specific conventions for catalogue references and excerpts. Its Classical rules are not identical to its Classical Crossover rules. Spotify’s public metadata help also asks for appropriate roles at both release and track level, including conductors and orchestras where relevant.

Use the actual programme and destination requirements to decide the entries. Do not apply a pop featured-artist shortcut to every classical performer or assume an ensemble name replaces every contributor question. The artist-role guide explains the wider billing record; your classical programme still needs its own review.

Review the work-to-track relationship

Check that the titles and order make sense together. If the programme contains only one movement of a larger work, record that scope rather than describing the whole work as complete. If several movements are recorded, confirm that every row refers to the intended composition and version. Avoid silently mixing a translated title, another edition’s numbering and a different recording’s subtitle.

Apple has separate requirements for grouping complete works. That does not establish an automatic DistroBolt work-grouping control or guarantee how every listener app presents the release. Ask about the supported handling before treating a private spreadsheet group as a delivered platform feature.

A practical programme example

A hypothetical chamber ensemble records a three-movement suite and a separate encore. Its worksheet gives each movement a row, connects the first three rows to the same verified work, and records the encore separately. The team checks the same player names and session reference against the approved files. If only the middle movement is later selected for a single, the new release record identifies that selection accurately rather than claiming the entire suite is present.

This example illustrates organisation, not a catalogue entry for a real composer or a guarantee that a particular grouping will be accepted. It does not establish rights to a score, arrangement or recording.

Keep repertoire rights alongside the metadata

Classical is a musical category, not a blanket rights status. Establish authority for the exact recording and any protected material used. An old composition, a recent arrangement and your newly recorded performance can raise separate questions. Use the public-domain preparation guide if the proposed basis is that protection has expired, rather than assuming age or genre clears the project.

For a live programme, retain the relevant performer and recording arrangements using the live-recording checklist. Credit accuracy, payment allocation and permission are related records, not interchangeable evidence.

Ask a specific question before delivery

Prepare the release through the verified New Release → Audio Release entry route in the approved account. Before submitting, ask DistroBolt about any unclear composer, ensemble, work, movement or excerpt handling in the actual release. Share the relevant track list and question; do not assume that every platform-specific field appears in the current portal.

After delivery, compare the public track list and artist identity with the approved record. If something differs, give the exact link, current display and intended correction using the metadata correction workflow. No particular processing time, classical-app placement or presentation outcome is guaranteed.