649week08 → Visualizing Filesystems
I’d like to continue our exploration of TreeMaps this week with a followon exercise. While I was planning this, Jakob Hilden contributed an interesting alternative filesystem visualization I’d like to share. The following picture is an annotated screenshot of Liquifile.
Jakob also points out a Quicktime video you can see to understand better what’s going on here. Jakob adds that he especially likes the horizontal time dimension, which he thinks can be useful to find files from a certain timeframe.
This raises an important issue for our treemap exercise. How do people use the treemaps you designed last time? What kinds of questions can people answer? I’d like to explore this by asking you to redesign your treemaps to accommodate a fictional user, Professor Farnsworth. Farnsworth is constantly running out of space on his laptop and tries to organize his files in a way that allows him to keep track of things kept locally and remotely.
Farnsworth has a number of kinds of files and has tried to create a hierarchy allowing him to find a given file without resorting to googling. In particular, he’d like to find files related to research topics, research projects, classes he’s teaching, skills he’s trying to acquire, and administrative work. Instead of searching for related keywords, he’d like to be able to browse for things created at the same time or while working on the same topic, project, class, or skill. Many of these turn out to overlap, so he keeps changing the hierarchy of folders, sometimes using the four headings above, but also using headings indicating the source of files, whether created by Farnsworth or others. Another heading has to do with file types. Farnsworth takes a lot of photos and creates a lot of videos. These files threaten limited laptop space more drastically than text files. A further complication is that Farnsworth takes a lot of baby photos and baby videos that are not part of his work but wind up on his laptop. They’re large and numerous and need to be organized largely by time so that he does not bore people by showing them the same images over and over.
Finally, Farnsworth needs to share some files and keep others private. He’d like to be able to easily put sections of the filesystem on a shared server, so that the appropriate groups of faculty, students, and staff can see only what they’re supposed to see. Examples of things that must be kept private include budgets for projects, grades for classes, evaluations of staff members, evaluations of prospective students and faculty, and plans with personnel implications. In all of these cases, it’s difficult and complicated (technically not philosophically) to know exactly who can and can’t see each file, but it is possible. The current form of organization is problematic in that files for different audiences reside in the same folders.
So the exercise is to create a TreeMap visualization of Farnsworth’s laptop-based filesystem that helps solve these problems more than just what a basic TreeMap application does.
