Getting Started

Catalogue Delivery Service (CDS)

What is it and who is it for?

A Catalogue Delivery Service (CDS) is used where a client wishes to store the catalogue metadata, and in some cases assets, on their own system. This would mean that the client is building out all or most APIs that would be required for their particular use case. In each use case below the client can send logging information to enable Tuned Global to complete end of month rights holders reporting, subject to this being included in your agreement. At a high level, the types of use cases are:

1. Where the client wishes to store and deliver all metadata to end users, including images and audio. The client will use the CDS JSON metadata feed to access all metadata and then use the images and assets APIs to retrieve audio and images, all of these items shall be stored by the client.
2. Where the client wishes to store and deliver all metadata to end users, including images but all audio would be delivered by the Tuned Global systems. The client will use the CDS JSON metadata feed to access all metadata and then use the images APIs to retrieve images, these items shall be stored by the client. Audio assets will only be fetched using the APIs as they are requested by users. This should mean considerable savings by the client as large sized audio assets will not need to be stored and only accessed on demand.
3. Where the client wishes to store and deliver all metadata to end users, but all images and audio would be delivered by the Tuned Global systems. The client will use the CDS JSON metadata feed to access all metadata which shall be stored by the client. Audio assets and Image assets will only be fetched using the APIs as they are requested by users. This should mean considerable savings by the client as large sized audio assets will not need to be stored and only accessed on demand while images can be available at eny size required by the client applications.

The components of a Catalogue Delivery Service are:

1. A JSON Feed that contains metadata you require, plus
2. A set of APIs that allow you to get the assets you may need
3. A set of reporting APIs
4. A general set of APIs to manage some components of the service.

To implement this service we would recommend that you first implement in the following order;

1. The importing and management of the JSON feed. Read the Catalogue Delivery Service documentation.
2. Retrieving image assets and using the image resizing engine if required
3. Retrieving preview assets (where required and available)
4. Retrieving full length audio assets (where required and available)
5. Where Tuned is managing reporting, implement the logging of plays as per the specification