Scrum Report 2023-08-10

[wgervasio]

Describe (for the project):

Quote from course staff: REQUIRED - Scrum report 6. A final wrap up scrum report to talk about what you did in the last two weeks, and what you would hypothetically work on if you were to continue on the project.

csid:

(1) what you’ve worked on in the previous two weeks,

(2) what you’ll be working on in the next two weeks, and

(3) where you might have gotten stuck during the last two weeks.

These should be quite short (a sentence for each of the three items above).

[leoxyu]

csid: z5z2b

(1) what you’ve worked on in the previous two weeks, Fixing youtube auto import for updated schema, song page, some UI and presentation prep

(2) what you’ll be working on in the next two weeks, and the course is finished, but I would implement a graph for song page that relates songs based on the various properties that are stored.

(3) where you might have gotten stuck during the last two weeks. n/a

[wgervasio]

csid: s0m3b

(1) what you’ve worked on in the previous two weeks,

• pagination of search engine. preview playlists from search page. preview albums from search page. play playlists from search page. play albums from search page. optimization of search engine fetching. migrating metadata annotation to other module. history module for song listening. ml recommendation system using history module results. navbar overhaul in styling. moved songs page to playlist page.

(2) what you’ll be working on in the next two weeks, and

• course is done but what I would do in the next weeks is create an ETL pipeline and polish up the UI. Maybe create a separate flask backend for ML and set up another server.

(3) where you might have gotten stuck during the last two weeks.

• the ml algorithm was really hard considering we have no sample output results so coming up with a viable unsupervised algorithm using JavaScript and not python was a challenge. Also there was no metadata from search pushed to the databases so I had to manually come up with a different way to annotate all data with metadata relevant to song suggestion.

[Ning114]

csid: c9x2b

(1) what you’ve worked on in the previous two weeks

• helped iron out final UI bugs
• implemented the currently playing page
• implemented the lazyLoad function for the currently playing page

(2) what you’ll be working on in the next two weeks, and

• debugging lazyLoad for currently playing page since it was broken during a merge

(3) where you might have gotten stuck during the last two weeks.

-n/a

[moseshsu01]

csid: t8v2b

(1) what you’ve worked on in the previous two weeks, Implement favouriting, fix UI for player, editor, navbar, options, page selector, clean up code for entire codebase, debugging spotify player.

(2) what you’ll be working on in the next two weeks, and I would implement liking and look into other options for playing spotify songs.

(3) where you might have gotten stuck during the last two weeks. I spent way to long debugging why the spotify player would sometimes not work, only to determine that it was a browser issue and that it was out of our control

[AlexZhou876]

csid: n4z2b

(1) what you’ve worked on in the previous two weeks, infinite scroll, clicking into playlist page, player/playlists redux changes, performance optimization for playlists page mainly lazy loading of songs within playlists (only load when playing or navigating to single playlist page)

(2) what you’ll be working on in the next two weeks, and I would like to implement discoverability of other users' unifi playlists, public/private playlists, server side playlists filter/sort, server side song page queries, UI success/fail notifications for importing.

(3) where you might have gotten stuck during the last two weeks. Spent a lot of time fine-tuning the infinite scroll behaviour and performance optimizations