On 18/09/2007, Stephens, Owen <o.stephens_at_imperial.ac.uk> wrote:
> If we are talking about a portable device web interface, how would this
> differ from a NGC on a desk/laptop device?
Mostly a technical issue, I suspect. Optimisation for a relatively
small screen would be key, keeping bells-and-whistles low enough that
it doesn't confuse the level of browser found on an average PDA. The
capacities in this area are rising steadily, but they're still fairly
backwards by the standards of desktop machines. Limit the amount of
user input needed, and *especially* don't require much mousework.
Build to the presumed capacity of the reading device.
I have a strong suspicion that in coming years a growing proportion of
patrons - and, potentially, staff - will be carrying around
wireless-capable palmtops; perhaps PDAs as we currently see them,
perhaps newer fancier phones, perhaps the next-generation iPod, but
*something*. Wireless access in libraries seems to be continually
expanding. and it's a short step to think of this as a way to get
catalogue access deep down inside the bookstacks. Next generation is
where you read it as much as it is what you read - remember the O in
OPAC :-)
(I have yet to get our local catalogue working on my handheld tablet,
which was one of the things I had down as a really good probable use
for it, but that's the fault of our intranet not the catalogue
proper... so give it time)
So try not to have a catalogue that's unusable on a screen wider than
640px, or that requires fancy Java tricks to get full functionality. A
"PDA view", or an optimised interface for WAP, would be an option - I
don't know what WAP usage is like in the wider world, or how long
until it's obsolete, but it's pretty handy for very basic lookup roles
if you have the capacity. (Do I buy this book? Wait, let's see if they
have it... I have in the past perched on top of bookshop stepladders
tapping names into a phone)
--
- Andrew Gray
andrew.gray_at_dunelm.org.uk
Received on Tue Sep 18 2007 - 07:39:50 EDT