> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/platform/catalog/managing-your-assets/viewing-a-release/metadata.md).

# Metadata

Learn how to manage your track and release metadata on Revelator. This section covers all key metadata fields—Track Title, ISWC, Genres, Lyrics, Copyright Information, Language,  and more

## The **Metadata** section provides comprehensive details about the release, including:

***

### Release-Level Metadata:

{% stepper %}
{% step %}
**Metadata Language**

The language used for all metadata fields.
{% endstep %}

{% step %}
**Release Title & Version**

The official release name and any versioning details (e.g. *Deluxe*, *Remastered*).
{% endstep %}

{% step %}
**Primary & Secondary Genre**

Main and secondary genre classifications.
{% endstep %}

{% step %}
**Catalog ID**

Internal identifier used by the label or distributor.
{% endstep %}

{% step %}
**UPC (Universal Product Code)**

A unique 12-digit code that identifies the release. Required for tracking, sales reporting, and DSP delivery.
{% endstep %}

{% step %}
**Copyright Information**

Copyright holder name and year of copyright.
{% endstep %}

{% step %}
**Catalog ID**

Internal identifier used by the label or distributor.
{% endstep %}

{% step %}
**UPC (Universal Product Code)**

A unique 12-digit code that identifies the release. Required for tracking, sales reporting, and DSP delivery.
{% endstep %}

{% step %}
**Copyright Information**

Copyright holder name and year of copyright.
{% endstep %}
{% endstepper %}

***

###    **Track-Level Metadata:**

{% stepper %}
{% step %}
**Track Title**

The track’s name, including any version or content tags (e.g. *explicit*).
{% endstep %}

{% step %}
**Title Version**

The track’s name, including any version or content tags (e.g. *explicit*).
{% endstep %}

{% step %}
**Language**

The primary language of the track’s lyrics or spoken content.
{% endstep %}

{% step %}
**Track Origin**

Describes the composition type of the track. *Original Work*, *Cover Song*, or *Public Domai*
{% endstep %}

{% step %}
**Track Properties**

Describes the nature of the recording. *Remix or Derivative*, *Samples or Stock*, *Mix or Compilation*, *Alternate Version*, *Special Genre*, *Non-Musical Content*, *Includes AI*.
{% endstep %}

{% step %}
**ISWC**

International Standard Musical Work Code used to identify compositions.
{% endstep %}

{% step %}
**Preview/Clip Start Time**

International Standard Musical Work Code used to identify compositions.
{% endstep %}

{% step %}
**Lyrics**

Field for entering or managing track lyrics.
{% endstep %}
{% endstepper %}

###  Best Practices

• Always double-check localized titles for accuracy in each language.

• Ensure your UPC and ISWC codes are valid and not duplicated.

• For UGC platforms, set a Preview Start Time that highlights the most engaging part of the track.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revelator.com/pro/platform/catalog/managing-your-assets/viewing-a-release/metadata.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.