ELAG - Mashing Up and Remixing the Library Website
1. Mashing Up and Remixing the Library Website
Karen A. Coombs
University of Houston Libraries
2. The problems
• Information on the library website is maintained by a disparate group of people with
varying skill levels
• Library websites incorporate (or should) information from many different systems
• Same information repeated several places throughout the library website
• Users want library information at their finger tips and where they are
• Library information should be integrated the curriculum
3. Traditional Solutions
• Use database-driven web pages
• Install a content management system
• Distribute responsibility for content creation and maintenance throughout the library
• Make other library systems look as much like library site as possible
4. The Road not Taken
• Easy to use system; little Web
Services interference in content
creation
• Remixable blocks of content,
objects, metadata
• Ability to incorporate content from
other systems easily
• Website content easily sharable
with other systems
Photo by John Linwood @ Flickr
6. Web 2.0 Six Pillars
•Radical Decentralization •Remixable Content
•Small pieces loosely joined •User as Contributor
•Perpetual beta •Rich User Experience
Photo by steve.wilde @ Flickr
7. Map of the Internet, The Opte Project, www.opte.org
Radical Decentralization
15. Virtual Subject Library
• Federated Search
• New Books from Catalog
• List of Relevant Databases
• Subject Liaison Contact Information
• News Feed from Relevant Professional Associations or Websites
• Relevant Websites
21. Next Steps
• Complete functionality to add media to pages
• Personalization
• User contributed content
• Integrate with other library systems
• Digital Library Software
• Better integration with federated search
Notas del editor
Libraries website has content which is created and updated by a number of different people
Wikis and blogs
Libraries website allows any staff to update any content
Libraries website is a combination of different technologies
Wikis, blogs, content management system
Libraries CMS made up a different modules for different content types
Content is reusable throughout the site
Any piece of the CMS can be replaced as needed
Deploy systems early and make constant improvements
Users are part of the development process
Deploy new systems to a small group of staff to test and help us refine
Gather constant input and make continuous improvements
APIs to allow content to be incorporated into other systems
Libraries website can incorporate content from external sources
Content which is part of the Libraries site can be used on multiple pages
AJAX to add a database link to any page, blog, wiki
Allow users to add and update content on the Libraries site
Class wikis
Wiki model for CMS
Institutional repositories for scholarly content from faculty, students and staff
Library hosts blogs (ie. UThink project at U. Minnesota)
User tagging and review content in catalog
Multimedia, interactivity, GUI-style application experiences
video, sound, screencasts
Personalization and customization
Space for collaboration and interaction
chat, VoIP
Decentralization of content creation, decision making, information
Flexible, nimble
Cross function teams and works groups
Mashups
Plugin architecture
Loose confederations
Working collaboratively to achieve greater success
Let others use the content you have in meaningful ways.
Exposes your content to a wider audience
Syndication RSS
Read/write web - the web isn’t just about consuming content anymore it is about creating content
Creative Commons model for copyright