Quick Start

Introduction

The Supplier Portal is where the suppliers of a catalog - labels, producers and distributors - maintain their own recordings and releases and hand them over as delivery-ready metadata. It complements melino Label and melino Publishing, which are the receiving side.

Where the Artist Portal is a read-only window onto data a label owns, the Supplier Portal is the opposite: the supplier owns the records and edits them directly. Nothing has to be requested from anyone.

Terminology throughout follows DDEX: a Release is the product, a Recording is the sound recording resource on it, and a Party is any person or company credited on either. That is what makes a release exportable as an ERN message at the end.

Signing in

There are no passwords. Sign-in runs in up to three steps:

A passkey can only be registered from a session that already exists, which is why the emailed code cannot be turned off. Passkeys are managed later under Account.

Clients

One account can hold access to several clients. The client is part of the URL - /{client}/recordings - so the address bar is always the answer to "whose catalog am I looking at". The switcher in the top bar navigates rather than flipping hidden state, which means two browser tabs can sit on two different clients without interfering with each other.

Switching carries the section across, never the record: an id from one client means nothing in another. If you switch while a release is open, you land on the other client's release list.

Everything is scoped to the active client. ISRC, UPC/EAN and label name are unique per client, not globally, so two clients may each hold their own record with the same identifier.

Key entities

How the catalog fits together

Create Parties (or invent them while crediting)
      │
      ▼
Create Recordings → add ISRCs, credits, upload the audio master
      │
      ▼
Create a Release → add UPC/EANs, artwork, release artists
      │
      ▼
Put Recordings on the Release and order the track list
      │
      ▼
Validate against the DDEX ERN schema → download the XML

Two tiers of metadata

Every edit form is split in two. The core section carries what almost every delivery needs - title, artist, label, genre, duration, release date. Everything below Full DDEX metadata sits behind a collapsed accordion: C-line and P-line, recording year, country of recording, sub-genre and the content flags.

The split is deliberate. Core is enough to get a record into the catalog; the advanced tier is what a DSP or a society will ask for before they accept it.

Lists

Every list screen shares the same controls: a search field, sortable column headers, pagination with a page size of 25, 50 or 100, a column menu for showing and hiding columns, and a New button. Lists are sorted newest-first by default. Clicking a row opens that record for editing.

Saving

One rule covers the whole application: nothing is saved until you press Save. Uploading a file is the exception and commits immediately; deleting anything asks first. See Editing and saving for the details.

Components

Select a topic to explore the documentation:

General

Catalog

Administration

Guides