Catalogue Events Overview

Overview

Catalogue Events allows you to retrieve constant updates for the global MassiveMusic catalogue as new and updated Standard Metadata is ingested into the MassiveMusic platform. You can then store and maintain this catalogue data within your own infrastructure for discovery and curation in your service.

In simple terms, Catalogue Events sends Standard Metadata to your service, which contains the core catalogue and availability information from licensors. Enhanced Metadata is available if it is included in your MassiveMusic deal, and adds extra track-level fields from MassiveMusic. Each metadata event type is delivered to its own HTTPS endpoint, so you should configure one endpoint for Standard Metadata and a separate endpoint for Enhanced Metadata only if it is included in your MassiveMusic deal.

Standard Metadata is delivered through Catalogue Events as content is ingested by MassiveMusic. Each event represents a snapshot of the release details at that time, and events can arrive out of sequence, so you should use the latest event to overwrite older release data. Standard Metadata includes the Artist(s), Release and Track(s), together with availability data.

Alongside Standard Metadata, you can also ingest Enhanced Metadata for tracks if it is included in your MassiveMusic deal. Enhanced Metadata is MassiveMusic provided track metadata, including up to 32 enhanced metadata fields, and is delivered through its own Catalogue Events stream after you have stored the Standard Metadata.

Metadata Event Types

When you integrate with the catalogue, you will always work with Standard Metadata and you may also work with Enhanced Metadata if it is included in your MassiveMusic deal. These metadata types serve different purposes and should be processed differently:

In practice, use Standard Metadata to create and update your catalogue records. If Enhanced Metadata is included in your MassiveMusic deal, use it to add extra information to the tracks you already store.

• Standard Metadata - delivered through Catalogue Events as Release Events. This is the licensor-provided metadata for the Artist(s), Release and Track(s), together with availability data. Ingest this first and use it as your source of truth for ongoing catalogue updates. Each event is a snapshot of the latest release state, so newer events should overwrite earlier ones. Bulk catalogue ingestion, availability, and takedown handling are all delivered as part of the Standard Metadata.
• Enhanced Metadata - available as a Catalogue Events stream if it is included in your MassiveMusic deal, after you have stored the Standard Metadata. This is MassiveMusic provided metadata for tracks, including up to 32 enhanced metadata fields. If it is included in your deal, ingest it after the Standard Metadata so you can attach the enhanced fields to your existing track records. Enhanced Metadata enriches your catalogue data, but it does not replace Standard Metadata as the source of truth for release and availability updates.

Key Differences

Functional Specifications

1. Ingest Standard Metadata first and use it to build and maintain your catalogue records.
2. Treat each Standard Metadata event as the latest snapshot of a release. Events can arrive out of sequence, so overwrite older release data when a newer event arrives.
3. Configure a dedicated HTTPS endpoint for Standard Metadata.
4. If Enhanced Metadata is included in your MassiveMusic deal, configure a separate HTTPS endpoint for that event stream.
5. Apply bulk catalogue ingestion, availability updates, and takedown handling from Standard Metadata.
6. If enabled, ingest Enhanced Metadata after you have stored the Standard Metadata and attach the enhanced fields to your existing track records.
7. Use Enhanced Metadata to enrich discovery and curation, but continue to use Standard Metadata as your source of truth for release structure and availability.

Standard Metadata tells you what is in the catalogue and where it can be used, while Enhanced Metadata is an optional enrichment stream that adds extra descriptive fields to help with discovery and curation.

Bulk Catalogue Ingestion

Bulk catalogue ingestion is delivered as part of the Standard Metadata received from licensors through Catalogue Events. Upon initial integration with Standard Metadata, services will be required to ingest a backfill of all cleared licensors' catalogues. This will need to occur whether you are:

• A new client onboarded to the digital platform
• An existing client who has licensed a new licensor

This follows the same process as standard day-to-day events and is delivered through POST requests to your dedicated endpoint. You must use the same endpoint for both backfills and regular events. Separate endpoints are not supported, so backfilled and regular events will be delivered to you simultaneously.

How long does bulk catalogue ingestion take?

The backfill process operates at up to 400 requests per second (RPS). At this rate, a complete catalogue backfill of 30 million releases takes up to 24 hours.

Design your systems to handle and acknowledge requests at or near this rate. Day-to-day events will be sent at a significantly lower rate per second (single digits) once you have been onboarded, but requests that time out during a backfill can result in events permanently failing.

If you cannot process events at the full backfill rate, you may choose to receive, acknowledge, and store them somewhere while you process them later at a lower rate. This is at your discretion.

Managing Availability

Availability is delivered as part of the Standard Metadata received from licensors through Catalogue Events.

Both ALC download and streaming availability will be sent in Events as it is received by licensors.

Subscription streaming - clearances which indicate where a release can be used in any service licensed to utilise on-demand streaming rights. Where no subscription streaming clearances exist, the release is unavailable to be used for on-demand streaming services, although the release may retain streaming rights for other business models.

Ad-supported streaming - clearances which indicate where a release can be used in any service licensed to utilise ad-supported streaming rights. Where no ad-supported streaming clearances exist, the release is unavailable to be used for ad-supported streaming services, although the release may retain streaming rights for other business models.

ALC (Permanent) Download - clearances which indicate where a release can be used in any service licensed to utilise ALC download rights (also known as permanent download rights). If there is a release-level Digital Booklet available (called PDF Booklet in the schema), it will only be available to purchase as part of the entire release.

Takedowns/End Dates - can be delivered to us in several different ways as part of the licensor-provided Standard Metadata. Catalogue Events will maintain the structure of this data, ie, we do not transform it and pass it through. The most common examples of how licensors will remove content are:

• A new end date is provided. Content should not be used past that date
• Start and end dates are the same day
• An empty release, with only the fields id, version and takedown (see example)

Integration Support

Services who have questions or issues regarding Catalogue Events should raise these with the Client Success team via MassiveMusic's support email address [email protected]. The team will review each ticket and respond with feedback within UK office hours.