Release Manager Bulk Import Guide – Too Lost - Help Center

General

Catalog Metadata- Below we describe the format for the CSV bulk upload template. Before you use the tool, it is recommended to use this guide and read it thoroughly.

Catalogue Assets- Assets won't be uploaded directly to the platform. Instead, the metadata file must include a URL from where the systems can obtain the asset in a single call. Our tool will automatically fetch the assets in real-time, from the given URLs in the CSV.

You can download the most recent CSV template attached at the bottom of this article.

Some Limitations

CSV bulk upload has some limitations:

This specific template only supports release inserts (excluding Ringtones and video clips).
Fields that are not supported: Release and track description and notes; Track lyrics, Track start time.
These fields cannot be inserted as a part of the bulk upload. You can update these fields from the regular interface once the upload process is complete.

Release and Track Field Definition

From line 8 and on in the CSV bulk upload template, you need to fill in your catalogue metadata info. Each line is for one track and contains the release (album) data as well. This way, if you upload for example a release with 10 tracks, the first part (Release fields) for the line will be filled with the same data for all the tracks (in all 10 lines), and the second part (Track fields) will be different for each of the tracks.
In this example, once you have uploaded the file, if there are no errors in the process, the system will upload 1 album with 10 tracks included.

Fixing Errors

If a release contains errors, it will not be uploaded, but free-of-errors releases will be uploaded in any case. Once the upload is complete, you will be provided with a CSV of failed releases, and details about the errors will appear when clicking on “Details”. This will allow you to fix the failed releases and upload another version of them.

Multiple Track relations

You can do the following regarding tracks relations:

Attach an existing track to a new release-
You can use this tool to attach a track that was already uploaded in the past, to a completely new release. In order to do that, you need to fill in the correct ISRC fields in the “Track Fields” section, and leave all the other fields empty. The “Release Fields” section should be filled as usual.
Attach a new track to multiple releases-
You can upload a new track to be included in multiple new releases within the same CSV file. In order to do that, you need to fill the same track metadata fields in the “Track Fields” section in more than one line and make sure you fill in different “Release Fields” in each of the multiple lines to attach this track to each of these releases.
Important: If this track already exists in the catalogue, follow the instructions from #1.

File Format

File must be [CSV] comma-separated fields, optionally enclosed by double quotes, as per RFC4180. File character encoding must be UTF-8 to ensure proper treatment for non-English languages.

Optional fields can be left empty, but their columns must be present in the document to maintain the structure the tool is designed for.

Release Type

Release format will be automatically assigned, following these rules:

Format	Description
Album	Releases with 7+ tracks.
EP	4–6 tracks.
Single	1–3 tracks.

Uploads menu

You will be able to upload your files from the Release Manager. By default, this option will not be available in your account as must be added by your account representative.

CSV Instructions

Metadata Section

The first section of the file is a metadata section (lines 1-5). All fields are mandatory and allow our tool to process the file correctly.

Field	Required	Description
description	YES	Description for you to identify this upload in the future. This field is especially useful if you use the tool more than once, and want to keep track of your uploads.
format_version	YES	The currently supported version is 4.
total_releases	YES	The total number of releases in the file.
total_tracks	YES	The total number of tracks in the file.

Release fields

