1 / 12

SCLS All Director’s Meeting July 27, 2011

SCLS All Director’s Meeting July 27, 2011. Goals for Shared ILS 2011. COMMUNICATION. Using SCLS Status wiki for most recent news—outages, new problems, etc.

sharne
Download Presentation

SCLS All Director’s Meeting July 27, 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCLS All Director’s MeetingJuly 27, 2011 Goals for Shared ILS 2011

  2. COMMUNICATION • Using SCLS Status wiki for most recent news—outages, new problems, etc. • Revamping known problems page to have more details about the status of problems and development with dates. Will be able to track development.

  3. COMMUNICATION • ILS Committee now meeting monthly. • The ILS Committee minutes will be reviewed by committee members first and will be available within one week of the meeting for all ILS libraries. • Two opportunities for input from clusters: • 2 weeks--ILS call to agenda-cluster rep shares and gathers input. • 1 week-ILS agenda sent to link—announce with reminder to contact cluster rep.

  4. SHARING OPPORTUNITIES • Module user groups and workflow sharing sessions • Semi-annual all ILS library user groups • Wiki for workflows (Circ Services Committee)

  5. MORE INPUT FROM LIBRARIES • Will continue new development prioritization process with input from all ILS libraries. • Will try to do one a month. • Will focus on getting the current problems fixed before moving on to the next list.

  6. DEVELOPMENT PROCESS • Submit list to libraries • Libraries “vote” on top 5 • Top 10 vote-getters are submitted to LibLime. • Bug fixes to existing software can be applied to the next service pack (not sure yet how far apart these will be) • For new development, LibLime will work with Development Committees on the following process which may take 3 to 4 months. • Develop specification • Provide quote • Code the feature • Submit feature to our sandbox for testing • Work the feature into an upgrade

  7. WHAT’S NEXT? • Continue developing Koha—focus on searching improvements • Ecommerce • Mobile device for patrons

  8. WHAT’S NEXT? • Prepare for “electronic materials age” • Collection development • Ownership • Circulation statistics • Seamless access to all types of materials for patrons • One search interface • LSTA digitization grant will allow us to try PTFS Archivalware interface

  9. KOHA SURVIVOR AWARD Andy Barnett / McMillan Public Library for creating most adaptable workflow on "go live" day when libraries could not do checkin

  10. KOHA SURVIVOR AWARD Richard Wambold at Dane County--most innovative way to document response time problems with Koha http://www.scls.lib.wi.us/dcl/temp/search/search.html

  11. KOHA SURVIVOR AWARD Verona Public Library--first library ever to do automated materials handling with Koha

More Related