Top Ten List: Number Two

From the Library Technology Conference:

Getting Back into the Library Business: Moving Library IT to the Cloud, Marc Davis, Drake University

• Marc Davis began by noting there can be a resistance to completely dismantling the server systems we have depended on and invested money in. The goal with cloud computing is to refocus our attention away from the hardware and back onto service. The assumption is that cloud computing is inevitable, at least to some extent, as the "old" server infrastructure is inefficient to sustain in the long run. By sharing on an extremely large-scale resulting electricity costs, network bandwidth, operations, software, and hardware costs were dramatically decreased as compared to providing similar results via local servers. Other benefits include elasticity and transference of risk. Cloud computing is not necessarily web based, rather services outside of the campus firewall. This may include using software and storing data outside of the library.
• Three terms to know:
  
  • SAAS: Software as a Service: use of hosted services, i.e. Springshare Libguides; though you have no access to the underlying infrastructure, you are also not responsible for managing the underlying software
  • Infrastructure as a Service: is "Utilizing a provided server environment but retaining responsibility for configuration and operation" i.e. Amazon Web Services
  • PAAS: Platform as a Service is an environment that supports "building, testing, and deploying (Web-based) applications" i.e. Windows Azure, twilio, and Boopsie (discussed in this post)
• Moving IT infrastructure elsewhere, to vendors or others out-of-house (i.e. centralized campus IT) is one characteristic of Library Cloud migration. Of course, you need to make sure that what your doing meets your needs, both financially and in terms of your goals and priorities). At Drake, they moved the information they supported on their servers from the library to a centralized IT location.
• An interesting question Marc Davis brought up was: are libraries uniquely positioned to migrate from on-site to cloud IT? While libraries do have expertise with hosted solutions, contracts, and discovery layer services, and are part of a service-rich environment, they may not necessarily be uniquely positioned because such services must be considered with local needs/conditions, sustainability, organizational culture, and other factors specific to the users you serve in mind. If there is extreme resistance based on campus culture, or concerns over information security, cloud computing may be dismissed as an IT possibility for where you are.
• Benefits of Cloud Migration
  • Experience vs. Hype: cost effectiveness, keeping in mind availability, data integrity (continuous back-up), provisioning, capacity (bandwidth); cloud costs tend to be more predictable, identifiable, and incrementally adjustable (to align with actual usage amounts)
  • Flexibility: quick service without infrastructure costs or system administrator duties, the focus is moved from hardware/operating systems to service
  • Innovation: service effectiveness, budgeting and planning, partnerships develop into collaborations
  • IT Skills: IT professionals develop managerial, project management, and budgeting/contract skills
• Services:
  
  • Free (SAAS-like): Meebo, Vimeo, Dropbox, Social networks
  • Hosted Services (SAAS): ILLiad by OCLC, Docutek E-reserves by SirsiDynix, DSpace by Longsight, ContentDM by OCLC, Wikis (i.e. Wikispaces, PB Works), Springshare Libguides, Discovery by Ebsco Discovery Service, Web Help Desk by MacsDesign Studio
• Drake is looking to continuing the transfer of resources from on-site IT to the cloud over the next several years (with a select few pieces remaining on-site for security or licensing reasons). While some of their data is processed through on-campus, centralized servers, other is done off-campus. You may learn more about the details of this transition in the presentation found here.