Field	Required	Description
action	NO	'insert' is the only supported action in this version of the file. Any other action will raise an error. Default value: insert
upc	YES *	UPC must be a 13 digit EAN13 code. 12 digit codes will be converted to 13 digit codes, by being front padded with a zero. * If your code has leading zeros, the value should be between quotes. What is a UPC code? If you do not have a code for this release, you can request the assignation of a new code by filling in the value "auto". It is mandatory to fill in either UPC or Catalog_Number with a valid ID. You cannot fill in “auto” for both.
catalog_number	YES *	Catalogue numbers can only contain alphanumeric characters, with a length from 1 to 45 characters, and uppercase letters. If you do not have a catalogue number for this release, you can request the assignation of a new code by filling in the value "auto". It is mandatory to fill in either UPC or Catalog_Number with a valid ID. You cannot fill in “auto” for both. On the other hand, please take into account that the catalog number introduced manually on the bulk upload does not follow a platform sequence. This means that you could end up with repeated catalog numbers. Catalog numbers are simply a internal reference number for your use. However, we would recommend following a different sequence for your bulk upload releases. For example "MYLABELBULK12345678" instead of "MYLABEL12345678".
grid	NO	A [GRID] code. Alphanumeric.
title	YES	Release title. This is the title of your album / EP / Single.
remix_or_version	NO	Release remix or version.
user_email	YES	User email for the account that owns this release. This field is a sensitive field and your data should be confirmed well before. Once the content is uploaded under a specific user, it may not be migrated to another user.
label	YES	Label name. If the label does not exist under the user account given, it will be created.
participants	YES	Artists+Roles. If an artist's name does not exist under the user account given, it will be created. Please review the “Participants” chapter below.
primary_genre	YES	Must be from our official genres list.
secondary_genre	NO	Must be from our official genres list.
language	YES	ISO 639-1, 2-letter code of the metadata language of the release, for all languages except the "non-linguistic content", for which you have to use the ISO 639-2 Code "zxx".
explicit_lyrics	YES	Does the release contain explicit lyrics? 'explicit' / 'not_explicit' / 'cleaned' (lowercase).
price_category	NO	Price category that will be applied in the channels you will distribute to. Default value: mid
digital_release	NO	Digital release date in YYYY-MM-DD format. The default date is the import date.
original_release	YES	The original release, in YYYY-MM-DD format, must be the earliest date that the original product was first released regardless of the releasing label, or format type (for example, LP, CD, or digital-only release). The original release date for remasters must be the first date the original recording was available and not the release date of the remastered recording.
license_type	NO	License types currently supported are copyright (value "(c)") and Creative Commons [CC] (value "cc") . Default value: (c)
license_info	NO	See below “Creative Commons Licenses”.
c_year	YES	Copyright year in YYYY format.
c_line	YES	Copyright text line.
p_year	YES	Publishing rights year in YYYY format.
p_line	YES	Publishing rights text line.
territories	NO	A semicolon (;) separated list of ISO 3166-1 alpha-2 codes for the countries where you've got the rights for this release. Use 'WD' for worldwide. Default value: WD
cover_url	YES	URL for the cover image. Read below for an explanation of how to attach assets.
track_count	YES	Number of tracks that this release contains. This is a validation field.

Track fields

Tracks for the release will be numbered from 1 onwards, in the order, they appear in the CSV bulk upload file. On the 2nd and later track lines for the same release, all release fields must be present and consistent with the 1st release line.

Field	Required	Description
isrc	YES ***	ISRC for the track. Alphanumeric. If you do not have an ISRC code for this track, you can request the assignation of a new code by filling the value "auto". If the track already exists in your catalogue, you should leave all the fields empty and just add the ISRC code of the track. What is ISRC?
iswc	NO	ISWC for the track. Alphanumeric. What is ISWC?
track_title	YES	This is the title of your song.
remix_or_version	NO	Track remix or version.
participants	YES	Artists+Roles. If an artist's name does not exist under the user account given, it will be created. Please review the “Participants” chapter below.
primary_genre	YES	Must be from our official genre list.
secondary_genre	NO	Must be from our official genre list
language	YES	ISO 639-1 2-letter code of the language in which the track is sung. In addition to ISO 639-1 codes, 'zxx' from ISO 639-2 code list can be used to indicate "no linguistic content". Click here to check for your language 2-letter code.
explicit_lyrics	YES	Does the track contain explicit lyrics? 'explicit' / 'not_explicit' / 'cleaned' (lowercase).
p_year	YES	Publishing rights year in YYYY format.
p_line	YES	Publishing rights text line.
audio_url	YES	URL for this track's audio master. Read below for an explanation of how to attach assets.

How to fill in Participants

All artists and other participants' roles and names must be listed in the 'participants' single column. Each participant must be prefixed with his role and a colon. Role and name pairs must be joined with semicolons.

