# Uncharted data

(this guide will be updated as needed)


## General notes

* This is a group project, which I expect will iterate during the rest of the term. This project will be presented as a group at the end of our course
* The project is expected to be developed as a group, however, you are free to present as many "subjects" within the group as you like in it
* Considering the relative complexity of the assignment, it is recommended to divide the task between *collectors*, *designers*, *theorists*, and/or *coders*. Use the strengths of the group to work efficiently
* It is important to consider that this will be on a public URL (at least until the end of the term). So feel free to pseudonymise or anonymise the data when possible

**The final product should be a website (strong preference of a gitlab *page*, but this is not compulsory) focused on a visualisation of the "uncharted" data. This website should contain the rationale for the "representation" of the subject, as well as a deeper explanation on processes of "subjectification" (being enacted or avoided by the assignment) using literature from the course (or relevant for the course).**

## The data

* Data about you that has not been captured, *exhausted* (Kitchin and Tate 1999) or *transformed* into a surplus (Zuboff 2019)
* because it is not "valuable" (profitable through current business models)
* because is difficult to capture
* because is difficult to structure
* because it relates to affective states
* (etc)
* The process of collection should be agreed between the group, and documented (as in, keeping a log of the changes or interations). Using GIT is recommended to keep track of the project, but not required.
* You're encouraged to use non-standard visualizations (and they don't need to be "digital"). Especially during the "design" process. Traditional charts (bar charts, scatter plots, etc) are not recommended, unless they relate explicitly to the development of the "subjectification" concept. It is recommended to follow the "recipes from Dear Data" (see below).

## Presentations

10-15 mins + 5-10 mins Q&A (total: 20 mins max)

| Date | Group | time |
| -------- | :------: | -------- |
| 07 may | 1 | 13.15 - 13.35 |
| 07 may | 2 | 13.35 - 13.55 |
| 07 may | 3 | 14.05 - 14.25 |
| 07 may | 4 | 14.25 - 14.45 |
| | | |
| 11 may | 5 | 12.15 - 12.35 |
| 11 may | 6 | 12.35 - 12.55 |
| 11 may | 7 | 13.05 - 13.25 |
| 11 may | 8 | 13.25 - 13.45 |

## In a nutshell, to deliver:

1. Clear role assignments (you're free to be critical about this requirement)
2. A consistent log of your discussions and of the changes of the project
3. Final product should be uploaded on a public web (consisting of visuals, and rationale for the project)
* A set of visualisations (analog or digital)
* A rationale for how a particular process of subjectification is enacted in your project, and how it relates to concepts from the course (I know this is quite open, so I'll add some example questions to this guide)
7. Presenting the project at the end of the term

## Dear Data recipes
*feel free to ask me for more examples of visuals


## Q&A

(feel free to select any text on this page, and click "comment" to leave a question. This will be added to the Q&A section)