Folder structure
Each release must sit inside a folder named after the release's UPC.
Example:
760666754128/
├── 760666754128.jpg
├── 760666754128_01_01.wav
├── 760666754128_01_02.wav
760666754129/
├── 760666754129.jpg
├── 760666754129_01_01.wav
Cover art
The cover file must be named after the release's UPC.
Example:
760666754128.jpg
Audio
Audio files must follow this format:
<UPC>_<DISC_NUMBER>_<TRACK_NUMBER>.<extension>
Examples:
760666754128_01_01.wav
760666754128_01_02.flac
760666754128_01_03.mp3
What this means:
01_01 = Disc 1, Track 1 01_02 = Disc 1, Track 2 01_03 = Disc 1, Track 3
For multi-disc releases:
760666754128_02_01.wav
This means:
760666754128__Disc 2_Track 1
Delivering the files
The recommended way to share the files is through an S3-compatible bucket (for example, Amazon S3 or DigitalOcean Spaces), since this lets us automate the import process more efficiently.
Random Sounds can provide storage space for the upload if you prefer.
If that isn't possible, we can also look at other options such as Google Drive.
Whichever platform you use, the files must follow the folder and naming structure described in this article.
How the CSV and the files relate
The UPC used in the CSV must match the UPC used in the folder and file names exactly.
Example:
CSV:
UPC: 760666754128
Files:
760666754128/
├── 760666754128.jpg
├── 760666754128_01_01.wav
├── 760666754128_01_02.wav
Important
If you can't organize the files following this structure, the migration may require additional manual work to match the files to the right releases, which can increase import times.
If you have questions about how to prepare the files, or you'd like to validate the structure before sharing everything, you can send one or two sample releases for review.