Tag: mobile

Code4Lib Day 2: Afternoon Notes

De-sucking the Library User Experience

  • Jeremy Prevost, Northwestern University

Libraries hate library users. If we didn’t, our websites wouldn’t suck.

Discovery

  • if a user can’t find it, why do you own it?
  • spend a lot of money on acquiring resources or access to them
  • want to allow them to find them
  • Good: works like Google from the user’s perspective
  • Bad: needs to know how it works to make it work e.g. need to know MARC; can only find known items
  • live examples: Ex Libris Voyager vs. Primo
  • Voyager: no relevant results even using boolean ‘AND’
  • Primo: can use boolean or not, relevant results – de-sucked!

Requesting Item

  • Request information/user experience also sucks
  • Prepopulated info, request item if not available – de-sucked!

Renew Item

  • consistency
  • made interfaces consistent – de-sucked!

Mobile

  • not going away
  • no mobile until mid-2007 for iPhone
  • jQuery mobile – Apr 2010 – but updating two sites sucks, no support for tablets
  • Mar 2013: responsive design, bootstrap

Libraries don’t hate library users!

  • start with something that you would enjoy using

Slides

Google Analytics, Event Tracking and Discovery Tools

  • Emily Lynema, North Carolina State University Libraries
  • Adam Constabaris, North Carolina State University Libraries

How to track in-page events. Decide which events to track, push to Google.

Event Tracking Use Cases

  • hidden or externally AJAX events e.g. facets, tabs
  • internal links that occur in multiple places e.g. request item
  • external links

Examples

  • Catalog: click on tabs twice as much as everything else; full text used a lot; browse graphical < text because of placement; about half request item even though in 2 different places
  • Summon: trying to track what they could track. Paging more popular than facets

Implementation

  • GA API script
  • jQuery API
  • HTML5 Data Attributes: data-* for use by scripts
  • decide what to track
  • basic technique
  • Summon gets harder. Have to get it in the code. more selectors

Debugging & Testing

  • set up safety net first
  • know the debugger
  • use the GA debug
  • test a lot

Actions speak louder than words: Analyzing large-scale query logs to improve the research experience

  • Raman Chandrasekar, Serials Solutions
  • Susan Price, Serials Solutions

Single unified index for all the items from all libraries’ collections.

RMF Goals

  • observe and log user actions e.g. queries, filters, click patterns
  • compute quality of search results e.g. user behaviour
  • analyze data to improve search results and enhance research experience

Data-Driven Documents: Visualizing library data with D3.js

  • Bret Davidson, North Carolina State University Libraries

Slides and resources

Why D3?

  • uses technologies that you already know
  • capable library – pre-built path generations, well maintained etc.
  • community – documentation, training available
  • might not because of learning curve, and don’t need something this complex

Examples

  • suma – space assessment toolkit
  • show visualization real time, tables, and CSV file

HTML5 Video Now!

  • Jason Ronallo, North Carolina State University Libraries

Yes! Also, slides/presentation.

Here’s Why

  • Flash video cannot be run on most mobile/tablets

How it Works

  • uses video HTML tag
  • use simple fallback – download if can’t view
  • problem: browsers cannot decide on single codec to use; codec war
  • solution: multiple sources: mp4, webm
  • use poster attribute as “screenshot” and don’t have to download video right away
  • add type attribute to say which format to use; can be very explicit
  • only one video per page please!
  • properties exposed in JavaScript
  • can add custom controls, more info for users
  • events that you can listen for e.g. timeupdate to update time in a video; update wording e.g. which floor
  • analytics: play, pause, seek, ended
  • can do visualization of engagement
  • can style with CSS
  • track for subtitles

Polyfills and Advantages

  • provide video controls
  • flash fallback
  • progressive download and range requests

Future of Media on the Web

  • DRM looks to be coming
  • Popcornjs – can do annotation
  • Web Audio API – mix audio, filters, etc.
baby and mother owl
Breakout Time

Access 2012 Day 3: Session Notes

Out with the Desk: Re-Shaping Service Delivery in Libraries

Marc Pillon

Challenges facing public libraries:

  • perceived as inconvenient/impractical in today’s digital world
  • budgets are shrinking
  • patrons expect a different service

Idea:

  • bring the library to them e.g. Tim Horton’s, Loblaws, Shoppers

