Scrum Report - Workshop 4

[JeromeTing]

What did you work on this past iteration (2 weeks)? What were any major issues/challenges you ran into? What do you plan to work on for this coming iteration (2 weeks)?

Include your CSID in your post.

[Parmvir-S]

Scrum Update - Parmvir Shergill (CSID: q3l6c)

1. What did you work on this past iteration (2 weeks)?
   I setup the MongoDB database on Atlas and inserted a LikedSongs collection. I linked the song liking code with the database. When a user likes a song that is already in the LikedSongs collection then that songs like count gets incremented. If the liked song isn't in the LikedSongs collection then it simply gets added to the collection with its likes count set to one. I also linked the LikedSongs with the scoreboard which shows songs from most liked to least liked. Pagination is also setup now showing just 5 songs per page.

2. What were any major issues/challenges you ran into?
   I ran into some challenges getting the environment variables to load into the files that used them. While developing I used a work around with env-cmd but managed to get it to work after some tinkering with the settings.

3. What do you plan to work on for this coming iteration (2 weeks)?
   In the upcoming iteration, we will be discussing what we want to work on next. We are thinking about implementing public playlists that users can add to and view but nothing is set in stone just yet. We have identified some bugs and UI issues that we will address in this upcoming iteration as well.

[JeromeTing]

Scrum Report (Jerome Ting - CSID: k3a0b)

1. What did you work on this past iteration (2 weeks)? I primarily focused on getting the globallySearchedSlice up and creating the backend API for that request and ensuring it showed up in the globallySearched carousel. Some of the API design choices were iterated on as we also chose to implement the database as well (for example we initially had our own version of the endpoint, but later decided that it's best to copy the json layout that was provided to us by the Spotify API which ensures less coupling).

2. What were any major issues/challenges you ran into? The major challenges for my tasks were just the clarity and fine-grain details of how we wanted to implement the reducer (and also future proof it for the database). That was resolved with our meetings and talking about what we wanted it all to look like.

3. What do you plan to work on for this coming iteration (2 weeks)? For the next iteration, we plan to review our current goals and evaluate which (and if any) of the stretch goals makes sense to where we currently are in terms of the project. We also want to look into deployment as well as polish up any issues we have (bugs, error handling etc).

[KDhieb]

Scrum Update - Khalid Dhieb (CSID: h2w7b)

1. What did you work on this past iteration (2 weeks)? I worked on some of the Redux for the search component and connecting our frontend to the backend ML server. Also did some small bug and UI fixes.

2. What were any major issues/challenges you ran into? Most challenging was connecting the frontend to the ML server. Also had to deal with an issue where our express server was clashing with our ML server, so I had to change our express server ports.

3. What do you plan to work on for this coming iteration (2 weeks)? I will help my team evaluate which goals to prioritize going forward as our project is near completion. Will help with polishing up the project as well.

[rrichc]

Scrum Update - Richard Chen (n4z2o)

1. What did you work on this past iteration (2 weeks)? Implementation of the machine learning pipeline using scikit-learn in jupyter notebooks training Kmeans & Knn models. Creation of a Flask backend with POST endpoint to accept requests for song recommendations based on a data from an input song.

2. What were any major issues/challenges you ran into? Trying to develop a pipeline that made sense given the dataset we had. It took some effort to devise a way to correlate data points returned from the Knn model back into song ID's .

3. What do you plan to work on for this coming iteration (2 weeks)? As we've completed our minimal and standard requirements, we are re-evaluating which stretch requirements we can feasibly finish by the term's end. It's likely we will focus on polishing things up like optimizing the ML model, error handling, etc

[aalchen]

Amy Chen (c9p6e)

What did you work on this past iteration (2 weeks)? I was building off of the GloballySearched components that Jerome worked on (using dummy data), and hooked up that component to the MongoDB database that Parm had set up. I created a separate GloballySearchedSongs collection, and adjusted the front-end and server/API logic to use the database instead. I also did code reviews to identify bugs, and performed adjustments on my PRs based on feedback as well.

What were any major issues/challenges you ran into? A major challenge involved learning how to use MongoDB again, as I had not used it in a long time, but with the appropriate documentation and research I was able to get the existing codebase to perform what was needed for our particular needs.

What do you plan to work on for this coming iteration (2 weeks)? I plan to work further with our team to discuss what other bugs, UI improvements, and other possible stretch goals we can work on, as otherwise we have largely already completed our minimal and standard requirements.