Draft Koha Evaluation ballot for 2016
The ballot includes three questions that identify the person submitting the ballot and theKohaevaluationquestion.The library director for each SCLS ILS library is authorized to vote. We will use the email address that we have on file for each directorto validate the vote.Each library has one vote, but the votes will be weighted according to the2016vote share of1002. This will be a simple majority vote. All votes will remain anonymous.This ballot was approved by the ILS Committee on 12/7/2016.
Are you [your library] satisfied enough with theKohaILS to stay on the path we, as a system, are on for the next two years(2017 and 2018). You have two choices in the form of paths
Path 1: Yes ______
A “yes” vote means:
- Staff will continue currentKohaDevelopment Plan
- SCLS will continue to control the development budget and plan with input from member libraries.
- New features and improvements will continue to be developed and tested
- SCLS will work with other consortia (e.g. WALDO, Pioneer Nebraska Library Consortium and the Colorado Library Consortium) to developKoha, which will provide additional features at no cost or by sharing the cost.
- SCLS will continue to work with ILS member libraries to identify projects that meet the needs of SCLS libraries and their patrons.
Path 2: No ______
A “no” vote means
- PauseKohaDevelopment and Explore alternative ILS options
- SCLS staff and ILS member libraries will explore alternatives to the current ILS and develop a new RFP, with the goal of reaching a decision before the August 2018 deadline. This process will include vendor demos,evaluationand testing of features.
- Using ILS contingency funds, SCLS staff would recommend hiring an outside consultant to coordinate the process
- No more new SCLS development will be done on theKohaILS, but SCLS projects already in progress with PTFS LibLime would continue until completion.
- TheKohaILS will be static for most of 2017 and 2018 in terms of SCLS development. There may be upgrades to theKohaILS in 2017 and 2018 that include bug fixes and new development from other LibLime customers, but SCLS staff may not be able to implement them.