Might be it's a legacy issue as well.... but never encountered it, and I'm sure I did update a given DISCOGS_RELEASE_ID field to a different DISCOGS_RELEASE_ID value when it was more appropriate/available to fetch the data from.Just FYI, as this works and I can get around the issue of the DISCOGS_RELEASE_ID not being re-written when updated in foo_discogs - so my current workflow for that then is, if I need to re-tag from a different release ID:
- Edit DISCOGS_RELEASE_ID on all files by hand to the new release to fetch data from
- run foo_discogs, picks up the new correct DISCOGS_RELEASE_ID , then applies all the data
This way I can get around not having disconnected data, i.e. the DISCOGS_RELEASE_ID from the previous release, and the data from the new one, stated in the foo_discogs first window ID input (which does not get rewritten, iif updated by hand).