Stevies Implementation

[carlosdp]

The "Stevies" are Scotch's version of achievements (a clever play on our good 'ol Stephen Schwartz's name).

These are achievements based on things like having directed a show or been on 5 consecutive production staffs / casts. There are several tasks involved here:

• [ ] Design the data model. We need something that will be dynamic and allow efficient checking for achievement completion.
• [ ] Collect awards. We need a list of Stevies to launch with. For this, we will also need to do a little data analysis to figure out quantity. At launch, we will want everyone involved in things to have at least one and some average award per member.
• [ ] Design graphics and interface. We will need icon graphics for the awards which means we will need the list at this point. We also need to decide where these awards are displayed.

Discuss!

[achivetta]

One interesting thing to think about: the action that causes someone to get an award isn't likely to be taken by the person getting the award. So, you'll use some sort of persistent notification to tell the user about their new award. So, the process of detecting and granting awards can be totally asynchronous: delayed task, cron job, whatever.

So, two tables:

Awards

• ID
• name
• description
• image
• etc

PersonAwards : many-to-many between your people and awards.

Then, there's no need to define the awards in your model, just write a function/class for each award that answers the question: has person X earned you?

If you want to use a cron job, you can run each award's detector across all members who haven't earned the award yet.

If you want to use deferred tasks, any time an action happens that could change a member's awards, queue up evaluating all awards for that members.

[carlosdp]

Right, I was thinking deferred tasks based on triggers at the group/show level. ie. when a show is archived, everyone in the show is checked for eligibility.