Vision for Public Libraries in the 21st Century

  • convenience! = ‘cutting the cord’ to service
  • being able to deliver them anytime, anywhere
  • less traditional bricks-and-mortar
  • more locations for drop off, pick up, access to technology
  • partner with existing retail outlets

Library in a Box

Gave access to ILS with small computer.

Pros

  • access to ILS anywhere
  • small enough to carry anywhere
  • limited only by wireless signal

Cons

  • not easy to transport, bulky/heavy
  • complicated setup requiring IT support

Introducing CanGURU

Using Apple iPhone and Bluetooth barcode scanner. iPad and wifi receiver

  • highly portable, light weight, easy to use
  • made inexpensive by using consumer products that are readily available
  • can be easily replicated by other libraries
  • used externally and internally (getting rid of information desk)
  • highlights important of librarian (return to reader’s advisory, roving to enhance customer service)
  • collaboration with social services, parks and recreation, and other non-profit organizations

Technology

  • 3G or wifi for connectivity
  • VPN (Cisco AnyConnect) for authenticated access to internal network
  • RDP protocol for access to ILS software
  • client device suh as iPad or notebook
  • bluetooth barcode scanner
  • custom iOS software (uses protocol to talk to ILS)

Future Improvements

  • faster wifi
  • streamline connectivity process
  • self-check version for iPad
  • patron version for self-check
  • implement SIP3 options
  • integrate with RFID
  • porting to android and/or Windows 8 tablet

Where should Libraries Locate?

  • big box stores/large retail centres
  • coffee shops
  • train stations/airports
  • hospitals
  • parks
  • university/college campus

One Example: Fraser Valley Regional

Encapsulated technology in a car with public computers, books, check in/out, etc.

Another Example: University of Alberta has an embedded Edmonton Public Library branch.

Shaping the User Experience

Sonya Betz and Robert Zylstra

Problem

A lot of different web interfaces:

  • library website
  • libguides
  • ILL
  • OPAC
  • etc.

Can get 3-4 different interfaces just doing a simple look up and placing a hold on book. Users find it too difficult to find things and so much time is spent trying to train users to use them all, but it’s a losing battle.

Had no mobile interface either.

Solution

Virtual Services Integration Project

  • simplify access to library resources
  • provide access via all devices
  • provide common experience between platforms

First was mobile version (iOS App) and full-scale web (responsive design).

Key Concepts

  • one access point replacing multiple access points
  • mobile and desktop interfaces
  • user aware
  • fast and intuitive access
  • consistent and intuitive experience

Project Motto

Think Big, Start Small, Move Fast

Using Web Servies APIs

Integrating Services (e-Reserve, room booking) and Resources (Physical, electronic, etc.). Also has EDS.

My Account: Authentication to App using LDAP, which send tokens to everything in the App to simulate single sign-on.

Search: uses EDS API, which allows limiters. Can then share through mail, print, copy, dropbox, etc. Holdings details from ILS.

Library info: from website.

Featured Lists: new materials using ILS

At Present

Consolidated 3 separate spaces of library info, search, and account.

Next

  • MusicBrainz
  • citations
  • Alexander Street Press (streaming audio and video)
  • Favourites
  • shared folders
  • library maps
  • barcode scan
  • NFC/RFID

Mobile App is a pilot for the CMS. App infrastructure will serve as basis for CMS. CMS and App will share user preference and content.

Marketing

  • public press release
  • website
  • posters
  • instructional sessions (provided premade screen)
  • etc.

Worked with communications department.

More notes on Access 2012 Live Blog.

TRY 2012: Mobile Device Loans at the Library

Panelists

  • Mandissa Arlain – RULA
  • Monique Flaccavento – OISE Library, UTL
  • Ricardo Laskaris – YorkU Libraries
  • Fangmin Wang – RULA
  • Jenaya Webb – OISE Library, UTL

Loaning Device

  • Laptops
  • iPads (with covers & cables) at OISE
  • York also provides many other gadgets & accessories
  • most 4 hour loans (York 1-4 days), restricted to university community

Marketing

  • posters
  • social media: twitter, facebook, blog
  • LCD screens
  • website
  • branding of bags

Popularity

  • iPad > laptop at OISE
  • 12.5% of circulation stats at Ryerson
  • laptops & iPads at York

