Great game of Turkey: Difference between revisions
Jump to navigation
Jump to search
(known bugs fixed but not tested) |
(some bug fixes) |
||
Line 15: | Line 15: | ||
cat( | cat( | ||
"Issue #", | |||
temp$Issueid[1], | |||
":'''", | |||
as.character(temp$Issue[1]), | |||
"'''\n", | |||
as.character(temp$Issuedescription[1]), | |||
"\n" | |||
) | ) | ||
oprint(temp[ , | oprint(temp[ , c("Action", "Actiondescription", "Actionid")], include.rownames = FALSE) | ||
</rcode> | </rcode> | ||
Line 42: | Line 42: | ||
objects.latest("Op_en7421", code_name = "initiate") | objects.latest("Op_en7421", code_name = "initiate") | ||
temp <- EvalOutput(issueofday) | |||
temp <- temp[temp$Date == as.character(Sys.Date()) , ] | |||
dat <- data.frame( | dat <- data.frame( | ||
Date = temp$Date[option], | |||
Issue = temp$Issue[option], | |||
Action = temp$Action[option], | |||
User = wiki_username, | |||
Result = as.numeric(Sys.time()) | |||
) | ) | ||
Line 63: | Line 63: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your choice was successfully saved.\n") | cat("Your choice was successfully saved.\n") | ||
</rcode> | </rcode> | ||
Line 149: | Line 149: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your group was successfully saved.\n") | cat("Your group was successfully saved.\n") | ||
Line 172: | Line 172: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your seed bonus was successfully saved.\n") | cat("Your seed bonus was successfully saved.\n") | ||
Line 209: | Line 209: | ||
"\n" | "\n" | ||
) | ) | ||
oprint(temp2[ , c("Action", "Actiondescription", "Actionid")]) | oprint(temp2[ , c("Action", "Actiondescription", "Actionid")], include.rownames = FALSE) | ||
} | } | ||
Line 250: | Line 250: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your issue was successfully saved.\n") | cat("Your issue was successfully saved.\n") | ||
Line 272: | Line 272: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("The issue was also voted for with your bonuses.\n") | cat("The issue was also voted for with your bonuses.\n") | ||
Line 321: | Line 321: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your action was successfully saved.\n") | cat("Your action was successfully saved.\n") | ||
Line 343: | Line 343: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("The action was also voted for with your bonuses.\n") | cat("The action was also voted for with your bonuses.\n") | ||
Line 390: | Line 390: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your issue vote was successfully saved.\n") | cat("Your issue vote was successfully saved.\n") | ||
Line 433: | Line 433: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your action vote was successfully saved.\n") | cat("Your action vote was successfully saved.\n") | ||
Line 484: | Line 484: | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your happiness score was successfully saved.\n") | cat("Your happiness score was successfully saved.\n") | ||
Line 537: | Line 537: | ||
who = wiki_username | who = wiki_username | ||
) | ) | ||
oprint(dat) | oprint(dat, include.rownames = FALSE) | ||
cat("Your progress score was successfully saved.\n") | cat("Your progress score was successfully saved.\n") | ||
} else { | } else { | ||
Line 598: | Line 598: | ||
if(exists("actday")) actday <- combine(actday, test) else actday <- test | if(exists("actday")) actday <- combine(actday, test) else actday <- test | ||
} | } | ||
return(merge(issday, actday)) | return(merge(merge(issday, actday), allactions)) | ||
} | } | ||
) | ) |
Revision as of 15:41, 14 February 2016
Make today's decision
First, see the issue and possible actions.
Then, make the decision about today's issue.
Question
What is a good game to crowdsource citizen priorities about daily political decisions in such a way that
- it can be done using a mobile app,
- it characterises happiness of citizen groups of the decisions,
- it characterises progress of important societal values,
- it enables crowdsourcing the actual issues and actions asked?
Answer
Game results
- See the top of the page for the main questionnaire of the game. Here we present results from the game.
Setup profile
Setup your profile. Do this before you start. You may change your preferences later.
Suggest issues and actions
|
|
Vote for issues and actions
|
|
Evaluate happiness and values
|
|
Rationale
Calculations
Structure and functionalities
The content of and use of the data tables is the following:
- Issues: List of decisions to be made. A user can suggest only one issue per day. For each day, the most popular issue is taken to the game.
- Actions: List of decision options to be made. A user can suggest only one action per issue. For each time point, two most popular actions are taken to the game. However, the actions in the game may change during the day, if the rank of the issues changes.
- Issue vote: List of votes for each issue. Each user can cast a single vote either for or against an issue. The number of votes a user has equals their bonuses.
- Action vote: List of votes for each action under issues. The voting system is the same as for issues.
- Decisions: List of decisions each user makes from the actions and issues on the game.
- Bonuses: List of bonuses the users have earned during the game. In the beginning, each user has 1 bonus. You can earn bonuses if your actions suggestions gets to be played (+1) or if your issues gets to be played (+5). Every time a user makes a decision, they get +0.1 bonus.
- Happiness: Users' opinions about how much happiness an action brings to their own group.
- Values: Users' opinions about how much value an action brings to a selected group.
- Users: List of users' groups (i.e. to which group each user identifies themselves).
The functions needed are the following.
- Upload data: Take the data provided by the user or calculated. Add automatic fields, e.g. ts, user and date. Upload data to the respective table.
- Create ovariable: Download data from a table. From the data, find the unique rows with a given condition (e.g. discard previous decisions made by a user previously on the same day). Then create an ovariable with the structure needed.
- Firstuser: Check's whether user's wiki_username is found from Bonuses. If not, it is added there and 1 bonus given.
The interface codes used are the following:
- Suggest issues: Ask date, issue and description from user. Date means the date when this issue will be played. Default is today, but user can change that and suggest future issues. Timestamp (ts) come automatically. User is the wiki_username. Upload data to Issues table. No need to check previous entries. Upload user's bonus to Issue vote as number of votes.
- Show issues: Ask date (today by default) and show all issues and each one's actions listed from the most to least popular. This is necessary for suggesting actions.
- Show today's issue: Ask nothing. Show today's top-ranked issue and its two top-ranked actions. [Calculate the sum of results over all users. Show these popularity sums as the result of object popularity? Select the most popular row among a group defined by an index; use oapply to integrate over the index using which.max and pick that row only. Should this be a function or ovariable?]
- Suggest actions: Ask date, issue, action and description from user. Date is today by default. Ts and user come as previously. If the date-issue pair does not exist in Issues table, give error message. Upload data to Actions and user's bonus to Action vote.
- Vote for issue: Ask the rank number of the issue as a number. The user can check the numbers with Show issues. Date, user, and ts come automatically. Do firstuser. Votes is the number of user's bonuses and comes from Bonuses. Upload data to Issue vote. Store information about the rank before voting somewhere (as an ovariable or a technical data table?). If the information has changed from the last time, give bonus to the user whose information is now on the top.
- Vote for action: Similar to vote for issue, except that the action number is asked and data is uploaded to Action vote.
- Make decision: Ask the action from the two top choices of the most popular issue using a drop-down list. The options can be seen with show today's issue. Upload data to Decisions. However, if an issue was the most popular at some point during the day, it is still kept in the issue list. ----#: . Is it? How? --Jouni (talk) 17:21, 7 February 2016 (UTC) (type: truth; paradigms: science: comment)
- Evaluate happiness: Ask date (today is the default), action number from show issues for that date, and hscore for happiness score in the user's own group. Ts, user as previously. Check if user has a group in Users and if not, give an error message to sign up to a group first. Upload data to Happiness.
- Evaluate values: As evaluate happiness, except that unlike group, the value is asked from the user and nothing is checked. Upload data to Values.
- Manage profile: Ask the group to which user identifies themselves. Take user and ts as previously. Add data to Users.
- Show results: This code is divided into several parts:
- Show happiness performance: Ask nothing. From Decisions, take the action of each day; do this separately for You, the user's own decisions, and Crowd, i.e. the most popular action of each day. Combine that with the happiness scores from Happiness. Show cumulative happiness across time for both decision makers.
- Show value performance: Similar to show happiness performance, but for values from Values. It is imprtant to notice that value scores for each action are only partly a matter of opinion and partly a matter of research. Therefore, ideas should be developed how this research is gathered and used.
- Show situation': Show the situation of the current issue: the issue and description, and the two actions and their votes.
- Show all issues: Show all issues and actions and their votes for today.
Groups for Turkey | Value categories |
---|---|
|
|
See also
Moderator:Jouni (see all) |
|
Upload data
|
Keywords
References