Skip to main content
Categorized Fields are simplified views derived from Structured Data. For full detail including term durations, conditions, and calculated date explanations, see the Dates structured data page.

Overview

Categorized Dates flatten the complex date structures in a contract into unique combinations of assets, dates, and territories. This creates clear reversion date records that are easy to track and export.
Categorized Dates currently ONLY calculates reversion dates for Spotify only. Support for additional platforms is coming soon.

What Gets Categorized

Each categorized date record represents a unique combination of:
FieldDescription
Composition IDsLinked compositions (if applicable)
Recording IDsLinked recordings (if applicable)
DateThe reversion/end date (YYYY-MM-DD format)
TerritoriesISO territory codes where this date applies

How Dates Are Categorized

The categorization process:
  1. Takes all calculated end dates from the structured data
  2. Incorporates control area territories
  3. Uses release dates from linked recordings/compositions
  4. Creates unique records for each asset + date + territory combination

Asset-Specific Dates

When contracts have per-asset terms (e.g., “rights revert 5 years after release”), the categorized view creates separate records for each asset:
RecordingDateTerritories
Track A2028-03-15US, CA
Track B2028-07-22US, CA
Track C2029-01-10US, CA

Territory-Specific Dates

When rights expire at different times in different territories:
RecordingDateTerritories
Album X2028-01-01US
Album X2030-01-01GB, DE, FR
Album X2032-01-01JP

Example

A contract with:
  • 5-year term from release date
  • 2 recordings released on different dates
  • Worldwide rights
Would be categorized as:
Recording IDsDateTerritories
rec_0012028-06-15World
rec_0022029-02-20World
The categorized view shows the computed reversion dates. For the underlying term durations, conditions, and calculation logic, see the full Structured Data.