Fetching ISRCs from Spotify

[Freso]

@tigerman325

Is there anyway to add release date?

Please don’t add release dates based on Spotify’s data alone. See my comment elsewhere:

@Freso

I’ve found Spotify’s release dates to be pretty hit and miss. For most current/modern releases (where digital and physical editions are released simultaneously (if they have a physical manifestation!)), it will likely be correct, but Spotify stores the oldest release date, and it’s unlikely that a digital media online streaming album was released in, say, 1978… (This is also the reason my importer—that this topic is about—doesn’t include release date information.)

[tigerman325]

Oh, yeah, totally agree with that.

[jesus2099]

@tatsumo

alpha version of a Spotify-powered tool

Hi @tatsumo.
Could you add some nice column headers to your table because we were wondering what some columns they mean, lately in this edit…

Spotify track title	Spotify ISRC	MusicBrainz recording	Whatnot
Bla bla	FRSD112345	Bli Blu	2.099

[Jeluang]

Isn’t that the amount of seconds it conflicted with the length of the track in the release on MB?

[tatsumo]

Yeah that’s coming very soon. Just been on holidays for a while.

[Jeluang]

Trying to input the ISRC from this album https://tatsumo.pythonanywhere.com/album/5Eh4g0AuSoFT5xc0vOG324 will display the following error message.

ISRCs must be in valid ISRC format
For usage, please see: MusicBrainz API - MusicBrainz

I’m guessing because the ISRC format used for the tracks have hyphens, e.g. GB-SMU-23-99532

[outsidecontext]

@Jeluang

I’m guessing because the ISRC format used for the tracks have hyphens, e.g. GB-SMU-23-99532

When entering enter them without the hyphens. Those were just added for readability.

[Jeluang]

I mean I can’t push the ISRCs to MB directly from the album view as it will display the error message. I know that the hyphens aren’t necessary when putting it in the recordings.

[tatsumo]

Yeah this isn’t going to get fixed. I’ve never seen this happen on any other release, so as simple as it would be, it’s still not worth the effort.

Additionally, I would say that having given Spotify ISRCs formatted like this, should raise question marks about the data quality, and think it’s a better idea to add another manual step to their submission.

I’ll look into adding something to prevent it trying to submit ISRCs that look invalid though.

[jesus2099]

Just to say this format is completely valid per ISRC specs and MB could accept them.
I think it does accept them in the web form.

[jesus2099]

How do you batch submit btw, I think my bookmarklet recognises this format and strips the hyphens down, but not sure.

[tatsumo]

Is it? I’ve never seen this in any other context, except ones that are constructed precisely to explain the structure of an ISRC.

In that case, I won’t make any change. I’ll allow the hyphenated ones to try to generate an edit. Because if the format is valid, the issue is that MB server rejects them, not that the tool doesn’t reformat them to what wants — if indeed this is a fully valid presentation of ISRCs.

[jesus2099]

I thought so but apparently « The hyphens are not part of the ISRC code itself, but codes are often presented that way in print to make them easier to read. » according to MB wiki and WP and their references.
But I confirm that if you paste a bunch of ISRC with or without hyphens in MASS ISRC and bookmarklet, it will detect them (and submit without hyphens, I think).

[tatsumo]

A few smaller under the hood updates were made yesterday. One somewhat bigger one, is you can now paste (almost) any Spotify link into https://tatsumo.pythonanywhere.com/auto and it should take you to the page – to save you (mostly to save me) manually rewriting the URL. This also supports track links, which it will resolve to its parent album, and redirect there.

It should be able to handle ignoring query strings as well, most often the ?si=[blahblahblah], that Spotify appends to shared URLs a lot.

[Lotheric]

Submission to MusicBrainz (pasting an MB URL) stopped working recently and we get a message (https://blog.metabrainz.org/2018/02/01/web-service-ver-1-0-ws-1-will-be-removed-in-6-months/)

[tatsumo]

I’ll work on that but it could be a few weeks

[Lotheric]

I was just reporting the issue

Thank you for looking into it. Your tool is very handy!

[tatsumo]

I will probably work on this this weekend, but I can’t reproduce this message. Submission continues to work for me.

I’m in the middle of a rewrite of how the album view renders, so it’s a good time to port the submission API to v2.

[Fabe56]

Thanks @tatsumo, I only discovered your tool this week. If that can help, like @Lotheric I got the same message when I try to submit to MB (try with Vivaldi and Edge browser).

[tatsumo]

I managed to get it now. But not every time. I believe if you retry the submission it should go through, at least sometimes