Because @chhavi specifically mentioned that she’d like to include the functionalities of some of these scripts in the upcoming redesign, I’m only gonna focus on the features that I think are suitable for every user, including new and inexperienced editors. Besides, most of the scripts I’m using have already been covered.
Here is my complete list for reference (I think the last one is currently not working):
Here are the features that I think could be implemented so that everyone could take advantage of them (as I said earlier, even new and inexperienced editors):
mb. INLINE STUFF
- displays how many cover arts does the release have and modifies the link to add CAA if there is none
mb. PENDING EDITS
- if the entity has open edits, it displays a highlight on the “Open edits” button and shows the open edit count
MusicBrainz: Expand/collapse release groups
- an ability to expand release groups on the overview page into releases and tracks (this feature has already been looked into for the artist overview page redesign at [MBS-9536] Redesign of "Artist" Overview Page - MetaBrainz JIRA)
Honorable mention:
mb. MERGE HELPOR 2
- indicates which entity has the oldest MBID, so no data will be lost after the merge
I decided to mention this userscript despite thinking the concept of MBID age would be complicated/confusing for new or inexperienced editors. The most important strength of this userscript is that it potentially prevents the loss of data. I remember when I was a new editor I merged some recordings and picked the target recording based on: a) most correct name and/or artist credit, b) most information attached to it, such as ISRC or relationships or c) consisted of the most tracks. I didn’t really pay attention to the MBID age, so it’s quite possible that some information could have been lost, because afaik the edits for the recordings with older age than the ones I had merged into can’t be viewed anymore. The most often case is the first one where people are merging entities into the newer MBID simply because the title or artist credit is correct on the newer entity instead of fixing the older MBID and merging it into that one. I think I even had to defend one of my edits simply because someone thought I was merging the “correct” recording into the “incorrect” recording while I was merging the newer MBID into the older MBID while also fixing the title and artist credit on the recording with the older MBID at the same time. Perhaps there could be a warning of some sort or even a guide how to fix the “incorrect” entity in these cases to preserve the entity with the older MBID. This is just some food for thought.