This document discusses using open source applications to support library operations. It begins by debunking myths about open source software, noting that while intermediate computer skills are helpful, advanced skills are not essential. It also states that open source software is not necessarily bug-ridden or difficult to support. The document outlines the top five qualities to look for in open source solutions, including a stable community, solid documentation, recent updates, pathways for feedback, and the ability to try before committing. It then discusses performing a cost-benefit analysis and introduces four specific open source solutions: the Koha integrated library system, SubjectsPlus guides platform, Omeka digital archives and exhibits software, and ResourceSpace digital asset management platform.
2. Overview
● Debunking Myths of Open Source Software
● Top 5 Qualities to Look for in Open Source
Solutions
● Cost Benefit Analysis of Open Source Solutions
● Closer Look at Some Open Source Solutions for
Libraries
3. Myths of
Open Source
Software
Requires Advanced Computer Skills
Intermediate Skills are helpful,
but not essential
Unpolished and bug-ridden
Community-driven development
observes QA standards
Difficult to support and drain resources
Good support, paid and
volunteer, is available in most
OSS communities
4. Top 5 Qualities
of Good Open
Source Solutions
For Those
Considering
Open Source
5. Stable Community
Look for Open Source
solutions that have an
active and stable
community of users and
developers.
#1
8. Pathways for
Feedback
Clear routes to post
questions, make
suggestions, get help, and
connect with the
community make it easier
to find answers when you
need them
#4
9. Try before
Committing
Take advantage of demo
sites or download and
install the software on a
localhost before deciding
to invest in the solution.
#5
10. Cost vs. Benefit
● Hosting and support
expense
● Set up and
customization
● Ongoing maintenance
● Investment
● No license fees
● Professional skill
building
● More control
● Community involvement
13. What?
● Integrated Library System
● Created in New Zealand by Katipo
Communications, now developed internationally
● Updates released every six months
● Embedded web-based documentation
● Full-featured modules for circulation, patron
management, cataloging, authority file,
acquisitions, serials, and reports
● Responsive OPAC built on Bootstrap
● Flexible with multiple integration possibilities
16. What?
● Guides Platform (Springshare’s LibGuides)
● Ongoing development at University of
Miami Libraries
● Wiki-based documentation, Google Group
user community
● Flexible and Feature-packed: FAQs,
Talkback page, A-Z resource list
● Responsive design fueled by CSS
● API capability
19. What?
● Web publishing for digital archives and
online exhibits
● Developed by Roy Rosenzweig Center for
History and New Media
● Expansive documentation on website with
hosted forums for user community
● Customizable themes and plugins
● Metadata on multiple levels: file, item,
collection, exhibit
● Dublin Core
22. What?
● Digital Asset Management Platform
● Developed by Montala Ltd., originally
commissioned by Oxfam
● Hosted Knowledge Base documentation,
bug tracker, and Google Group for user
community
● Automatically harvests metadata,
including full-text
● Users log in to access content