Introduction - kristinedomingo/cs373-idb GitHub Wiki

##Problem

A study performed in 2011 by the United States Bureau of Labor and Statistics reported that there were about 67,000 people that denoted their occupation as a musical performer or composer. This number is a rather conservative estimation of the amount of musical talent that actually exists in the US. If we begin to think at a global scale this number grows exponentially. Assuming that each one of the aforementioned artists creates 2 albums and produces 2-4 music videos we arrive at a large number, but yet still a wildly conservative estimation of the musical content and information on the internet.

Enter SWEet Music, a service that combines some of the most content rich APIs on the internet to pull and organize this mountain of data in a way that is insightful and informative.

##Use Case for Clients Imagine that you are out in the city during SXSW and you have just attended a impromptu show by an artist that one of your friends had suggested. You loved the atmosphere, the venue, and most importantly the music.

Where do you go to find out more about the artist's work, bio, or upcoming events?

Maybe you check Spotify to hear his or her work and then check the artist's website for news, information, or tour schedule. This quickly digresses into a string of searches to find information that is now precious to you.

We at SWEet Music are here to simplify this process by consolidating all the information that you could ever want to know about your new-found favorite artist, favorite jams from your childhood, to everything in between! We accomplish this by bringing together rich content into single place to be your one-stop-shop for everything music.

##Use Case for Developers

SWEet Music's philosophy towards development is no-frills. As we scoured the web searching for content on different artists, we realized that there was a lot of information that was not relevant to us as developers nor to our clients.

####Our solution Combine data from some of the best music data sources on the web (Spotify, EchoNest, etc.) and to provide endpoints that sum up the information that we deemed valuable for clients and developers. Additionally, we remained flexible in keeping some information that is important (ie spotify uri) for making api calls to some of the aforementioned data sources.

Ultimately, we believe by taming down the vast amount of music data available while keeping unique identifiers from other data sources that we become not only a one-stop-shop for clients but also for developers looking to utilize all types of data on music.