Page Comparison

...

1. Create a Synapse Competition
   1. Fill in details, attach relevant Synapse entities
   2. Specify access requirements
   3. Specify open/close dates
2. Listen for Submissions (using messaging service)
   
   1. Download unscored Submissions
   2. Perform scoring
   3. Push scores back to each SubmissionStatus
3. Track user participation and publish competition status/leaderboard
4. Award achievements for user participation / success

Planned Additions

We plan to include the following features in the The following Competition Services , but these features have features are planned but not yet been implemented.

• Banned user lists
  Banned users should be prohibited from participating in one or more Competitions, and any Submissions by a banned user should be isolated from the general populations of Submissions.
• Customizable Amazon Simple Notification Services messaging tools
  Competition administrators should have tools to configure a selective Amazon instance to listen for messages pertaining to Competitions which they own. These messages should be sent to a queue dedicated to Competitions.
• Immutable copies of the submitted Entities
  Once an Entity is submitted to a Competition, a static copy of that Entity should become the property of the Competition administration.
  
• Administrator lists for Competitions
  Competitions should support administration by multiple users (rather than just the Competition owner). These admin lists should function as a lightweight ACL of sorts.
• Multi-author Submissions
  Competitions should support team Submissions, where more than one Synapse user claims authorship of a given Submission.