Schema/API Design Comments (Josh Queja)

[jqueja]

1. Since Playlists are tied to users, perhaps it can be the other way around where the playlists are connected to the platform. Just so you can listen to all different types of music elsewhere.

2. Seems like the API spec and the ER diagram is slightly a little off. The Artist is an int compared to a string.

3. In the ER diagram, there is something called the isrc_number, which I'm not sure what it means

4. Playing a specific song or starting the playlist in a certain spot of the playlist.

5. Creating a public and or private playlist in which only or other people can add to it.

6. Having the ability to reach out to other platforms while checking if its a valid site and can play music.

7. Deleting a user is a serious operation and should not be taken lightly. Having first time generated keys that can be in the database so the user can write them down to delete.

8. Having a username when signing up would be great, rather than an unique id

9. It seems to me that there is no check to see if the song already exists before you add it.

10. Are Songs supposed to be unique or is the link going to the song supposed to be unique. What if I added two songs that are the exact same but on two diff platforms?

11. There is nothing getting returned when I try to add a song to a playlist

12. Creating a function that views all of the songs in a playlist would be beneficial.