For example:

Primary artists: Natos, Waor.
Featuring: Ambkor.
Remixer: Natos.
Producer: Waor.
Composer: Waor.

Participants column should show:

primary:Natos;primary:Waor;featuring:Ambkor;remixer:Natos;producer:Waor;composer:Waor

Rules for Participants

Every release and every track must have at least a primary artist.

In a release or track a single artist can have a single role between primary, performer, featuring, and with.

For any release that is assigned a genre other than non-spoken, there must be at least one composer on each track.

Role Names List

Currently accepted participant role names (in lowercase) are:

primary
performer
producer
remixer
composer
author
editor
featuring
with
conductor
arranger
orchestra
actor

Duplicated track in the same CSV file

If you need to create a new track, with a specified ISRC, that will be shared in two or more releases, you can accomplish this by repeating the track in all of those releases, but take special care that the information of each track must be the same for all duplications.

If some track information differs from the others then all tracks will be marked as failed.

This shared track must have an assigned ISRC, they can't be an AUTO ISRC.

Repeated track in the user's catalogue

You can assign an existing track in the user's catalogue to a newly created release.

To accomplish this, in the CSV file we must leave empty all the track information except ISRC, which is the data we use to find the existing track in the user's catalogue.

How to attach Assets files

In the asset links fields (cover_url on release level, and audio_url on track level), you need to link to an available file so we can fetch it and upload it with your content.

Assets are mandatory and if any of the links fail, the release cannot be uploaded. Therefore, you need the ensure that the URLs point to the right assets.
If the URLs (e.g. WeTransfer) or the authentication credentials (e.g. S3 signed URLs) last only for a limited time, ensure that the time is long enough to allow the system to ingest the assets.

Please review our Audio files requirements guide.

Please review our Cover art requirements guide.

Asset Ingestion Supported Methods

Assets won't be uploaded directly to the platform. Instead, the metadata file must include a URL from where the systems can obtain the asset in a single call. It means that the URL has to be unique for each asset. For example, the cover link can be repeated for each track in the album, but the audio has to be one for each track (as the audio is different). The URL has to be a direct downloading link.

Authentication credentials of any kind must be included in the URL. The ingestion process won't follow any kind of separate login procedure.

The metadata does not have to be hosted permanently in the external URL, it only needs to be accessible while we retrieve it to process the album on our platform. Indeed from there on the audio and cover are stored in our system.

We currently support the following options:

Public URLs:

HTTP URLs
HTTPS URLs
FTP URLs
SFTP URLs
Amazon S3 URLs (with a signed URL if the asset is read-protected) (this is the preferred method)
Cloud storage services that provide public direct downloadable links (such as Dropbox; WeTransfer; Google Drive)

Authenticated URLs:
We support some methods of authenticated URLs, only with user and password. In order to include authenticated link, follow this formats:

Http URLs:http://{user}:{pass}@{host}/{file}
Https URLs:https://{user}:{pass}@{host}/{file}
FTP URLs: ftp://{user}:{pass}@{host}/{file}
SFTP URLs*:sftp://{user}:{pass}@{host}/{file}
Amazon S3 URLs**:https://{bucket}.s3.amazonaws.com/{file}?AWSAccessKeyId={accesskey}&Signature={signature}&Expires={timestamp}

* We only support public keys for SFTP URLs. In order to provide us with a public key, please contact our support center and coordinate your upload with our team.
** Amazon S3 URLs - with a signed URL if the asset is read-protected.

Creative Commons Licenses

We currently support only cc version 3.0. Use the 'license_info' to show creative commons clauses with the official acronyms, hyphen separated.

	Description	Acronym
	Attribution alone	BY
	Attribution + ShareAlike	BY-SA
	Attribution + Noncommercial	BY-NC
	Attribution + NoDerivatives	BY-ND
	Attribution + Noncommercial + ShareAlike	BY-NC-SA
	Attribution + Noncommercial + NoDerivatives	BY-NC-ND

Example Bulk Import CSV .csv
7 KB Download