Thursday 19 January 2017

OS Readings Series: Avery

Avery, Joshua M., ‘Implementing an Open Source Integrated Library System (ILS) in a Special Focus Institution’, Digital Library Perspectives, 32 (2016), 287

These notes have turned into a list of advice... the start of the article contains a very nice literature review on similar projects, and observations about same.


  • A list of ILS selction criteria are listed in Bossels 2008, Muller 2011, Pruett and Choi 2013. Sing and Sanamann 2012 and Yang and Hofmann 2010
  • Current literature shows Koha is a better fit for small less complex library systems. 
  • Opac is highly customizable
  • Discussions with local IT began well in advance of migration. A task management system (Asana) was put in place (manage, schedule, track and update stages)
  • Knowledge gathering via listserv, chat-boards, weblogs, tutorials, documentation and contacts
  • Read online handbook 
  • Talk to institutions of same size
  • Test server allow release and updates to be tested before going live
  • Koha implementation check list is available online
  • Install than, branches, item types, patron types, collections. Locations and other rules and preferences > then data migration
  • Migration means questioning rules, config., etc. 
  • Data mapping > MARC EDIT USED to edit marc records for import
    • 952 = holdings data
    • 942 = class and item type
    • Data is loaded in batches so carefully label each batch using the comment function in the koha batch upload tool 
    • Try to keep batches <10,000
    • Batch load Circ data via offline circ
  • One month before live = final opac customizations and intensive training for staff on new system
  • Old system was kept live for 24 months and staff did harvest data from it on occasion. 
  • Each library’s migration and day to day experience is different.  
  • Consider formal per and post measures of staff and student satisfaction with the ILS
  • Local understanding of the limits of MySQL, CSS, HTML, Linux, Apache and Perl is needed
  • Clearly determine who is responsible for which task
  • Waive fines and fees
  • Have regular meetings with all parties – face to face


OS Readings Series: Singh

Singh, Vandana, ‘Experiences of Migrating to an Open- Source Integrated Library System’, Information Technology & Libraries, 32 (2013), 36–53 <http://search.ebscohost.com/login.aspx?direct=true&db=a9h&AN=89093583&site=eds-live> [accessed 19 January 2017] 
Singh refers to Kohn and McCloy's advice to migrate in 3 phases: 

  1.  Public Web Site and Federated Catalogue
  2. & 3 Staff back end. 
In relation to time frames Walls (3 months) and Dennison and Lewis ( 2months) are mentioned. 

Advice is given to have staff work on the system before training (2 days), to ensure that they get the most out of it, and to deliver same by module.

CONSIDERATIONS outlined: 
  • Create awareness as to what open source is in the library
  • Develop IT skills internally
  • Have a demonstration system
  • Have a designated liaison with the vendor
  • Set aside a significant amount of staff time for: 
    • Testing
    • Development
    • Migration
  • Set up regular meetings
  • Do three test loads
  • Set up tables and settings in advance
  • Do data mapping very carefully
  • Weed out of date materials 
  • Have a fine amnesty
  • Look at grant money for OS development and do so in a partnership.
  • Spot check data
  • Utilise training materials generated by other libraries 
  • Utilise manuals created by other libraries
  • Utilise pre-existing webinars
  • Systems administration staff will need more intensive training
    • Specifically: Linux and SQL
  • If migration is changing things significantly for patrons additional marketing and a demonstration system could be made available
  • Set up online tutorials for patrons 

OS Readings Series: Walls

Walls, Ian, ‘Migrating from Innovative Interfaces’ Millennium to Koha: The NYU Health Sciences Libraries' Experiences’, OCLC Systems & Services: International Digital Library Perspectives, 27 (2011), 51–56 <https://doi.org/10.1108/10650751111106564>


 This article was reviewed with aneye to identifying problems, issues and advice for migrating from Millennium to Koha. 

MAPPING BIBLIOGRAPHIC DATA 
Expired codes, typos and outdated MARC21 fields were identified as needing to be addressed. 
Location field in Millennium translates into 4 fields in Koha. (Branch, Item Location, Item Type and Collection)
M    MARC21 export required a script to extract in MARCXML format from the OPAC as Data Exchange module was not available. 

     PATRONS
     Consider which patrons to migrate : 
     Only those active in the last X years
     Only those with library materials
     Only those with fines / bills 
     Validae accounts to be migrated against the local master directory

     Staff training and testing
     Have the data available to staff 3 months in advance. Test extensively for functionality as it may be there but in a different location, or labelled something else. 
     Identify and document changes to procedures and policy. 
     Create cataloguing templates 
     Use different CSS for the public and staff interfaces to make them clearly different from each other. 
     Workflows will change in Acquisitions, Cataloguing and Circulation at a minimum. 

Open source systems for libraries - readings series

Over the next while I will be doing a significant amount of reading in the area of open source systems for libraries. My notes on each reading (including full citation) will be posted separately on this blog, and these notes will be from the perspective of looking to implement some of these systems. Each reading will be listed here once posted. The readings will be from a variety of sources, from blogs, wiki's, journals etc.