You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion the following feature is essential and might have a severe impact on the file structure. Therefore I suggest that we address it in an early stage:
Karman should also have a possibility to save whether or not a song is "good" or rather "tested".
This way you could upload your current song library / give external users access to upload songs without worrying too much which songs are good enough.
Furthermore this way the work of testing songs can be split up, since everyone with a browser (and permissions) could test the song and it's not depending on one user who might have a lot of songs he/she wants to upload.
In addition to that I would wish for two ways to check this status:
A list of trusted persons / administrators who are allowed to set the state of a song (done, needs attention, unplayable, ...)
A rating system where anybody could give a 1-5 star rating and maybe a comment on what could be approved.
The point, which makes it file structure breaking, would be my proposal, that the file state should somehow be reflected in the file structure. This way you could easily download only the "good songs".
Furthermore a history of all edits / state changes should be saved. However, this implementation should be easy
The text was updated successfully, but these errors were encountered:
From #3: I would suggest more details to the verification. I would some kind of state and maybe multiple users could set different states or approve states from other people? This needs more thought...
In my opinion the following feature is essential and might have a severe impact on the file structure. Therefore I suggest that we address it in an early stage:
Karman should also have a possibility to save whether or not a song is "good" or rather "tested".
This way you could upload your current song library / give external users access to upload songs without worrying too much which songs are good enough.
Furthermore this way the work of testing songs can be split up, since everyone with a browser (and permissions) could test the song and it's not depending on one user who might have a lot of songs he/she wants to upload.
In addition to that I would wish for two ways to check this status:
On how we track broken songs, see #6
The point, which makes it file structure breaking, would be my proposal, that the file state should somehow be reflected in the file structure. This way you could easily download only the "good songs".
Furthermore a history of all edits / state changes should be saved. However, this implementation should be easy
The text was updated successfully, but these errors were encountered: