SRS Copy
==
## Seasonal GTS setup
|Attribute |Value
|------------|-----
|Actor |Campaign admin
|Description |The extension of the GTS concept, where matches are presented as mini GTS campaigns within a single logical campaign with aggregated leaderboards in the live app.
|Priority |Essential
### Fit criteria
1. Seasonal GTS campaign type is available in the campaign list.
2. The configuration steps include (attributes required, unless marked as optional):
1. A list of matches, each with:
1. Match date
2. Guessing start date (optional)
3. Guessing end date (optional?)
4. Home team
5. Away team
6. Post Participation Action
2. Defining prizes and assigning them:
1. As main prizes.
2. As prizes of for a particular match.
3. Enforcing enabling `Nickname` in auth options (used to display top participants in live app).
4. Top lists configuration ==OUT OF SCOPE FOR NOW. This will probably be added later==
1. Show all participants/Show X participants in lists
2. Default: Show all participants in lists
3. Default value for X is 10 ==This value will be used showing lists in live app==
### Designs
**Wizard** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f290fe36014322057c306bc)
<a href="https://i.imgur.com/wJJRojX.png" style="padding-right:200px;">Behavior (Empty)</a><a href="https://i.imgur.com/6DX2EY6.png">Behavior (Creating)</a>
 
<a href="https://i.imgur.com/QadWRse.png" style="padding-right:200px;">Behavior (Filling)</a><a href="https://i.imgur.com/59ampDq.png">Behavior (List)</a>
 
## Seasonal 1X2 live app
|Attribute |Value
|------------|-----
|Actor |Campaign participant
|Description |User gets to guess outcomes of matches. The guesses are submitted individually for each match. Also, leaderboards are displayed for top guessers globally and for each match.
|Priority |Essential
### Fit criteria
1. The live app for Seasonal GTS renders
1. Initially displayed:
1. Match that has the closest guessing end date in the future from now.
2. The match view (named `Home`) allows the user to cycle among defined matches:
1. The match is displayed by displaying `home team name`, `away team name`, `match start date` and based on state:
1. If the guess was already submitted
1. If guessing end date is not expired
1. Show two number inputs with submitted guesses so that user can edit his/her guess
2. If guessing end date is expired
1. Show guess as text
3. If match result was set:
1. The correct result is shown
2. Indicator if user guessed correct or not is shown
2. Otherwise, if date is within guessing start-end date, two number inputs are displayed so that user can submit his/her guess.
3. Otherwise:
1. If pre guessing start date
1. Show notification that guessing is not available yet
2. If past guessing end date
1. Show notification that guessing has ended for this match
2. If match result was set, show correct result
3. The `Top list` is displayed showing a list of nicknames of all participants or the X participants with the best scores, depending on configuration ==Value 10 will be used for now==
1. If configured to show only X participants
1. If logged in participant is within the top X:
1. His/her row is highlighed
2. If logged in participant is *not* within the top X:
1. His/her placing is listed at the bottom with the score
3. Fields shown in list:
1. Nickname
2. Change in position since last match
3. Score
4. The `Match top lists` view allows the user to cycle among the different match leaderboards showing all participants or the X participants with the best scores, depending on configuration. ==Value 10 will be used for now==
1. Initially displayed:
1. The `Match top list` for match with latest match date and correct score set
2. If no scores are set for any matches, empty list for match with earliest match date is displayed. ==TODO: Or should we here disable the tab link?==
2. You can only cycle among `Match top list` for matches with match result set
3. A `Match top list` is displayed showing a list of all participants or the X participants with the best scores for that match ==Value 10 will be used for now==
1. If configured to show only X participants
1. If logged in participant is within the top X:
1. His/her row is highlighed
2. If logged in participant is *not* within the top X:
1. His/her placing is listed at the bottom with the score
3. Fields displayed in list:
1. Nickname
2. Score
5. Score calculation
1. Reuse score calculation from GTS. Any way of "turning it around", so the closer you are to the correct score, the more points you get?
### Designs
#### Default template
**Live app** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f290ee9cef0152011f55a3d)
:::info
See Zeplin for latest versions of design/screens
:::
<a href="https://i.imgur.com/wfa6nd6.png">Guessing not yet started </a>
<a href="https://i.imgur.com/7qUXbQq.png">Guess </a>
<a href="https://i.imgur.com/JVugGAA.png">Submit </a>
<a href="https://i.imgur.com/fsGCUQr.png">Top list (state 1) </a>
<a href="https://i.imgur.com/kI15CJo.png">Top list (state 2) </a>
<a href="https://i.imgur.com/O8UFLac.png">Match top list </a>
#### Eliteserien
**Live app** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f290f128823b824e8c06768)
#### OBOS-ligaen
**Live app** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f290f5ef88364218c434a85)
#### Superettan
**Live app** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f290f3b16cb6324c8ee8e0f)
## Seasonal GTS overview
|Attribute |Value
|------------|-----
|Actor |Campaign admin
|Description |The overview of Seasonal GTS will include UI for entering the results of all the matches in the campaign. Custom drawing strategies are also added.
|Priority |Essential
### Fit criteria
1. The outcome of each match can be defined (home score, away score)
2. Main prizes can be drawn using drawing strategies:
1. Random among all participants (the default one).
2. Random among correct match guesses.
1. Only available if at least one match outcome was defined.
3. Among most correct guesses.
:::info
The prize is given to the participant that had the best ratio correct guessed matches/all defined matches. If multiple participants had the same ratio, randomize among them.
3. Match prizes can be drawn using drawing strategies:
1. Random among match participants.
:::info
Only participants that submitted for the given match are eligible.
:::
2. Random among correct match guesses.
3. Among most correct round guesses.
### Designs
**Overview** - [on Zeplin](https://app.zeplin.io/project/5a8c374a156b308a239eef02/dashboard?seid=5f29102ed8823b255b972137) ==NOT UPDATED==