Download & fill out the Releases Metadata Import template.
Upload your completed Release Metadata template to the Remote Desktop Virtual Drive.
Navigate to the Import Menu and select Release Metadata.
Click on Import Data and select the file you want to import.
Analyze the imported metadata for errors and warnings.
Click to show only Valid and Create Releases.
Review Invalid releases to review errors and warnings. Warnings can be bypassed later on; errors must be resolved before the new release can be created.
Common errors and warnings include:
Match FAILED using ISRC: This occurs when associated assets do not yet exist in SR1 (and thus cannot be attached to releases being imported). Any new Assets will need to be created before you create releases (see step 9).
Invalid EAN/UPC: UPC/EAN should be 12 or 13 digits. Sometimes this results from a leading zero being cut off of a UPC (manually adding a 0 to the beginning of the UPC should validate).
Matched using ISRC. Title/Artist mismatch: This occurs when a release is matched to an asset via ISRC, but the Artist or Title data doesn't match exactly. If the data in SR1 is incorrect, you can manually fix it. If appropriate, you can ignore this warning and create the new release.
Release Exists: Analysis found that this release already exists in SR1. If you are expecting to import only new releases, these must be reviewed closely to avoid creating a duplicate release. If a client provides their full catalog each month to import, these will be common and should be omitted from new release creation.
To resolve a Match FAILED using ISRC error message, you'll need to create new Assets.
Once all errors have been resolved, you can go ahead and Create Releases.
Importing Releases into SR1 Using the Releases Metadata Import
![Sara avatar](https://static.intercomassets.com/avatars/7098251/square_128/Sclarson_Profile-1706711991.jpg)
Written by Sara
Updated over a week ago