Session 5- Service at Point of Need: SharePoint & Mobile Tools

This one was for Reference Librarians. Towson University and Howard County Library (Maryland) are currently using these reference PDA style tablets for mobility and service at the point of need.

SharePoint and Mobile Tools
Speakers: David Dahl, Kay Kazinski, James Kelly, Donny Frank-Rice

SharePoint is a Microsoft Technology.

Why mobile reference?
- Improves customer service
- Provide faster service at time and point of need
- Incorporate pro-active approach to Reference

Details of Mobile Reference Model
- Based on Orange County Library Model
- Funding: State library and FCPL contribution
- Team: 9 Volunteers and various staff from branches and departments across system

Equipment
- Site survey
- Installation of signal coverage

Vocera Communications Badges (phone system)
- Weighs less than 2 ounces
- Wireless, hands-free
- Locate staff by name, location or title
- Voice activated

Samsung Q1 Mobile Computers (mobile reference computer)
- Networked to desk printers
- 7 inch displays
- Weighs less than 2 pounds

460 hours of Mobile Reference service

7,584 patrons reached during test pilot

Pros
- Staff had more floor time, which prevents security issues
- Staff can multi-task
- Desk time lessened
- Staff became more tech-saavy

Questions to consider
- Will your staff be interested?
- Can you secure funding?
- Is Mobile Reference just an additional service? A permanent fixture?


SharePoint

Reference Portal- Collaborating for Librarians

Centralized location for sharing information

Why SharePoint?
- Customizable
- High level IT experience not necessary, for end-users or designers
- Can offer training for SharePoint
- Free- if you own Windows Server 2003
- SQL server database is required

4 Features of Reference Portal

- Messaging system
- Issue Tracker (computer problems, facilities problem)
- Wiki Page
- Desk Tracker

You can create a new website in SharePoint particularly for Reference Librarian

You can track meetings, minutes, etc.

Tips and Suggestions

Get a beta site even keep it after production
- Access now
- Who needs access
- Be prepared for
- Make sure sites match
- Deploy early
- Make sure you have ample training

These are so neat. They look like little TV screens.

Here is the Samsung Q1 up close. It's cool.
From Computers in Libraries 2009 Conference



This was the last session..Blog Ya tomorrow!

Session 4- Open Source Library Implementation

Open Source Library Implementation

Karen Kohn and Eric McCloy are both from Arcadia University, explained in detail how they were able to pull off switching from Sirsi to Koha.

Koha runs on Linux, takes very little space and is fast.

This session was mainly about how the Arcadia University library got ready to implement Koha from Sirsi.

Who should be on board?
IT
Library Staff
Facilitating Faculty

Motivation for Migration
- No access to data
- Website design
- Unresponsive customer service
- Hard to upgrade and modify

Pros
- 12% cost savings
- Broke project into chunks
- Able to see some improvements quickly, faster federated search

Cons
- Staff time for testing (expensive)
- Could not pay for overlap support
- Delay in catalog changes being displayed

How it was implemented?
- Dropped Sirsi
- Used Savings to get Master Key working
- Dumped nightly from Sirsi to Koha
- Did a Z39.50 search from site to Koha
- Tested and debugged frequently

Issues to consider
- STRONG IT vs. Librarians relationships (working together)
- Staff and Faculty knowledge is important

Here is Arcadia's Landman Library looks like with the Open Source software Koha as their Integrated Library System.

I love this library catalog. It feels like you're on Amazon.com!

What do you guys think?