# \[Suggestion\] In 'Tag Sources', group the 5 'Discogs' entries in a separate submenu

**URL:** https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065
**Category:** General Discussion
**Created:** [September 5, 2023, 6:58pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065 "2023-09-05T18:58:00Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![ricky](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/439d5e/32.png) [@ricky](https://community.mp3tag.de/u/ricky)
#### Post date: [September 5, 2023, 6:58pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/1 "2023-09-05T18:58:00Z")

</div>

Currently the 5 Discogs entries in 'Tag Sources' are all separate:  
 ![2023-09-05_211839](https://community.mp3tag.de/uploads/default/original/2X/f/ff87e352952234d090598ffca350d2c14003beda.jpeg)  
My suggestion is to group them in a separate "Discogs" submenu which will contain:

- Search by Album _(the current 'Discogs' entry)_
- Search by Artist + Album
- Search by Artist + Title
- Search by Artist + Year
- Search by Release ID

This could make the Tag Sources list initially more compact, i.e. initially showing only:

```auto
Cover Art
Discogs
MusicBrainz

```

Here is what I mean _(with the addition of Metal Archives)_:  
 ![2023-09-05_214942](https://community.mp3tag.de/uploads/default/original/2X/9/984d37c2854407cfb48721dd8cf4841cbd560860.jpeg)

I tried the same with `Cover Art` group:  
 ![2023-09-05_211907](https://community.mp3tag.de/uploads/default/original/2X/2/20cf2dfea12a33e6c8b7142db0890294efeee1cf.jpeg)  
i.e. (renaming e.g.  
`Cover Art#Discogs Artist + Album.src` to  
`Cover Art#Discogs#Search by Artist + Album.src`),  
but it seems that multiple level subgroups are not supported.

Note: I have read the [relevant documentation page](https://docs.mp3tag.de/tag-sources/archive/#organizing-tag-sources) and I could simply modify the entries for myself without posting this suggestion, but since they the `Discogs` is among the default tag source ones (=they are installed by default), therefore ~~my modified versions would be overwritten~~ the initial ungrouped entries would be re-added with every new Mp3Tag release update. That's why I'm suggesting this re-organize.

Thank you

PS. Using Mp3Tag 3.22 x64 on win11.

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [September 5, 2023, 8:03pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/2 "2023-09-05T20:03:55Z")

</div>

> [@ricky](#):
>
> therefore my modified versions would be overwritten with every new Mp3Tag release update.

They would not get overwritten, because when you create submenues with # you rename them. What you would get are parallel existing websource-entries in the menue - your modified and the original entries.

---

<div class="post-metadata">

### Author: ![ricky](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/439d5e/32.png) [@ricky](https://community.mp3tag.de/u/ricky)
#### Post date: [September 5, 2023, 8:22pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/3 "2023-09-05T20:22:23Z")

</div>

Thank you for clarifying.  
I still believe that my suggestion would be useful, as it would make the default Tag Sources list more compact and convenient to use.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [January 22, 2024, 8:07pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/4 "2024-01-22T20:07:17Z")

</div>

For users that encounter web sources for the first time it would be more easily to see if all the script names are visible with a single click and glance and not need to navigate further.

You are right that it may be more convenient to group the scripts in sub menus if you have a lot scripts - but these would have been installed by you anyway.  
So if the need arises to also group the default scripts together then you have the options to do so.

---

<div class="post-metadata">

### Author: ![ricky](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/439d5e/32.png) [@ricky](https://community.mp3tag.de/u/ricky)
#### Post date: [February 13, 2024, 11:32pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/5 "2024-02-13T23:32:01Z")

</div>

In any case, I think that the default 1st "Discogs" entry should be renamed to "Discogs Album" to make its function clearer, i.e.:

- Discogs **Album**
- Discogs Artist + Album
- Discogs Artist + Title
- Discogs Artist + Year
- Discogs Release ID

The default "MusicBrainz" entry can remain as it is, i.e. not be renamed to "MusicBrainz Album + Artist",  
because it is the only one from this source.

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [February 14, 2024, 7:03am UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/6 "2024-02-14T07:03:24Z")

</div>

Mp3tag shows the name from the WebSourceScript file.  
Therefore you can rename the `Discogs.src` file to whatever you like.  
The name change will be visible immediately in Mp3tag.

![image](https://community.mp3tag.de/uploads/default/original/3X/5/b/5bb26c0d6560d41bedc24e976c51c5dcf560f366.png)

Location for `Discogs.src`  
File -\> Open configuration folder -\> subfolder `\data` -\> subfolder `\sources`

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 14, 2024, 7:49am UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/7 "2024-02-14T07:49:21Z")

</div>

> [@ricky](#):
>
> Discogs **Album**

For compatibility reasons:  
first, there was a single script for Discogs, the one that is based on the album, just like the one for Musicbrainz. And then further scripts got developed and added. And they had to get different names, of course.  
So, anyone who wants to participate in updates of the scripts that come with each installation, keeps the name and so does the creator.  
Otherwise, you would have 2 scripts for the same purpose after the next update.

If you don't like the name, then other posters in this thread have suggested workarounds.

---

<div class="post-metadata">

### Author: ![ricky](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/439d5e/32.png) [@ricky](https://community.mp3tag.de/u/ricky)
#### Post date: [February 16, 2024, 10:53pm UTC](https://community.mp3tag.de/t/suggestion-in-tag-sources-group-the-5-discogs-entries-in-a-separate-submenu/62065/8 "2024-02-16T22:53:50Z")

</div>

> [@ohrenkino](#):
>
> For compatibility reasons

Thanks for clarifying.

&nbsp;

> [@LyricsLover](#):
>
> Therefore you can rename the `Discogs.src` file to whatever you like.

> [@ohrenkino](#):
>
> If you don't like the name, then other posters in this thread have suggested workarounds.

Sorry for the confusion with my previous reply, I should have posted the screenshot below in instead of that bulleted list. Yes, I know that I can rename the various .src files to whatever I choose, that's how I did the screenshots in my OP.  
My purpose in making the suggestion in my previous reply (renaming 'Discogs' to 'Discogs Album') was about the names of the default .src files when you first install Mp3tag:  
 ![2024-02-17_001326~](https://community.mp3tag.de/uploads/default/original/3X/d/1/d11b4781c323ea215340b7690684603fcf5f4f3c.jpeg)

> **This is how the list is currently for me:**
>
> ![2024-02-17_004447](https://community.mp3tag.de/uploads/default/original/3X/0/5/05edafbdf444b3d528c9e70b8eb5908399a96cbb.jpeg)

&nbsp;  
In summary, I see that my suggestion with the OP (and with my previous reply) is not really worth implementing. Anyway, thanks for your replies.
