I was going to attach the paragraph below to Display more info with “mb. INLINE STUFF” but then I realized I should probably create a new topic for it instead. What I had written by then:
Hmm, the more the features like this are mentioned, the more I think about how an “advanced editor” status with some UI enhancements is needed. Currently, we have userscripts for this, but I believe there should be separate editing UI for editors who apply for “advanced editor” status. Advanced editors could be both regular and autoeditors, since it would not actually change how their edits get applied. Currently we only have new editors (until first 20 edits IIRC) and after that they will become regular editors. Imo editors should apply for the status instead of getting it after certain number of edits, because I have seen editors with thousands of relationship edits and even years of mb membership who would definitely be confused by the “advanced editor” UI and could make a mess of the database.
In my opinion, having the same editing UI for regular editors, whether they have 50 edits or 50 000 edits is just not good enough. Currently, people use userscripts to make a bunch of mass-editing and mass-checking of the data easier and faster. However, I believe everyone will agree that having to use 50 userscripts to be able to do said editing work is a nightmare, mainly because there is high chance that some of the userscripts are not working, are buggy or simply outdated because of how mb is constantly evolving.
With the upcoming redesign, there have been talks of integrating some of the features from userscripts into the main UI which would partially mitigate these problems. However, a new issue will arise from this, and the issue is: Add only those features that wouldn’t make editors submit bad data or add more features but risk editors being confused and/or submit bad data. I personally think this approach causes too much chaos and we need an advanced editing UI for whoever applies for it (of course bad editors could be rejected from having such status so they don’t mess up the database) but I don’t think we need an election like we do for autoeditors for example.
Another benefit is that @chhavi wouldn’t need to be limited so hard when making the new UI. She and all the people who provided feedback on her redesign mockups know that balancing the aspects of the UI to not be confusing and overwhelming for starting or returning editors and not losing existing features/editing flow for existing experienced editors is another nightmare. I would prefer if we got an advanced editing UI with all the current features (and even more features taken from userscripts) on top of the new UI instead of compromising what to show/not show in the new UI because of new editors. You could also have settings in your profile for these advanced functions that came from userscripts, which would make it even better so advanced editors could choose which functions they need. And since all of the features would be native to mb, you wouldn’t need to chase the userscript devs on the script’s github pages and would just open a JIRA ticket instead.
Lastly, I’m not saying all userscripts should be ported into the advanced UI, I’m just saying the most common/useful/time saving ones should be, which is not possible with the regular UI (because regular editors would be confused and/or make a mess from the database).
Any thoughts on this matter? Is there anything that I missed? I apologize for a wall of text I just wrote my thoughts as they went and rolled with it
Edit: I found a post by @Zas that could be a tl;dr for this post: Your favourite User Scripts for MusicBrainz?! (so that they can be used while redesigning!) - the only arguable thing that came to mind is whether we allow these features for every editor or whether they need to apply for the special status to unlock them (some authority could then check their edits and decide if they are not a danger to the database). Granted, if people wanted to mess with the db at any point, they could just install userscripts and mass submit bad edits.