This might be a feature request?
I would like to be able to select all files that I am working on and goto discogs and pull tag data. Once I select the tag I want, go to the next file automatically instead of having to goto discogs again.
Kind of like this: [Request] Automatically select next file after import tags from Discogs, Beatport etc - General Discussion - Mp3tag Community]([Request] Automatically select next file after import tags from Discogs, Beatport etc)
Websource scripts work album/medium orientated and not file/track orientated. So you can
mark a whole album and fetch the metadata from discogs.
Automatically get metadata for - let's say Beatport Top 100 - is currently not possible with Mp3tag Websource scripts.
AFAIK Discogs does not support playlists with different artists and different songs like the one above. The chances of finding a source for your own playlist ("files I am working on") are close to zero.
It could be possible with streaming services like Spotify.
Create a playlist in Spotify exactly like the files you want to tag in the right order and submit the playlist to Spotify with a websource script.
But there is no websource script I know of, that can do this.
I dont know what experience you have, but I can always find tag information from discogs for the music I am working on.
In my experience, no automated method can tag my music correctly, especially not for multiple ARTISTs or ALBUMs.
I always have to manually check the ARTIST, the ALBUM, the release year, the number of tracks and the track sort order to ensure that exactly the one matching release will be used from the source.
Maybe I don't understand your
Yes, I dont think you understand the ask.
I dont want MP3Tag to automatially pick the tag information. I just want it to automatically start searching discogs for the next MP3 in the list.
edit:
Say I am working on a folder with 20 MP3s. I start at the top by searching discogs... Once I find the tag information that I want, I would like MP3tag to then search discogs for the next MP3 automatically.
I think it would be 3 clicks:
AFAI understand the idea, there should be a Next button in the web sources dialogue in addition to the OK button
Is it really the standard procedure for users to mark many single files for the websource call? When I use a websource I use it for an album, mark all files of an album and call the websource. How shall Mp3tag distinguish between several files as 1 album and orphaned files of different artists and albums?
Yes, the album-wise approach would be the preferred way in an ideal world. But apparently this is not how some people put together their collections. For some reason, there are a lot of free-floating single files around.
AFAI understand the suggestion, the function should not work on a bunch of selected files - here I would also see the possible ambiguity of complete album vs. single (orphaned) files - but a way to treat one file after the other from a list of loaded files.
It would be up to the user to stop clicking the Next button, if no more files should be tagged with data from the web source.
(also, a little GUI logic would be nice to disable the Next button if there is no next file).
Yes - this is what I am hoping to one day get implemented. I have a lot of MP3 that are not part of an album, so they cant be logically grouped as such.
edit: for context, I am a DJ and I do not collect/sort music "by album". MP3s are obtained from music services that provide MP3s in various "packages" that are essentially free-floating/orphaned files as you would call it.
I was not aware of this, I will try this. This might make my work a little more efficient (for now..) 
Idk if it would work for you and your specific usage needs, but whenever I have a bunch of loose single files , ill just go ahead and lump em all up n call the ‘album’ sumn like “demos” “singles” “2016 revisions” etc lol
Or like if an artist is follow never drops eps or full albums and legit just puts out each song as its own (which pisses me off so much.. 17 albums for 17 song.) I just make em all 1 album. Idk if thatll help you out at all. Figured id throw my 2 cents in
This method would make it even more unlikely to get information with the help of a web source script as it is not very probable that someone else put together the same tracks under the same user-defined album name as you did.
It is still valid, what @LyricsLover said:
