Feature Request: Chained platform sources with different tags extracted [via ISRC]

[eejd]

Summary: When the files you would like to Auto Tag have a known source (e.g. Beatport, iTunes purchase, etc.) and you can extract the primary metadata from the correct platform, it should be possible to then use the canonical identifier (i.e. ISRC) to retrieve additional tags from other platforms (e.g. Mood, Sub-genre, etc.) and Audio Features. Ideally, this would be viewed as a single Auto Tag sequence, where there is a primary (or multiple primary) platforms selected which are used sequentially to get core metadata and ISRC and then secondary platforms that are searched for additional information. Then any primary platform would be used to determine 'success' or 'failure' and the secondaries are just used to get the additional data—and therefor are never failures, even if the track is not included.

Details: I often know the source of my files or have a canonical source I would like to use. For example, I have online playlists on streaming services I use to identify new material and evaluate if they are interesting to add to my DJ catalog. I also often get tracks from platforms I know as the source. Ideally, I would like to use 1T in these cases to get the full metadata and ISRC canonicalized by an Auto Tag run, but also get any and all extra metadata available. Currently, even if I know that a song comes from a platform (e.g. Beatport), I cannot select it as a 'primary' source—but still get extra tags from additional sources. My current experimental workflow is to have a configuration for a few primary sources, where I get all tags, then a secondary configuration that I run after to get Mood, extra Genres, sub-genre, etc. In general, it seems that there might be other workflows that users might like to implement where you can chain one or more platforms for primary searches and one or more platforms for secondary searches. Specifically, this should speed up large batch searches—especially if the source of the files is largely related to (or like to be found) on one or two platforms, were the remaining searches can be ISRC based and only collected a few tags.

For me, a related problem is interpreting the 'success' and 'failure' counts, as these are not aggregated or managed differently depending on if the platform is being used to get supplemental data or for primary identification. I am currently using 1T on small batches of incoming tracks, but I would like to go back and re-tag my entire collection to ensure complete tags and maximal metadata... which I couldn't see doing without some form of a feature like this.

Possible implementations:

1. A simple solution would be to group platforms into 'primary' and 'secondary' (allowing the same platform in both cases, potentially) where the primary is 'matching' and ensuring an ISRC and then the secondary is for additional tags. (So, in this case, the tags, overwrite, etc. would be also settable separately for 'primary' and 'secondary'.
2. A more complex approach (not sure if it would be useful) would be a tree search strategy where you could define primary, fallback platforms or additional metadata platforms.
3. Simply allow the tagging update options to depend on having found a first match (with ISRC) and then every remaining platform becomes a secondary.