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

Style guidelines for Places

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Normal Normal
    • Next!
    • None
    • Guidelines
    • None

      (This was spurred by discussion at https://musicbrainz.org/edit/40794845)
      Some related discussion on Discourse: https://community.metabrainz.org/t/when-a-place-is-no-longer-a-place/114747

      Currently we have no style guidelines for Places. Here are a few suggestions:

      • The name should be the current name of the Place; if the Place no longer exists, the last name it had before closing should be used. All previous names should be entered as aliases, with begin and end dates, if available. Do NOT create duplicate Place entries for past names.
      • The address should be the full address, including ZIP/postal codes. Do not include the country in the address.
      • If a Place has relocated, a new entity should be created. If the same name was used before and after the move, date and location information should be added in the disambiguation comment box for both entities.
        • Example: Charlotte Coliseum (now known as Bojangles' Coliseum) moved and became Charlotte Coliseum. The older Place has the disambiguation "known as Charlotte Coliseum until 1988" and the later Place has the disambiguation "1988-2005."
      • If a Place still stands but is no longer used for its purpose as a Place, it should be marked as "ended" with the name set to the last name it had before closing.
        • Example: Cobo Arena is technically still in existence as part of Cobo Center, but it is no longer an arena (it was remodeled into additional convention space).
      • If a Place is demolished or destroyed and rebuilt on the same site, a new Place entity should be created.

            reosarevok Nicolás Tamargo
            hibiscuskazeneko HibiscusKazeneko
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                Next!