Key takeaway
A recording identifier and a musical-work identifier describe different assets. Keep their relationship and ownership evidence separate instead of inferring either from a shared title or code.
One work can have more than one recording
A music archive owner sees a studio recording and a live recording with the same song title. A title-based export merges them into one asset. Another export creates a new musical work for every distribution copy. Both transformations can lose the relationship a catalog reviewer actually needs.
The International ISRC Agency explains that ISRC identifies sound recordings and music videos, not compositions, products or performers. The ISWC agency describes a different referent: the musical work, rather than a recording, performance or other manifestation. The owner should identify which entity each record describes before deciding how to connect it.
This is not a guide to assigning registered codes or deciding who owns a catalog. It is a completed identity-map example that preserves the distinction needed for those later questions.
Build a typed graph from stated source mappings
The hypothetical example uses symbolic aliases, not invented registered ISRCs or ISWCs. Work W1 has studio recording R1 and live recording R2. Distribution file D1 is stipulated by the fictional source mapping to be a copy representing R1. No acoustic comparison or registry lookup was performed.
The graph contains one work, two recording identities and a separate distribution-file node. The relationship from R1 to W1 does not make them the same asset. The relationship from D1 to R1 does not create a third recording under the stated premise.
A completed export keeps these node types and links. If the archive has only a shared title, the work-recording link remains unsupported rather than being filled from the title. The example supplies that mapping as a premise; an actual owner must retain the evidence that established it.
| Symbolic node | Entity type | Stated fictional relationship | Completed export treatment |
|---|---|---|---|
| W1 | Musical work | Related to recordings R1 and R2 | One work node; preserve its work-identifier field |
| R1 | Studio sound recording | Records W1 | Separate recording identity and recording-identifier field |
| R2 | Live sound recording | Records W1 | Distinct from R1 despite shared work |
| D1 | Distribution file | Source mapping says it represents R1 | Link to R1; do not invent a new work or recording |
Change the owner without changing the recording identity
Now extend the hypothetical history: a supported ownership record for R1 changes from owner alias O1 to O2. The recording already has an assigned ISRC. IFPI’s ownership explanation says that a change of ownership does not change that assigned code. Identity can remain fixed while the separate owner record changes.
The same agency warns against inferring rights status from elements of the ISRC. A code prefix should not populate a current-owner field, establish a license or settle whether a proposed recipient may use the recording. Retain the actual ownership and grant evidence with its scope and dates.
The completed mapping therefore changes the owner-history relation, not the recording node or its assigned identifier. This is a representation decision under the stipulated source history, not a finding that a real transfer occurred or covered every right in the music.
Do not ask a work code to carry ownership shares
The ISWC agency’s explanation distinguishes the work’s identity from information it does not encode, including ownership shares. It also distinguishes the musical work from its recordings and other manifestations. An exact, well-preserved identifier can therefore still be inadequate for a royalty or proposed-use decision.
Preserve the identifier as supplied, its source and the entity type it identifies. Put work-recording associations, current ownership assertions and proposed-use grants in separate relationships with their supporting evidence. Correcting a mistaken association should not silently rewrite the source declaration or manufacture a grant.
The fictional W1–R1–R2 graph deliberately stops before royalty allocation. It gives a reviewer the assets to which an actual question refers; it does not state shares, payments, territorial rights or a permission outcome.
Name the asset in the proposed evaluation
The owner can now distinguish a question about two performances of W1 from a question about duplicate distribution files representing R1. That distinction changes the records a reviewer needs without requiring title-based guesses or treating a code as proof of ownership.
The completed artifact is a typed relationship map with explicit source premises: one work, two recordings, one linked copy and a separately changing ownership history. It can accompany approved metadata about a catalog category. Access to the recordings, actual work associations and any external reuse still require their own evidence and authorization.