Uploaded image for project: 'MusicBrainz Style'
  1. MusicBrainz Style
  2. STYLE-351

Release group official website wording causes it to be misused

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2014-12-03
    • None
    • Relationships
    • None

      The current wording of the official website relationship for release groups causes it to be largely misused. I think we should change the wording to try and improve that.

      The main problem seems to be the word "official". People seem to see that and think it means they should use it for anything which is official. It also seems to be possible to misread it as meaning a link to a page on the artist's official website.

      According to https://beta.musicbrainz.org/search/edits?auto_edit_filter=&order=desc&negation=0&combinator=and&conditions.0.field=type&conditions.0.operator=%3D&conditions.0.args=90%2C233&conditions.1.field=link_type&conditions.1.operator=%3D&conditions.1.args=287&conditions.2.field=open_time&conditions.2.operator=%3E&conditions.2.args.0=2014-10-18&conditions.2.args.1=&conditions.3.field=open_time&conditions.3.operator=%3C&conditions.3.args.0=2014-11-18&conditions.3.args.1=&field=Bitte+w%C3%A4hle+eine+Bedingung there have been 138 of these relationships added in the last month. Out of those, skimming over them, I counted 89 which look wrong and if that's representative of how people normally edit, that suggests at least two thirds of the edits using this relationship type are wrong, and if most of the data is wrong, that makes the relationship type pretty useless.

      I'm not sure what the best wording would be, but a few possible ideas:

      • release (group) website
      • release (group) standalone website
      • release (group) mini website

            reosarevok Nicolás Tamargo
            nikki nikki
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2014-12-03