Six important factors to consider before choosing a technology jon solomon


Published on

Choosing the technology before knowing the goals of a project is a common mistake. Often this leads to a feeling the library or a project group is “implementing technology for technology’s sake.” To ensure you are selecting the right technology, it is important to ensure the proper research and attention is paid to matching project and library needs with the right technology.
In this session, we will guide you through six important areas for consideration, prior to choosing a technology; these steps will allow you to complete side-by-side comparisons that will help you make a good decision for the best service outcome. We will also offer an opportunity to review these six concepts through a high level practical exercise by reviewing these steps for selecting a Content Management System (CMS).

Published in: Technology, Education
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Why 6? Just cuz…
  • Technology for technology’s sake:Qr codesBlogs (contra didn’t do)Wikis (contra did do) – also shows that there can be times when you just have to select a technology in order to meet a service goal, then re-evaluateOthers?
  • You can still have vendors to consider, even if your technology is open sourceComparing calendaring software
  • Of the products reviewed, which meets your feature needs best?Is getting more than you need a benefit or detriment to your library?Impacts on implementationImpacts of learning/useAllows for future growth and increased usageWhen is ‘more’ too much? (federated search w/aquabrowser)Customization is huge – what is meant by it? How much customization? – SD Enterprise demo example (“fully customizable”)
  • Vendor Track Record for On Time DeliveryWhat library staff is needed and when (project stage)?Call References!
  • What library resources are needed for ongoing support?Daily, weekly, annuallyCan you afford Open Support?Existing talent and knowledgeGrowing additional/back-up supportDocumentation and knowledge warehousingHardware, peripherals, backupsIT staff limitedDoes the CMS you purchase offer a hosted solution?Is your library website supported through library backup policies or can the CMS offer a back-up solution?
  • The service goal is a new web site. The technology has not been defined yet. Do we need a CMS?Good article on creating your business case; determining features needed –
  • ScalabilityAccessibilityEase of use (wysiwyg)
  • Revize CMS – lots of customization options. Too much?ILS integration?Searching performance?
  • Six important factors to consider before choosing a technology jon solomon

    1. 1. A Guide to Making the Right Decision forYour Library
    2. 2.  Know your mission/vision Prototype/proof of concept Avoid techno-lust Define what technology isneeded, based on y0urservice goals
    3. 3.  Price matters, but is not everything More expensive does not necessarilymean better Consider staff time spent inimplementation and support Add-on costs Total cost of ownership Open Source Hosting
    4. 4.  Determining what is out there; narrowthe field Case studies Product comparisons Demos Vendors References Keep current – often outside of library-land
    5. 5.  Core functionality: how does thismeet your needs? Overcoming feature overdose Integration with other products/ILS Customization
    6. 6.  Vendor Success Project Success ProjectTimelines Library Resources Needed Check References!
    7. 7.  What library resources are needs for ongoing support? What can the vendor offer? Training Documentation Can you ‘afford’ Open Source? LibraryAssets Needs:Staff and IT Infrastructure Support and Service Levels (SLAs) Hosting Options
    8. 8. For the remaining portion of this session, we will walk through theseaforementioned “six steps” for choosing the right Content ManagementSystem (CMS) to enhance the AnyTown Library’sWeb presence.1. Project Objective1. Budget1. Research2. Feature Match1. Implementation1. Support Needs
    9. 9. AnyTown Library’sWeb Site Initiative1. Project ObjectiveAnyTown Library is interested in increasing their web presence but offering information abouthours, summer reading, and also information about library events to their community. Thelibrary currently has 1 FTE for web site management and would like a librarian from their staffto participate in publishing information to the website without the need for an IT or web staffmember to intervene.The CMS will be used for the library’s customer facing website. The library would like to offerlinks to a few community (external) resources and post press releases and other documents tothe website.Library stakeholders believe this new initiative will enhance the user experience and offer animproved presentation of the library to it’s service community, once completed.
    10. 10. Identifying Requirements: There is no single best list of requirements for a content management system. Everyorganization has unique needs. Involve all your stakeholders in the requirements process.This includes relevant IT groups,business/library units, and end users. This is particularly important if you are purchasing an “enterprise-wide” CMS.
    11. 11. 2. BudgetThe library has proudly set aside $10K for funding this project; additionally, they have sharedthat this is a priority for the web site manager and feel that staff from throughout the librarysystem can contribute by offering book reviews, posting event information and keeping hoursand other information up-to-date.3. Research What products exist for your budget? What do they offer? Seek information in articles and online: What of these options meet your budgetary needs? May require a bit more review of specific software
    12. 12. AnyTown Library’sWeb Site Initiative4. Feature Match Of the products reviewed, which meets your feature needs best? Is getting more than you need a benefit or detriment to your library? Impacts on implementation Impacts of learning/use Allows for future growth and increased usage When is ‘more’ too much? Set-Up Demonstrations5. Implementation VendorTrack Record for OnTime Delivery What library staff is needed and when (project stage)? Call References!
    13. 13. AnyTown Library’sWeb Site Initiative6. Support Needs What library resources are needed for ongoing support? Daily, weekly, annually Can you afford Open Source? Existing talent and knowledge Growing additional/back-up support Documentation and knowledge warehousing Hardware, peripherals, backups IT staff limited Does the CMS you purchase offer a hosted solution? Is your library website supported through library backup policies or can the CMS offer aback-up solution?
    14. 14. Any Additional Questions?What are yourTake-Aways?Resources: CMS Research