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

Standardise and validate Spotify URLs

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2017-02-13
    • Component/s: URL cleanup
    • Labels:
      None

      Description

      It seems that Spotify has gone https-only. Right now we accept both http and https, we should make it change http to https.

      There are two subdomains being used now, open.spotify.com and play.spotify.com. Actually open.spotify.com is preferred over play.spotify.com as it is more versatile. Spotify user settings allow to redirect from open.spotify.com to play.spotify.com.

      Both URL parameters (e.g. ?play=true&utm_source=open.spotify.com) and fragments (e.g. #top) are unnecessary and should be removed.

      Right now, there's no validation done to make sure the URL matches the entity type. There are three main types of URLs, /artist/, /album/ and /track/, which should correspond to artist, release and recording.

      Typical URLs:

      URLs which should get cleaned up:

      Other examples from the database:

      I've made a list at http://reports.mbsandbox.org/report/290/view of URLs which don't match the regex '^https?://(open|play).spotify.com/(artist|album|track)/[A-Za-z0-9]

      {22}

      $' if more examples are needed (I'll wait until this is done before fixing them).

        Attachments

          Activity

            People

            • Assignee:
              yvanz Yvanz
              Reporter:
              nikki nikki
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: