Skip to content
pmartin7 edited this page Apr 25, 2017 · 25 revisions

List of TODO in the Music Graph Explorer project, in no order of priority:

  1. Create a client library for the web service, and handle calling the local endpoint in debug mode from within the library

  2. Create a base GetArtistResponseBase and GetGenreResponseBase class that other response data contract classes can inherit from

  3. Speed up search API with a proper index

  4. Bug: why is artist relevance within artist > 1? For instance, search for Artist = Soundgarden

  5. exception processing and return Http Errors in the API webservice

  6. ArtistDetail page in website UI - asynchronously load artist, related artists, and images of the related artists

  7. Allow testing the website UI against a local API or the prod API, based on configuration setting

  8. Develop worker service for all computes, and host them on Azure

  9. build an http client to the web service

  10. Compute Artist relevance within a Genre.

  11. Add Artist relevance within a Genre in the DataAccess.GetArtistForSpotifyId method. This can only be done once we compute Artist relevance within a genre.

  12. Add Artist relevance within a Genre in the DataAccess.GetAllArtistsForGenres method. This can only be done once we compute Artist relevance within a genre.

  13. Make GraphStore.Write multi-threaded for multi-threaded writes. This may require to make Artist and Genres thread safe and use ConcurrentBag instead of list. In order to do parallel writes, we will need to use multiple instances of dal. Have to decide whether the right architecture is to spin multiple instances of the GraphStore.Write application working of a single queue.

  14. Find a way to implement full text search to search artists and genres by name

  15. Create test for web service APIs

  16. add settings to tests

  17. read the list of seed artists from a settings file

Clone this wiki locally