You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
I recently encountered a user that used one of the scripts to automatically create lots of new works: https://musicbrainz.org/edit/112649307
The script leaves the following trace in the edit note:
—
MusicBrainz: Batch-add "performance of" relationships 2023.7.2
Relate to new work using recording title
The problem is that this script doesn't check if a work is already attached, or if a work already exists. This has led to countless new useless works added, with near-identical titles or to recordings where the correct work is already attached. Is there a way to give a warning when using the script, or at least check if a work is already linked before creating a new one? Also, the works it creates do not have any properties/relationships attached to them, making them pretty useless. Is this a case of lack of discernment of the user, or could the script be improved to make it less prone to this kind of behavior?
I haven't used the script, I just cleared up the mess when a user went nuts with it.
Thanks,
Dorian
The text was updated successfully, but these errors were encountered:
Hi all,
I recently encountered a user that used one of the scripts to automatically create lots of new works: https://musicbrainz.org/edit/112649307
The script leaves the following trace in the edit note:
—
MusicBrainz: Batch-add "performance of" relationships 2023.7.2
Relate to new work using recording title
The problem is that this script doesn't check if a work is already attached, or if a work already exists. This has led to countless new useless works added, with near-identical titles or to recordings where the correct work is already attached. Is there a way to give a warning when using the script, or at least check if a work is already linked before creating a new one? Also, the works it creates do not have any properties/relationships attached to them, making them pretty useless. Is this a case of lack of discernment of the user, or could the script be improved to make it less prone to this kind of behavior?
I haven't used the script, I just cleared up the mess when a user went nuts with it.
Thanks,
Dorian
The text was updated successfully, but these errors were encountered: