INDUSTRY FIELD GUIDE
Record release and master version data for AI
A compilation, a single and a remaster can reuse a title while referring to different recordings or products.
NAICS 512250 · Record Production and Distribution
A compilation, a single and a remaster can reuse a title while referring to different recordings or products. DDEX release delivery standards provide a model for release and resource metadata. A label can build a small fictional version-matching benchmark before discussing any audio. DDEX release delivery · U.S. Copyright Office recording context
Invent three releases and two recording identifiers. Let one release reuse the same recording and give another a verified revision. Ask which edition the metadata supports and which license or source record remains missing. Keep a release-level term separate from track-level permission. Use no valid commercial identifiers.
Keep actual recordings, contract terms, royalties, unreleased music, artwork and artist information private. Verify rights for underlying compositions, performances, recording and artwork separately.
Describe a release version sample
Original Fiund exercise
A new release can reuse an old recording or introduce a new master
Three invented releases and two nonvalid recording IDs separate product metadata from resource identity. No actual music, artist, artwork or commercial identifier is used.
| Record | Source | What it records |
|---|---|---|
| RM1 | Practice release catalog | Single R1 and compilation R2 both reference recording M1. Remaster release R3 references M2. |
| RM2 | Verified lineage note | M2 is a separately identified revised master derived from M1. No assertion that M1's grants automatically cover M2. |
| RM3 | Permission register | R2 packaging grant covers its original layout; M1 has U permission. M2 U source record absent. |
Question for the model
Which releases reuse the same recording, and does R2's packaging or M1's permission establish U support for the remaster?
Show the reference answer and checks
RM1 shows R1 and R2 both using M1, so those release records do not establish two different recordings. R3 uses the separately identified M2 revision under RM2. RM3 supports M1 for U and a distinct R2 packaging scope, but supplies no M2 U grant. Neither a shared title nor derivation from M1 automatically fills that missing record under the exercise terms.
- Counting every release as a distinct recording despite shared resource IDs.
- Using release artwork or packaging permission as track-level master permission.
Fields to preserve
- Release-to-recording reference
- Separates products from their reused audio resource.
- Master revision lineage
- Identifies the changed resource without collapsing it into the original.
- Release-level and track-level grants
- Keeps different permission subjects explicit.
Test another case
Add a fourth release with an unchanged M2 reference but new artwork. Ask the model to identify which resource changed and which did not.
Use fabricated catalog records and original text. Exclude recordings, royalties, unreleased tracks, artist information, artwork and actual contracts.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.