Search

Open Source Library System Software: Libraries Are Doing it For Themselves

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    2 nd of 2-part series on OSLS Part 1 defined Open Source software licensing Open Source Library Software Examples

    our long-term goal provide services to our customers services they want and need Not easy to do when….

    working with our hands tied behind our backs Using software designed in the 80’s and 90’s Very few improvements have been made Not responsible to library requests for changes

    many different needs to address Standards: children, literacy, lifelong learning, reading for enjoyment New needs: new Americans, baby boomers, Millennials, gamers How much of what you do involves using software? prevented from offering a service due to software? How easy is it to change procedures? OS software gives us the ability to control our environments.

    Quote from the description of this webinar We can do this because – with OSS - we have control over our own software environment When the software doesn’t support what we want/need to do, we can change it Focus today is on getting involved What’s that mean when talking about designing and supporting software?

    Getting involved is not just about writing code In fact, code writing is just a small part

    Write code Fundraise for development efforts Co-sponsor development (Liblime Development Exchange) Develop documentation or build a system of managing documentation Manage a Koha community (consortia…, large public libraries, small rural libraries, law libraries) Test release candidates Do usability testing - provide usability guidance Manage a community of interest (customers, catalogers, circ staff, acquisitions, serials, ILL/Resource sharing, digital asset managers) Create or test 3 rd party add-ins Optimize workflow (and suggest changes to the software that would support that) Troubleshoot existing code Write software specifications Identify what users needs (staff and the public) Design screens Get more people involved!

    Co sponsor development Conduct user need assessments Write specs

    Usability testing Design screens Write specs Decide what procedures need to be supported

    Conduct user need assessments Manage communities of interest Catalogers Customers circ staff Design screens Beta test Optimize workflow

    So, you think you might like to get involved in an Open Source Library System project?

    If you do nothing else…. Sign up for the Koha and Evergreen general discussion lists

    Koha Mailing lists: General bugs Developers Patches Translations zebra Windows users Portuguese community Brazil community French, German, and Spanish Lists

    General Documentation planners, technical writers, trainers, documentation contributors, etc. participating in or interested in following the progress of the Evergreen documentation project. Technical Discussion List patches and technical discussions Evergreen SVN commit list This list tracks the full diff of every commit to the Evergreen Subversion repository.

    Koha uses bugzilla (as to many other open source projects) to…

    Reported: owen of nelsonville public Assigned to: french developer Paul Poulain Summary Comments (can be several)

    Note the “component” field Here a NEKLS library staffperson addresses the Hold functionality Release Manager (Galen) gets assigned to work on it

    Create you own custom reports to track something specific I created report of Holds Related Enhancement Requests Who’s involved Status of requests Who’s doing what When will it get done (next release? On hold? Unassigned? Need more info?)

    Not quite as many things going on with Evergreen Newer, just launched in 2007 Still a tadpole (with forelimbs) – not metamorphosized yet You’ll know when it has matured into a full adult open source project when there is a place for the community of users and the community of developers to interact more directly. One ways this is done is via “bugzilla”

    You can hire a commercial service provider to help you with the “getting involved” part.

    Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?

    Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?

    Sure commercial service providers are nice Familiar model “The Vendor” But…other models…

    Hosting: Service Level Agreement 100%? Data Center: redundant servers, Amazon cloud? Data recovery? Nightly backups?

    PINES did the impossible – created their own ILS SITKA took what PINES did and expanded on it, build a support organization Michigan created an opportunity for the willing NEKLS established a resource sharing and support organization around Koha NYS Boards of Cooperative Educational Services did the same with OPALS What about us?

    Favorites, Groups & Events

    Open Source Library System Software: Libraries Are Doing it For Themselves - Presentation Transcript

    1. Open Source Library System Software: Libraries Are Doing it For Themselves Lori Bowen Ayre [email_address] METRO Webinar October 13, 2009
    2. Why are we here?
    3. Tough working environment…
    4. Diverse Customer Services Needed!
    5. “ One of the great advantages of an Open Source Library System (OSLS) is the ability to empower staff and optimize the user's experience by getting involved in improving the software.”
    6. Involvement = Write Code
    7. “ Coding” is just one way to be involved… Increase participation Contribute new code Co-Sponsor development Develop documentation Organize Koha communities Do usability testing Create and test third party add-ins Manage communities of interest (e.g. customers, catalogers, circ staff) Write specifications Conduct user need assessments Optimize workflow Troubleshoot existing code Raise money Beta Test new releases Design screens
    8. You decide what gets built. Write specifications Conduct user need assessments Co-Sponsor development
    9. You decide how it works. Design screens Do usability testing
    10. You decide how you work. Manage communities of interest (e.g. customers, catalogers, circ staff) Beta Test new releases Optimize workflow Design screens Conduct user need assessments
    11.  
    12. Step One: Read
    13. Where to Get Started….
      • Evergreen http://evergreen-ils.org/about.php
        • Evergreen demos, mailing lists, blogs
        • FAQ
        • Development roadmap
        • Downloads
      • Koha http://koha.org/about/get-involved
        • Koha demos, mailing lists, blogs
        • Development roadmap
        • Support
        • Sponsoring a project
        • Test things and report bugs
        • Suggest improvements
        • Teach developers about library standards/process
    14. s
      • Owen Leonard, Nelsonville Public Library http://www.myacpl.org/koha/
      • South Central Library System http://scls.typepad.com/link2koha/
      • Nicole Engard http://blogs.liblime.com/open-sesame/
    15. Evergreen Blogs http://planet.evergreen-ils.org /
    16. Follow #koha on Twitter
    17. Follow @esilibrary on Twitter
    18. Step Two: Lurk * To lurk, joining is required
    19. Social Networks
      • Facebook:
      • LinkedIn:
    20. Koha Mailing Lists http:// koha.org /about/get-involved/mailing-lists/
    21. Evergreen Mailing Lists http://evergreen- ils.org/listserv.php
      • Wed Jul 15 15:02 2009
      • Do automatic email notifications for holds need a cron job set up on the server to send them out? If so, is there a script already set up that I could run to pull and send out the notifications from evergreen?
      • Thanks, Robert
      • Wed Jul 15 15:38 2009
      • Yep, see Open-ILS/support-scripts. We run the following cron job:01 06 * * * cd /home/opensrf/Evergreen-trunk/Open-ILS/src/support-scripts/; PERL5LIB=/openils/lib/perl5 perl generate_circ_notices.pl --send-email --notice-type overdue,predue-
      • Dan Scott, Laurentian University
      • Thu Jul 16 13:13 2009
      • Thanks Dan and thanks for your answer regarding my earlier question on a "due time" column which was exactly what we needed.
      • -Robert
    22. http:// bugs.koha.org /
      • Tool used for keeping track of bugs and enhancements of software
      • Mechanism for directly communicating with developers
      • Publically available to anyone who creates a Bugzilla account
      • bugzilla
    23. Bug # 813
      • Summary: OPAC virtual shelves should store comments
      • Description [ reply ] Opened: 2004-08-06 03:51 The OPAC virtual shelf system would be improved by allowing for storage of description and comments information. I suggest the addition of a 'description' column in the 'bookshelf' table so that shelf creators can describe the purpose of the bookshelf (useful for teachers, for instance, who want to provide their students with more information about the purpose or use of the list).
      • ------- Comment #1 From tipaul 2004-12-17 00:32:59 [ reply ] -------
      • good idea, could be done after 2.2.0 official release as it requires new DB field(s), and i don't want to modify DB structure during 2.2.0RC process
      • ------- Comment #2 From tipaul 2006-05-12 21:11:12 [ reply ] -------
      • good idea, moved to head for 3.0
      • Reporter : Owen Leonard < [email_address] >
      • Assigned To : tipaul < [email_address] >
    24. Bug# 3342 Summary: Changes to holds priority list should be logged for accountability. Component: Hold Request Description:  [ reply ] Opened: 2009-06-19 15:11 When a library staff member changes a hold priority or moves a hold up or down the list, the change information should be logged to encourage accountability. Log information should include: - Which user did it - Date/Time stamp - Which Patron was moved and to which priority. Reporter : Liz Rea < [email_address] > Assigned To : Galen Charlton < [email_address] >
    25. Holds-related Enhancement Requests
    26. Evergreen is still a tadpole…
    27. Step 3: Test Drive
    28. Install and Try Koha
      • Current stable version: 3.0.2
      • Server operating systems support: Linux with Apache, MySQL and Perl installed
      • There is no client software. It is browser based. Firefox is recommended.
      • Download the software and installation instructions from:
      • http://koha.org/download/
      • Download End User Documentation from
      • http:// koha.org /documentation
      You need someone knowledgeable with a Linux to set up your own demo. Not for the faint of heart….
    29. Install and Try Evergreen
      • Current stable version: 1.4.0.6
      • Server operating systems support: Ubuntu or Debian
      • Client operating systems supported: Windows, Mac, Linux
      • Client software must match the server version
      • Download the software and installation instructions from:
      • http://www.open-ils.org/downloads.php
      • Download End User Documentation from
      • http://www.open-ils.org/dokuwiki/doku.php?id =evergreen-user:evergreen_end-user_documentation
      You need someone knowledgeable with Debian or Ubuntu to set up your own demo. Not for the faint of heart….
    30. In case your head is exploding…..
    31. Help is on the way!
    32. Equinox Software http:// www.esilibrary.com /
      • Support
        • Per incident or comprehensive 24/7/365
      • Migration
        • Project Management
        • Data Translation
        • Training
      • Hosting
      • Custom Development
    33. http:// bywatersolutions.com /
      • Support
        • 24/7 phone-based support
      • Migration
        • Data clean-up
        • Installation
        • Configuration
        • Training
      • Hosting
      • Custom Development
    34. PTFS http:// koha.ptfs.com
      • Product selection
      • Support
        • Email and helpdesk support
        • Tiered support structure
      • Migration
        • Data export
        • Retrospective conversion
        • Implementation
        • Configuration
      • Hosting
      • Custom Development
    35. Media Flex http:// www.mediaflex.net
      • Not available to download locally without registering with Media Flex
      • No obvious open source community
      • Most users are hosted by Media Flex
    36. Liblime http:// liblime.com
      • Support
        • Web and phone-based support
      • Migration
        • Installation
        • Data clean-up
        • Configuration
        • Training
      • Hosting
      • Custom Development
    37. Non-Commercial Support Options
      • PINES (Georgia) http://www.georgialibraries.org/public/pines.php
      • SITKA (BC) http://sitka.bclibraries.ca/
      • Michigan Library Consortium http://mlcnet.org/evergreen/
      • Northeast Kansas Library System (NEKLS) http://nexpresslibrary.org
      • NYS BOCES provides support services for NY state school libraries using OPALS http://www.boces.org
    38. Peer-to-Peer Support
      • IMLS Grant for $1,000,000 Awarded to King County Library System (KCLS) and 3 other library systems to….
      • Watch http://oss4pl.org for developments related to this grant project
      “ create and develop the critical infrastructure components that have traditionally been provided by ILS vendors and establish a peer-to-peer support model for open source libraries.”
    39. Let me know how I can help! [email_address] (707) 763-6869 http:// galecia.com

    + loriayreloriayre, 1 month ago

    custom

    150 views, 0 favs, 0 embeds more stats

    One of the great advantages of an Open Source Libra more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 150
      • 150 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 4
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    -->
    Search
    RSS Feed
    What's new?

    © 2009 SlideShare Inc. All Rights Reserved