-
Notifications
You must be signed in to change notification settings - Fork 0
TODOs
List of TODO in the Music Graph Explorer project, in no order of priority:
-
Create a client library for the web service, and handle calling the local endpoint in debug mode from within the library
-
Create a base
GetArtistResponseBaseandGetGenreResponseBaseclass that other response data contract classes can inherit from -
Speed up search API with a proper index
-
Bug: why is artist relevance within artist > 1? For instance, search for Artist = Soundgarden
-
exception processing and return Http Errors in the API webservice
-
ArtistDetail page in website UI - asynchronously load artist, related artists, and images of the related artists
-
Allow testing the website UI against a local API or the prod API, based on configuration setting
-
Develop worker service for all computes, and host them on Azure
-
build an http client to the web service
-
Compute Artist relevance within a Genre.
-
Add
Artistrelevance within aGenrein theDataAccess.GetArtistForSpotifyIdmethod. This can only be done once we compute Artist relevance within a genre. -
Add
Artistrelevance within aGenrein theDataAccess.GetAllArtistsForGenresmethod. This can only be done once we compute Artist relevance within a genre. -
Make GraphStore.Write multi-threaded for multi-threaded writes. This may require to make Artist and Genres thread safe and use
ConcurrentBaginstead 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. -
Find a way to implement full text search to search artists and genres by name
-
Create test for web service APIs
-
add settings to tests
-
read the list of seed artists from a settings file