1 / 11

Customizing VuFind

Customizing VuFind. Costs and Opportunities. Clint Bellanger - Software Developer Auburn University Libraries. Costs? VuFind is free* software!. * Zero licensing costs * Free as in Freedoms and Rights * Elbow grease not included. Common Customizations. Data Wrangling.

preston-mccoy
Download Presentation

Customizing VuFind

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. Customizing VuFind Costs and Opportunities Clint Bellanger - Software DeveloperAuburn University Libraries

  2. Costs? VuFind is free* software! * Zero licensing costs * Free as in Freedoms and Rights * Elbow grease not included

  3. Common Customizations Data Wrangling Institutional Branding ILS Integration Note: most of this work is required for every discovery tool

  4. VuFind could do exactly what you want Custom Facets Index Digital Collections Include Google Results University Log-in

  5. Levels of Customization Vendor Solution Configure VuFind Change VuFind Least Control High $$$ Cost Most Control High Staff Cost

  6. Is internal development worth it? • In-house expertise • Change is difficult • More possibilities • GPL contribution • Licensing fees • Waiting for fixes/features • Limited customization • Support safety net Vendor Solution Do It Yourself

  7. What You'll Need • Supportive and critical Research Librarians • Patron feedback • More meetings and time than you expect • But most of all ...

  8. What You'll Need (cont.) ... Mad Scientist Programmer(s)! Frankenstein, 1910.  Public Domain

  9. Case Study: Auburn University Catalog • 18 months from experimentation to Beta to default* • 1 project leader spending 50% time • 2 software developers each spending 50% time • 1 server admin spending 5% time • 1 graphic designer spending 5% time • 5-8 departmental representatives in weekly/biweekly meetings • Server costs *Development continues.  Meetings are smaller and monthly.

  10. Risks Rewards • Software project failure rate is notoriously high • Considerable staff costs • Customize too much and upgrading is painful • Google Scholar gains sentience; then what? • Less patron frustration, especially among undergrads • Increase in patron service usage • Campus-wide interest in indexing local data • Leads to publishing, seminars, and grants! • Share improvements with libraries around the world

More Related