Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-8369

Require edit notes for cover art uploads

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Edit system
    • None

      Recently there has been an epidemic of users who pull release cover images from Google Images, Amazon or other such websites and add them to MB with no notes explaining where they came from. Many users don't think anything of it (myself once included), but it becomes a problem when that user selects the wrong release (e.g. https://musicbrainz.org/edit/32493819) or adds a blatantly wrong image (e.g. in https://beta.musicbrainz.org/edit/30739200, where the image is a known fan-made Photoshop).
      Having editors provide the source of the images they upload will help us sniff out such cases and rectify the situations as they arise.

          [MBS-8369] Require edit notes for cover art uploads

          Blocking the button based on the edit note field content will become a lot more trivial once we convert this to React, so linking this to the appropriate ticket so we hopefully remember to do it just after the conversion  

          Nicolás Tamargo added a comment - Blocking the button based on the edit note field content will become a lot more trivial once we convert this to React, so linking this to the appropriate ticket so we hopefully remember to do it just after the conversion  

          Ulrich Klauer added a comment -

          Ulrich Klauer added a comment - Some discussion at https://community.metabrainz.org/t/suggestion-stricter-rules-for-adding-cover-art/103322

          pankkake added a comment -

          Is there anything holding implementing this?

          I think something extremely simple like graying out the button like it happens in the release editor (i.e. purely JavaScript) would be enough. The idea is to make users think, not to have flawless security which wouldn't help us anyway.

          pankkake added a comment - Is there anything holding implementing this? I think something extremely simple like graying out the button like it happens in the release editor (i.e. purely JavaScript) would be enough. The idea is to make users think, not to have flawless security which wouldn't help us anyway.

          pankkake added a comment -

          The problem is steadily getting worse. I'm pretty sure a third of the new images we get are associated to the wrong releases.

          pankkake added a comment - The problem is steadily getting worse. I'm pretty sure a third of the new images we get are associated to the wrong releases.

          pankkake added a comment -

          I second that. There are two factors I hope this would improve:

          • Writing the note makes the editor think more. Ideally, there's also a suggestion of what to provide (why they think it's the cover of this edition, and maybe the source).
          • Having a note makes checking for correctness much faster.

          The note requirement does not have to be on the server side, if that's complicated; only a simple JavaScript enable/disable of the button or something.

          pankkake added a comment - I second that. There are two factors I hope this would improve: Writing the note makes the editor think more. Ideally, there's also a suggestion of what to provide (why they think it's the cover of this edition, and maybe the source). Having a note makes checking for correctness much faster. The note requirement does not have to be on the server side, if that's complicated; only a simple JavaScript enable/disable of the button or something.

            Unassigned Unassigned
            hibiscuskazeneko HibiscusKazeneko
            Votes:
            11 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:

                Version Package