Suma: A Mobile Space and Service Assessment Toolkit
Using Suma to inform space and service planning
Jason Casden | Bret Davidson
NCSU Libraries
Outline
Why Suma?
How do libraries use it?
How does it work?
What's next?
How to get started?
by Joyce Chapman, Suma community development and data analysis specialist.
Could we collect more detailed data, more easily, with fewer errors, and manage it all more consistently?
And could we build more sophisticated and intuitive analysis tools that are totally reusable for all data by lots of people in our institution?
Could we then use data about space and service usage to make better decisions (even small ones)?
The web has had this for years
Web Analytics
Collecting rich relational data for a new service is trivial or easy.
Spreadsheets
Collecting data requires error-prone and time-consuming data entry.
Less data is collected, with less detail, less often.
Web Analytics
Years of data for dozens of services is in one place.
Spreadsheets
Many spreadsheets, many formats, split by year or semester, stored in a variety of locations.
Cross-service analysis is rare.
Web Analytics
Although APIs exist, analysis tools are easy to use and can be accessed by many people.
They're also the same for every dataset.
Spreadsheets
Limited analysis tools. Can a programmer help?
Fewer people use data to inform fewer decisions with less sophisticated queries.
Suma
An open source tablet-based app (well, toolkit) to aid library staff in assessment of how patrons are using library spaces.
In other words…the gathering, storing, exporting, analyzing, and visualizing of data across spaces/activities/time and around events.
Data collection
Suma data collection
Staff as sensors
Understanding our users
Where do our users go?
What are they doing?
When are they doing it?
What could they be doing?
Space and Service Analytics
Staff scheduling
Building hours
Service desk service patterns
Study room reservations
Technology and furniture use
Use of specialized spaces (e.g. Graduate Commons)
Comparing branch and main libraries, at different times of day
Special Collections researcher services
Turnaways (e.g. Technology Lending)
Combine with other data: circulation, gate counts, tech lending, reserves, online services
System Overview
System Overview
System Overview
System Overview
Data Synchronization
Core Technologies
Zend PHP Framework
MySQL, Web SQL Database, Persistence.js
AngularJS
D3.js
Analysis in Action
Sample Data
2 of 5 reports
Time of Day
Reference v. Computing
Day of Year
Period Totals
Reference Only
Time of Day/Day of Week
Jumbo Report
Other reports
Nightly email report
Calendar heat map
Collecting sessions summary
Project team
Jason Casden
Bret Davidson
Joyce Chapman
Rob Rucker
Rusty Earl
Eric McEachern
Future goals
Arbitrary day boundaries (done)
Easier pilot project deployment (in progress)
Improved documentation (in progress)
Broader client browser support
Improved support for third-party analytics systems
Open Source
100+ active academic library pilot projects
Hosted on GitHub
Pull requests are always welcome
Open Source support (free kittens)
For Suma, the vast majority of our project support is during the installation process.
"[W]ho would be the best person on your team to talk with about the technical requirements and skills needed for us to install SUMA and get it up and running. For example, do we need a computer programmer with such and such skills. I’m sure you have good documentation available, however, we would like to talk with someone. We are also curious as to how much time it would take to get SUMA working for us. I am not sure we have the expertise in-house."
- librarian at a RU/H research university (with permission)
On canceling a pilot project...
"Ultimately, I didn’t want to get on our IT support’s bad side and because I’m not allowed to play with our development servers I can’t exactly go at the installation process alone."
- librarian at a RU/VH research university you've totally heard of (with permission)