Comments on: Introducing Project Rosetta Stone

By: Amsterdam Music Hack Day « Music Machinery

Amsterdam Music Hack Day « Music Machinery — Sat, 24 Apr 2010 16:28:20 +0000

[...] New Java and Python clients that let you access all of our features (such as Rosetta Stone) [...]

By: JustSomeOldJoe

JustSomeOldJoe — Sun, 07 Mar 2010 05:58:35 +0000

Finally someone in the online music biz gets a clue and works on defining an external ID mapping structure and capturing said mapping data. Should work well with well defined and structured data sources i.e. Musicbrainz. However, could be a bitch when it comes time to implement “commercial services.” Most of the commercial service back end implementations I’ve seen wouldn’t know consistency if it hit ‘em upside the head.

It’s ridiculous that nothing exists for music akin to the Library of Congress LC# system used for written works.

Good luck to you!

By: Lucas Gonze

Lucas Gonze — Fri, 12 Feb 2010 18:19:23 +0000

Really good idea for a service. It makes sense for the Echonest mission, and it’s a valuable resource for many different companies. It makes zero sense for Myspace/Yahoo/ad infinitum to build the mapper for themselves.

By: Echonest ID mapping service — Lucas Gonze’s blog

Echonest ID mapping service — Lucas Gonze’s blog — Fri, 12 Feb 2010 18:18:15 +0000

[...] Echonest has released a web service for mapping music identifiers across namespaces. [...]

By: Paul

Paul — Fri, 12 Feb 2010 11:39:07 +0000

Tristan:

You’ll be able use our get_profile call as a mapping service. Give the method an ID in any supported name space and ask it to return IDs in other name spaces.

Paul

By: Tristan

Tristan — Fri, 12 Feb 2010 09:56:32 +0000

Very useful. Will you be opening up the ID mapping service as a separate thing or is it just supporting the ability to use non-Echonest IDs in Echonest API calls?

By: Ben

Ben — Thu, 11 Feb 2010 16:06:00 +0000

This is excellent news! Though I must admit I wish it was up during the Stockholm Music Hack Day. That said, Mike and I will do a bit of reconfiguring to use this call instead of the chained calls via pyMBZ…