Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comp objects need to know what state they're in #19

Closed
jmacdotorg opened this issue Jan 20, 2014 · 2 comments
Closed

Comp objects need to know what state they're in #19

jmacdotorg opened this issue Jan 20, 2014 · 2 comments
Assignees
Milestone

Comments

@jmacdotorg
Copy link
Member

Where possible states include:

  • Nascent (hasn't started accepting entries yet)
  • Open (accepts entries and prizes)
  • Begun (accepts votes and prizes)
  • Prizing (judging is done, but not all prizes have been assigned to authors yet)
  • Over (is all done)

Plus these meta-state:

  • Active (in the state of either 'open' or 'begun')
  • Inactive (not 'active')

And there needs to be a "fetch the active comp" method on the comp resultset, which will return 0 or 1 comp objects.

@ghost ghost assigned jmacdotorg Jan 20, 2014
@jmacdotorg
Copy link
Member Author

I reckon that the best way to do this involves adding date columns to the database.

@taskboy3000
Copy link
Collaborator

Agreed. I would use simple datestamps for each each event.

Active/Inactive may be helper routines to look process the DB values but shield the details of implementation from the caller.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants