Somewhat confusing 🙂

When running the Discogs or MusicBrainz wizards (UI) there is not currently any way to override consistent import settings retained in files. I can see the case where import settings were retained inadvertently so perhaps having an 'Always Ignore Retained Import Settings' option makes sense. Many years ago, the retained import settings capability was added as evidently the ability to refresh an album with retained settings was desired.

If I pull in an album imported the "wrong" way, I need to use the contextual menu during the import wizard to select my saved set. However, doing this for every album would be suicidal.

True, however, if there is not a consistent set of import settings values, the last used settings will be retained. There would be no need to always select your saved values. Currently, this is always overwritten. So, 'Always Ignore Retained Import Settings' would work ... as would an always use a named import settings set (of a specific name) if defined.

Second, is there a way to batch change directories for which I have things wrong?

This is easier as long as you've already retained the Release ID and the Release Ordinal Position in the files. If you have those UDTIs retained, you can use an Access Discogs statement (which allows you to explicitly specify named import set, or a Discogs Metadata for Release statement where you import whatever you want. Depending on what you want to extract, the Release Ordinal Position may not be required. Deleting whatever you don't want is easy.

A batch process could be used to download only the information that you want if you can determine which folders should be processed from the metadata. For example Country is missing. As long as you've retained the required release information, this is doable.

What I've written could also be confusing 🙂

Let me know if it makes sense. I'll look into what it would take to add the one or two options to be able to ignore retained import settings.

Thanks for the response. I'll reread the docs and your input here and see if there's a workable solution. Appreciate the support as always.

There is really no concept of a selected import set. It's loaded and which was loaded is not retained.

I can do the following relatively easy and fast. If you have an import set named Always Use it will automatically be loaded when the Discogs or MusicBrainz wizard is first started. They each have their own list of import sets.

Note the when the Discogs or MusicBrainz wizard is first started verbage. If you start the Discogs wizard, change the import settings and back up to do another search, the last set settings will be used. However, the next time you start the wizard, the Always Use settings will again be loaded.

Let me know.

It'll be in v8.2.2 coming soon. The name of the set has been changed to Autoload

I'll be happy to help. However I need additional information. You've retained the Release ID. Have you also retained Release Ordinal Position and Track Position? If you gave, great I can extract everything simply using a Discogs Access statement. If you have not imported all three items, some of the Access Discogs extraction modes are disabled. The statement cannot extract per track information.

As long as you have the release ID, (regardless of the other two items), the Discogs Access statement can be used to extract all non per track metadata.

The question becomes, what metadata do you want to import in the batch repair run? If it's only non per track metadata, it's simple. If you want some per track metadata I'll have to use a Discogs Metadata for Release statement which is a little more complicated.

The following metadata is per track: Disc, Disc count, Media subtitles, Release ordinal position, Track, Track count, Track position and Title metadata. Let me know if you need to extract any of these fields

Also if you tell me what criteria is to be used to determine if you already have all the metadata ... ie. no need to extract again.

.... and if you want to rename the files or clear out other metadata let me know and I can stub that in the action as well.