Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mimic MBS edit note validation and warnings #712

Closed
thomasboehm opened this issue Oct 13, 2022 · 4 comments
Closed

Mimic MBS edit note validation and warnings #712

thomasboehm opened this issue Oct 13, 2022 · 4 comments

Comments

@thomasboehm
Copy link

When merging release groups, I get the warning about the destructive edit and after clicking OK it goes back and the edit note field is highlighted in red. What am I doing wrong?

Selection_077

Firefox 105.0.3
Greasemonkey 4.11
Kubuntu 22.04

@jesus2099
Copy link
Owner

jesus2099 commented Oct 13, 2022

You have forgot to write an edit note for the edit reviewers and for history.

It's the same if you don't use the userscript.

image

Merging entities is a destructive edit.
You must know what you are doing and you must explain it in the edit history, why you are merging, why you think they are the same.

I will change my scripts (MERGE HELPOR 2 and MASS MERGE RECORDINGS) to mimic MBS, using the same error messages and styling.

@jesus2099
Copy link
Owner

jesus2099 commented Oct 13, 2022

Ah sorry, I see that you did write an edit note:

duplicate release group

My scripts are validating edit notes and they think this one is not enough. 🤣
I will maybe lower the threshold of validation.

Didn't my script explain this?

Merging entities is a destructive edit that is impossible to undo without losing ISRCs, AcoustIDs, edit histories, etc.
Please make sure your edit note makes it clear why you are sure that these entities are exactly the same versions, mixes, cuts, etc.

Did you see this warning?

@jesus2099 jesus2099 changed the title mb_MERGE-HELPOR-2 doesn't accept edit note Mimic MBS edit note validation and warnings Oct 13, 2022
@thomasboehm
Copy link
Author

Maybe you could lower the threshold for release groups only. Two release groups with the same name are very rarely correct.

In the last few weeks/month I see a lot of new users using some scripts to scan their music collection and adding release groups even if there is already one.

In my example the band 10cc had their last release 27 years ago, yet some newbie thought he should add each album with a new release group.

https://musicbrainz.org/artist/f37c537b-3557-4031-bfd6-ab63ced32854

Maybe Musicbrainz should make it much harder for new users to create release groups.

jesus2099 added a commit that referenced this issue Oct 27, 2022
MBS forbids ".." and "a"
I additionally forbid ".a." and " a "
jesus2099 added a commit that referenced this issue Oct 27, 2022
Align on valid edit note conditions and text
Stop using (cu)cumbersome alerts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants