in Process

Reflections on Marsha Kinder’s Designing a Database Cinema

Upon reflection, the aspects behind designing a database cinema is very different from my initial impression of what it meant. Initially, my impression of a database cinema was basically- information overload. With that, the one main key takeaway I had from the reading was the point on how database narratives actually focused on the processes of selection and combination of the information that lie at the heart of the piece. To me, what really struck me was indeed that in this era, information is readily available at hand and maybe now, it’s not so much how much you know but instead what you can do with the information. Especially placing it into the context of new media, and creating a narrative, the information selected plays an important role in letting the user realised on their own that they are the reader. What I realised in the works that were part of the Labyrinth project were that they required for the users to first be attuned to the technical specification of the apparatus before the user can start composing their own interpretation. Thus, the structure in the works is crucial to the “language” of these works. This sort of engagement might not be the most straightforward as compared to the traditional printed book but thats the beauty of it. In the reading, it describes as its structure as a sort of ‘search engine’, where users have to make their own random choices to piece together information to form their own hypothesis or in this case, their own story. In my daily life, the information that I retain is often the ones I search for myself instead of the ones fed to me. So, if we could feed our stories in these way and leave impressions to truly drive our message across as artists then I say honestly, What a better way to present information!