 |
 |
From the article Tod helpfully links: "One of our implementation goals was to build a touch interface that appeared to be completely dedicated and self-contained: we did not want it to be apparent to the user that the interface had been created with and was being driven by commodity components. " I'm stuck by the self-contained nature of this project design, and similarly with the iPad catalog look-up tools. Are such implementations most successful with separate, narrowly defined goals? Or would a library want to keep a consistent interaction experience across the website, kiosks, and even physical space (signage, displays, functional process terminology, etc.)? I tend to think that even if specific interaction methods are tailored to provide particular information in specific contexts, they all need to be designed as components of the user's overall interaction experience. David ------------------------------ Date: Mon, 13 Feb 2012 09:55:09 -0600 From: Tod Olson <[log in to unmask]> Subject: Re: Touch Screens in the Library NCSU has done some work you might be interested in. See this article: Lessons in Public Touchscreen Development by Andreas K. Orphanides http://journal.code4lib.org/articles/5832 -Tod Tod Olson <[log in to unmask]> Systems Librarian University of Chicago Library