I spent longer chatting at lunch than expected, so missed most of the post-lunch session, but I’m back for sessions 4 & 5.
Session 4: Unifying Content Across Platforms
Matthew Blake, Web Services Lib,
iKiosk – interactive touch screen
Library displays its hours in many, many places: website, digital signage, info kiosk, mobile platform, and then there’s the subject department/branch hours.
By using an XML file, it’s easy enough for non-technical folks to update the content itself.
Combination of RSS and CSS to make the native campus-wide calendaring system display everything in a reasonable way.
News & Events blog has RSS feed sent direct to Sharepoint, which just knows what do to with the feed URL.
News & Announcements widget on website and digital signage are pulling from the same datasource.
[Faded out here.]
Created single file for floorplans – encouraged others to only ever change that file when needed.
Digital wayfinding – using isometric map, identifying pixels, and wayfinding will draw a line from one pixel to the next and so is completely scalable
Responsive design: media queries determine user’s screen size and adjust size and layout of elements accordingly. You don’t need to choose – it’s all available and the device chooses how it displays. Better tablet interface because it doesn’t make you have to develop another
Grand Valley State Univeristy – www.gvsu.edu/library – neat!
[And again, that’s where I faded out. Lots of stuff I already knew, with just a few neat ideas here & there.]
Rebranding the Library’s Virtual Presence
Lora Cokolat, Electronic Resources Librarian, Santa Clara County Library District
Megan Wong, Virtual Library Manager, Santa Clara County Library
Felicity Gilbert, New Technologies Coordinator, Yarra Plenty Regional Library (via Skype)
Natasha Hesch, Product Manager, BiblioCommons, Inc.
I sat in on this mostly to see what other libraries had done with the Bibliocommons CMS, and the answer is that it simply facilitated a seamless integration and seamless user experience with their Bibliocommons discovery layer. All the usual benefits of a CMS, plus an absolutely painless integration with the online catalog for a single user experience.
We can’t do that at the BPL – it doesn’t look robust enough for what we’re trying to do – but it’s awesome for other libraries.