I've been using Yate for a while now, but I haven't had time to dive into Actions until just a few days ago. I really appreciate this functionality. It's saving me a ton of time.
I assembled a batch action that imports metadata from Discogs. It reads the Discogs Release Id value from the parent folder/directory (e.g. "Donovan;1969;2422420" where "2422420" is the release id). It reads the disc and track numbers from the file name ("DD-TT Title.flac", where DD and TT are the zero-padded disc and track numbers respectively).
From there it builds the values for the Track Position and Discogs Release Ordinal Position fields. The track position value seems to have two variants.
Take the case of the first track in an album:
1. Track Position = 1, for a single disc release
2. Track Position = 1-1, for a multi-disc release
I thought I'd figured out the pattern for the Discogs Release Ordinal Position field. Initially I constructed these values as "track number minus one" for disc one, and "sum of track counts of previous discs, plus track number of current track, minus one" for subsequent discs in the release.
1. Disc one, track three -> Discogs Release Ordinal Position = 2
2. Disc two, track 2 -> Discogs Release Ordinal Position = 3 (assuming disc one has exactly two tracks)
But now I'm finding that it's not that simple with multi-disc releases. For example:
These two multi-disc releases follow the above pattern (start counting from zero and end at "release track count minus one"):
1. 6097171 (Ministry - Twelve Inch Singles)
2. 4147144 (Can - The Lost Tapes)
And these two multi-disc releases are exceptions to the above pattern:
1. Release 6451663 (William Onyeabor), which has 37 tracks, starts at Discogs Release Ordinal Position = 1 for track one, and skips a few numbers along the way so that it ends up at ordinal position = 45 for the 37th track.
2. Release 1195635 (Vangelis - Blade Runner Trilogy), which has 36 tracks, starts at ordinal position = 1 for track one, and also skips a few numbers to end up at ordinal position = 38 for the 36th track.
My first thought is that there's inconsistent data in the Discogs database. But I'm not sure how to approach this issue with Discogs. I have not found any relevant information in their guidelines, or any way to edit the release ordinal position values on the Discogs site. The only way I'm aware that these ordinal position values exist is through the Yate application.
How would I describe these values to Discogs so that they understand what I'm referring to? I started looking at the Discogs API documentation, but there's a lot of information to sort through. Can you point me in the right direction?