COP25 anonymized dataset
<p>This postgresql file is the result of a collective intelligence experiment which took place in the framework of COP25 in Madrid in December 2019.</p> <p>The tables in the file are described below.</p> <p>answer_distances: No relevance. </p> <p>answers: Each answer given to a question by a user is logged. Each answer is composed of 5 different items, which are individual answers to the question. The same user can make several answers, at various times during the exercise, which is also recorded.</p> <p>answers_items: Each of the items is associated with the ID of the answer to which it belongs. </p> <p>answers_solutions: Each answer is associated to a solution, that is, the position in the network associated to the user for that project.</p> <p>ar_internal_metadata: Not relevant. </p> <p>delayed_jobs: Not relevant. </p> <p>delayed_jobs_id_seq: No relevance. </p> <p>event_logs: Each of the phases of the project, when they have started and what has happened in those phases. </p> <p>history_logs: No relevance. </p> <p>item_solutions: Each item is associated to a solution.</p> <p>item_swaps: No relevance. </p> <p>items: Each item is a participant's answer to the question asked in the project. </p> <p>neighbor_logs: Not relevant. </p> <p>net_logs: Not relevant. </p> <p>options: No relevance.</p> <p>projects: Each question asked to the participants is associated to a project ID.</p> <p>questions: The different questions that have been asked in different experiments of the tool are displayed. Only those related to SDG #6 and #13 are collected in this database.</p> <p>registration_requests: Not relevant. </p> <p>schema_migrations: Not relevant. </p> <p>solution_swaps: In some phases of the projects the solution assigned to a user can change, this is the equivalent to change the user's position, having different neighbors therefore. </p> <p>solutions: For each project the user receives a solution ID, this is located in an x,y matrix, so we can know which solutions are adjacent to each other (for x, y; x-1, x+1, y-1, y+1). </p> <p>users: Each participant receives a user ID that appears in this table.</p>
ShareScore
40/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 8
- Harmonization
- 4
- Access
- 16
- Reuse readiness
- 8
- Engagement
- 4