New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Genres are not returned for albums #157

Closed
RocketCity opened this Issue Jan 24, 2016 · 21 comments

Comments

Projects
None yet
@RocketCity
Copy link

RocketCity commented Jan 24, 2016

The list of genres for an album is always empty: confirmed in the Web API Console for "Get an Album" -- I tried it in code for hundreds of albums and none return a genre.

@holmberd

This comment has been minimized.

Copy link

holmberd commented Jan 26, 2016

Get an artist endpoint seems to be the only endpoint that returns genres for some artists.

@aljondo

This comment has been minimized.

Copy link

aljondo commented Jan 29, 2017

This is a problem for me too, is it going to be fixed soon?

@AltroozTodd

This comment has been minimized.

Copy link

AltroozTodd commented Feb 16, 2017

+1

@gaurav183

This comment has been minimized.

Copy link

gaurav183 commented Apr 19, 2017

Any updates? +1

@holmberd

This comment has been minimized.

Copy link

holmberd commented Apr 19, 2017

We don't have weights for artists genres because that information isn't available to us, and genres are so subjective that the value of such a weighting would be limited.

Why is this considered a bug? When Spotify aquired EchoNest, which had endpoints for this kind of data, they should have gained access to all the genres available from that service.

@jpmurray

This comment has been minimized.

Copy link

jpmurray commented Sep 10, 2017

I know it's bad practice, but I'll just add me voice to this, to at least to get notified of any updates on the matter.

Now, if the genres aren't supposed to be exposed on the album object, you might as well remove it. (I'd rather them to be there though!) Seeing that someone said in #31 that we should be able to get them by album, it really seems like a bug. And a long standing one at that :(

That being said, I'm adding also my voice to @holmberd on this one. If I remember correctly, EchoNest also had genre data to the track level, it's weird we can't access the data anymore. If I may add, in the linked issue above, we're said that Spotify doesn't expose the track level genre data, but it doesn't seems it's not there. This kind of information in invaluable to some, and I'd honestly be willing to pay to access an API that gives me track genres (since it seems no current api are willing to do so!).

@goldensunliu

This comment has been minimized.

Copy link

goldensunliu commented Sep 27, 2017

@thelinmichael since you no longer work at Spotify. Could you help point us the right person in terms of the most up to date information regarding the web api endpoints?

@davidgibsonp

This comment has been minimized.

Copy link

davidgibsonp commented Oct 23, 2017

+1

9 similar comments
@michelle-chiang

This comment has been minimized.

Copy link

michelle-chiang commented Dec 3, 2017

+1

@rosem1696

This comment has been minimized.

Copy link

rosem1696 commented Feb 1, 2018

+1

@fredericklu

This comment has been minimized.

Copy link

fredericklu commented Mar 18, 2018

+1

@ssemenova

This comment has been minimized.

Copy link

ssemenova commented Mar 19, 2018

+1

@sureshHARDIYA

This comment has been minimized.

Copy link

sureshHARDIYA commented Apr 10, 2018

+1

@ju-popov

This comment has been minimized.

Copy link

ju-popov commented Apr 21, 2018

+1

@grahamalama

This comment has been minimized.

Copy link

grahamalama commented May 28, 2018

+1

@Rawnly

This comment has been minimized.

Copy link

Rawnly commented May 30, 2018

+1

@travisR004

This comment has been minimized.

Copy link

travisR004 commented Jun 5, 2018

+1

@jpmurray

This comment has been minimized.

Copy link

jpmurray commented Jun 6, 2018

PEOPLE. Stop saying +1, it's only spamming previous commenters and it's, obviously at this point, not going to motivate anyone from this repo to act on it! Use reactions on original post!

@arirawr

This comment has been minimized.

Copy link

arirawr commented Sep 21, 2018

Hey all,

As per our new developer support process, any issues that have no plans to be considered in the next 6 months will be closed as wontfix.

We do not have any plans to implement this in the next 6 months and thus will close as wontfix.

We encourage you and other members of the community to continue to share use cases and your support for this feature, as it helps us prioritize features going forward. You will be able to comment on this issue even after it is closed. We will also post any updates here relating to this suggestion when they happen.

@arirawr arirawr closed this Sep 21, 2018

@arirawr arirawr added the wontfix label Sep 21, 2018

@jpmurray

This comment has been minimized.

Copy link

jpmurray commented Sep 21, 2018

@arirawr it is, at minimum, possible to get the reasoning? I mean, if it's not possible within 6 month, is it because at the start you don't have the information, or is it because you're not planning to share the information?

This gives us a good idea if what we want to do is actually possible or not.

@shillshocked

This comment has been minimized.

Copy link

shillshocked commented Oct 26, 2018

Bump!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment