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

Rename Release-Label Publisher to "Release Publisher" and Work-Label Publisher to "Song Publisher"

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • Relationships
    • None

      Currently both are referred to in the UI as "publisher".

      The disambiguation would be especially useful for "Frankenstein" Labels which are a combination of several different legal entities, e.g. Lantis:
      https://musicbrainz.org/label/51a22f67-8bbd-473e-b4af-2e60efebe150/relationships

      which has 2 distinct "published" sections.

      Release-Label:
      "publisher" -> "release publisher"
      "published" -> "published release"

      Work-Label:
      "publisher" -> "work publisher" or "music publisher"
      "published" -> "published work" or "published music"

      I don't think this should require an RFC/RFV unless the wording is objectionable.

          [STYLE-275] Rename Release-Label Publisher to "Release Publisher" and Work-Label Publisher to "Song Publisher"

          Rechecked this, and with the icons anyway it's very obvious what the different sections are, so there doesn't seem to be a need to rename anything.

          Nicolás Tamargo added a comment - Rechecked this, and with the icons anyway it's very obvious what the different sections are, so there doesn't seem to be a need to rename anything.

          Yes, I think it being split came after this (with MBS-4151 linked in the comments above). Additionally, it now also has the entity type icons by the entities, as well, which kinda makes it more clear whether something is a work, a release or a recording.

          I wouldn't be against renaming the publishing rels if need be, but that's not so much a case where it is confusing because of our UI, but a case where it is confusing because the industry calls different things the same way :/

           

          Nicolás Tamargo added a comment - Yes, I think it being split came after this (with MBS-4151 linked in the comments above). Additionally, it now also has the entity type icons by the entities, as well, which kinda makes it more clear whether something is a work, a release or a recording. I wouldn't be against renaming the publishing rels if need be, but that's not so much a case where it is confusing because of our UI, but a case where it is confusing because the industry calls different things the same way :/  

          Dan added a comment -

          although this appears to be split out (maybe it wasn't in 2013, I don't know wasn't using the site back then!) on the relationships page a bit better now it still isn't overly clear which "published" is which.

           

          Good example would be Warner/Chappell's page

          https://beta.musicbrainz.org/label/1a0ef599-bb5c-4dfa-9a8c-078f77dee133/relationships

          Dan added a comment - although this appears to be split out (maybe it wasn't in 2013, I don't know wasn't using the site back then!) on the relationships page a bit better now it still isn't overly clear which "published" is which.   Good example would be Warner/Chappell's page https://beta.musicbrainz.org/label/1a0ef599-bb5c-4dfa-9a8c-078f77dee133/relationships

          nikki added a comment -

          Oh, you but mean update the link phrases. In that case it should go via the style list anyway.

          Personally I'd rather we just fixed the interface (which I suppose comes under MBS-4151) rather than adding entity types to the link phrases to compensate for a bad interface.

          nikki added a comment - Oh, you but mean update the link phrases. In that case it should go via the style list anyway. Personally I'd rather we just fixed the interface (which I suppose comes under MBS-4151 ) rather than adding entity types to the link phrases to compensate for a bad interface.

          nikki added a comment -

          This isn't anything to do with the server code, so I've moved this to style.

          I've been told previously that we're not allowed to rename relationships though, so it's possible that this is a won't fix.

          nikki added a comment - This isn't anything to do with the server code, so I've moved this to style. I've been told previously that we're not allowed to rename relationships though, so it's possible that this is a won't fix.

            Unassigned Unassigned
            yindesu yindesu
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package