richardbirkin
commented
1 year ago I've done some documentation around the columns that we need to grab from each line to infer what has had a usage, what version it is, and what universal identifiers there should be for referencing third party APIs or grouping tunes into albums and products.
Cargo Physical
This comes as a .xlsx file and contains sales of physical products (vinyl, CD, tape etc.)
Perfect for assembling 'albums' as a group of 'tunes'
Also great for metadata such as ISRC and UPC as these are mandatory for distributors, unlike Bandcamp where metadata is optional.
Bandcamp
We're pretty familiar with this now, so just adding for reference and to capture our current thinking as I understand it.
Column C tells us what has had a usage. track is a single track purchase, album is an album
Column D is the title of the thing.
If the thing is a track then its ISRC will be in column AG (if an ISRC has been supplied).
If the thing is an album then its UPC will be in column AF (if a UPC has been supplied).
The product version of the thing is in AA
The artist is in E.
Cargo Digital
Contains tunes that have been streamed on a Digital Service Provider e.g. Apple Music.
TBC - is the -products.csv file different from the -royalty-extended.csv file i.e. when someone buys a whole album from Apple Music, they are buying a product, not streaming a tune. I need to spend some time with the files and figure this out.
UPDATE: everything that is reported in -statement i.e. the ££ that hit the label account adds up the same as everything in -royalty-extended.csv So that's all that matters really.
We'll have all the ability to load album art from DSPs. I'm currently in the process of making a lovely self-documenting Spotify API client, so I'll use that.