Security

  • sign waiver first time
  • replacement fee for losts
  • personal data cleared by deep freeze software once powered down
  • iPads cleared manually (~20 minutes each time) whenever returned
  • theft reported to security & IT
  • repairs sent to IT

Staffing Considerations

  • training sessions for staff including hands on experience
  • basic use and troubleshooting help
  • technical support & issues to IT
  • working group meeting to discuss issues
  • chargers with devices

Financial Support

  • education commons as pilot project at OISE
  • library itself & one-time funding from provost office to upgrade at Ryerson
  • library paid & some donations at York
  • apps purchased with gift card so as not to associate credit card #

Software & Apps Selection

  • laptop software same as what’s on desktop
  • productivity apps e.g. Dropbox
  • educational
  • preferred free, but some money to purchase apps

Age & Replacement Schedule

  • no formal refreshment cycle
  • mostly depends on budget, try to repair existing laptops
  • replacements determined by IT

User Feedback

  • informally, anecdotal
  • from student committee
  • studies planned for future: focus groups, survey

Future Directions

  • meeting demands, so unlikely to expand
  • no money to expand
  • future to encourage students to bring their own devices

 

Code4lib Day 2: Mobile Breakout Notes

Just a few notes if anyone is interested:

  • digital collections tool: wolf walk, digital images
    • geolocation using JavaScript to make it availble in HTML5
    • find it easier in app store, means more people use app
  • HTML5 more clunky with jQuery mobile
  • native app smoother, especially Google Maps
  • mobile site: only force on homepage and opt out using query string
  • mobile app/site needs to be interoperable
  • designing: mobile framework better at bringing out ideas vs. developing web version of a website
  • how do you build up services? concentrate on what is needed on mobile devices
  • should have just what you need and do it well while taking advantage of mobile aspects e.g. bluetooth, GPS
  • how best to build?: REST layer on top of what’s available
  • time resource: if know objective C, then just adding functions
  • voice use: comfort level? accurate enough? difficulty with quiet/study areas/floors?
  • phone tap to reserve seats/room, other application?
  • staff use in stacks? Shelflister: barcode scanner inserts into web form for shelf reading or collection development, including circulation data
  • mobile hours: just give today’s hours or closed (give tomorrow’s hours)

Reference Gone Mobile Notes – ALPS December Meeting

Presented by panelists Debra Flewelling (Douglas College), Nicole Gjertsen (Simon Fraser University) and Joyce Wong (Langara College).

  • 93% students use phone for texting

Phone Based Service

This is where a library buys a phone and plan and passes the phone from librarian to librarian (whomever is on duty).

Pros:

  • cheap cost

Cons:

  • no statistics
  • cumbersome
  • asynchronous means a student might reply hours later when another librarian has the phone

Might start with phone as beta service, but will usually move to software based.

Software Based Service

Users send texts, which are then turned into emails sent to librarians. The reply emails are sent back to students as texts. Different setup options are available, such as shared or dedicated numbers.

Pros:

  • little or no change to workflow
  • automated message sent if unavailable
  • can do mass messaging campaigns
  • courtesy notice option

Con:

  • more expensive

Upside Wireless

  • somewhat of a monopoly in Canada
  • can share number or shortcut but needs – user needs to precede text with a specific word (e.g. Douglas or Langara)
  • dedicated line – more expensive, but more messages and dedicated

Some Statistics

Langara

dedicated phone and staff

  • 50% facilities/how/where
  • 22% ref/citation
  • rest known item/technology

SFU

recently extended hours
auto response with askaway or desk’s phone number if closed

  • 20% directional
  • 50% known item
  • 30% ref
  • 8am-6pm typically
  • few questions on weekends, but open
  • ~10 mins response time
  • ref questions usually referred to subject/liaison librarian

Considerations

  • must be careful of message size limit
  • should have quick turnaround time
  • may point to where can find answer instead of give answer
  • best practices and guidelines including local polices
  • need to work out workflow
  • might bring in other staff to answer non-reference questions

Marketing

  • keyword campaign – users text keyword to number to enter prize draw
  • posters and banners
  • tabletop mini-posters
  • social media of institution
  • website, especially mobile site
  • powerpoint slide for liaison libraries to add to their presentations
  • article or ads in student paper
  • QR codes
  • word of mouth

Can ask students where they found out about the service.