The contest, as it stands, is unorganized, weakly structured, and unintuitive. A contest is 4 steps and should be programmed to represent these four steps. By refactoring the model, errors in a step will fail much more gracefully and running a contest will be more intuitive.
Contest steps:
Start: Server is to vote on samples grabbed from the google drive folder
Vote-End: Votes have been cast and top three samples are displayed
Allowing people to opt into event might be a good idea to keep track of entries a bit better
Event-Start: (this happens immediately following vote-end, may be better to merge) Event is underway, Submissions folder is created and accepting uploads. Force naming of files [producer-tag]-[song-title].[ext] in document. Maybe notify those who have uploaded file incorrectly
Event-Vote: Submissions are closed and a vote is started from previous week's submissions
Event-End: Top 3 is announced with a congratulations to first place
The contest, as it stands, is unorganized, weakly structured, and unintuitive. A contest is 4 steps and should be programmed to represent these four steps. By refactoring the model, errors in a step will fail much more gracefully and running a contest will be more intuitive.
Contest steps: