Skip to content
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

Investigate EchoNest API integration #10

Open
toroidal-code opened this issue Jun 4, 2014 · 5 comments
Open

Investigate EchoNest API integration #10

toroidal-code opened this issue Jun 4, 2014 · 5 comments

Comments

@toroidal-code
Copy link
Member

Utilizing a music info system like Echonest will allow us to improve the overall user experience.

Things like detailed Genre, Album, and Artist information (like google music), better song recommendations, and dynamic playlists based on the user's library.

Possible questions

  • Where would we integrate this? The Rails side, and then provide the data to the client? or the client-side?
@toroidal-code
Copy link
Member Author

I'm leaning towards the rails side. We could have a create_dynamic_playlist_with(model => item) function in the PlaylistsController for example

@nickserv
Copy link
Contributor

nickserv commented Jun 4, 2014

I agree about doing this on the backend. It seems like it would be too closely tied to the models and backend logic for it to be done efficiently on the fronted.

@kristenmills
Copy link
Contributor

I server side is better for that for performance reasons.

@zellio
Copy link

zellio commented Jun 4, 2014

+1 server side - if it proves really time expensive shell it off to job threads

@toroidal-code
Copy link
Member Author

possible gem: echonest-ruby-api

@kristenmills kristenmills self-assigned this Jun 24, 2014
@kristenmills kristenmills removed their assignment Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants