You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

When Information Navigation Divorces File Systems –Database Surface Prototype Results


Publication Type:

Conference/Workshop Paper


Proceedings of the Good, the Bad and the Irrelavant


All PCs have file systems. The design of this most vital part of personal computers has had the consequence that the design of user interfaces, for better or for worse, hasbecome wed to the file system. The file system can be traced in interfaces from today's graphical user interfaces, for which the desktop metaphor helps explain to users how totreat their documents and folders, to yesterday's command line user hostile DOS (Disk Operating System) interfaces. What if one was to exchange the spine of computer system from a file system to adatabase? Imagine the unstructured stream of ones and zeros you normally put in a location on a hard drive instead be put in a content aware database. Monolithicapplications are divided into components that are put in the database. All the different content files are turned into objects that are put into the database and so forth. Thisintroduces a number of questions that include how to handle: information access; information visualisation; user collaboration; multi modal interface usability; programarchitecture; scalability over different platforms; to name a few. This paper presents a design rationale for how to visualise the content of the database. Ihave chosen a comprehensive approach to the zoom interface paradigm. All content is presented on a flat and infinitely large two-dimensional database surface. There are nowindows. The information has only the state: open; there is no closed state for which an application opens the content in a file. Users zoom in and out on the information as themain navigation technique. The application area first to be investigated was music creativity. I have interviewedmusicians, both young female novices and male experts in their 30s. Both groups agreed as to what the problems with current tools are. With the interviews as inspiration I formedthe design rationale and constructed a prototype accordingly. Eventually this prototype was evaluated with user studies based on the collaborative evaluation method. The usersfelt mentally head over heels at first, but thought this dramatically different approach to what they were used to was both usable and amusing.


author = {},
title = {When Information Navigation Divorces File Systems –Database Surface Prototype Results},
editor = {Kari-Hans Kommonen},
month = {September},
year = {2003},
booktitle = {Proceedings of the Good, the Bad and the Irrelavant},
url = {}