ITP is a two year graduate program at NYU focused on the intersection of art and technology, “a Center for the Recently Possible.” One way a sense of community and connection is facilitated is with the ITP student listserv, host to all sorts of email conversations between students on everything from missing power chargers to animated gifs and pop culture.
My experience of the ITP student listserv upon arriving at ITP in the Fall of 2013 was one of mostly confusion, my inbox suddenly overwhelmed by a barrage of emails from people I didn’t know replete with animated gifs and insider jokes. By the Spring Semester of this year, my sense of the listserv was that it seemed largely dominated by Second Year students, who seemed to mainly just be speaking with Second Year students with minimal participation by First Year students.
I decided to test my theory by gathering my gmail data and creating a network visualization of the ITP listserv.
First Year students are grouped on the right hand side of the circle, and Second Year students on the left side. The density of lines is much greater on the left side of the circle, indicating there are more public conversations taking place between Second Year students.
During the process of researching for this project, I discovered an ITP student listserv network visualization made in 2007 by Joshua Knowles. My visualization chooses as its reference point the 2007 visualization, but I have many ideas to expand on this earlier visualization including making the visualization interactive so users can more deeply explore the data, and visually exploring the class imbalance of listserv usage.
I believe it is important to explore data in context. Once my data visualization is interactive, I would like to user-test it with ITP students, while also getting feedback from students on their own individual experience of the listserv and the ways it could be improved upon.
So how did I create this visualization? With Dan Shiffman’s guidance, I wrote a Processing program to visualize the ITP ListServ:
→ Read more
