OLE Project Webinr - Conversation with CUFTS April 8 2009


Published on

Conversation with Brian Owen and Kevin Stranack about CUFTS

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

  • Be the first to like this

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

No notes for slide

OLE Project Webinr - Conversation with CUFTS April 8 2009

  1. 1. OLE Project & CUFTS (Open Source Serials Management) a Webinar Conversation Featuring Brian Owen, Associate University Librarian & Kevin Stranack, reSearcher Associate of Simon Fraser University Moderated by John Little, Duke University & Michael Winkler, University of Pennsylvania Presented by the Connecting with Other Projects Working Group, OLE Project
  2. 2. Questions/Topics <ul><li>Overview of </li></ul><ul><ul><li>the CUFTS (Open Source Serials Management) application </li></ul></ul><ul><ul><li>The CUFTS Knowledgebase and the potential for being community maintained </li></ul></ul>
  3. 3. Questions Continued <ul><ul><li>What is the roadmap for the future of CUFTS? </li></ul></ul><ul><ul><li>What is the timeline for development and release of future services? </li></ul></ul>
  4. 4. DEVELOPMENT ROADMAP FOR CUFTS ERM (revised Dec.15, 2008)   2009: Q1 & Q2     - Complete 2008 items: o Statistical and other reports o Customizable interfaces o Import/export tools - Major code refactoring. Commence development on following: o Perl Moose support where appropriate o ORM / database / models enhancements o Business logic into data models, also unit testing for data models o Switch to DBIx::Class from Class::DB o Investigate database type options for some data, e.g. COUCHdb - Rest APIs for data - CJDB and CRDB: o Template clean-up o Improved caching, handling of static resources, logged in/out status-CUFTS public tools: bug fixes and various enhancements - Email notification function in workflow - OCLC e-serials holdings reporting using Google Scholar standard - Online help and documentation revisions - Minor interface enhancements: o Additional padding under “red alerts” o Titles highlighted as links o ISSN display relocation o Embargo period: text changes for display note - MARC data mapping for Order data from Innovative - Investigate options for integrating dbWiz and CUFTS subject profiles maintenance
  5. 5. DEVELOPMENT ROADMAP FOR CUFTS ERM (revised Dec.15, 2008)   2009: Q3 & Q4 - Complete major code refactoring and related clean-up - Complete API work - Job queuing system for background updates, e.g. data loads - Commence internationalization support: codebase preparation, e.g. add language layer - UNICODE for all data - Updates scheduler for resources - Basic editor for public notes field - Statistical enhancements: cost/usage; access log info.   2010 and on: Under consideration   - Full internationalization support, e.g. all interfaces, data in multiple languages - Maintenance tool rewrite: o Javascript-centric interface using REST APIs o Move CUFTS public tools to standalone mode o Move to Chained Catalyst dispatch o Online help improvements - Autonotification options in workflow, e.g. email requesting new catalogue entry - Integrated dbWiz and CUFTS subject profiles maintenance - Licence data import/export, e.g. ONIX PL? - Integrated link checking tool
  6. 6. Questions Continued <ul><ul><li>How can other libraries use CUFTS services model to match local workflows? </li></ul></ul><ul><ul><li>Who has been involved in CUFTS development? </li></ul></ul><ul><ul><li>How have the features been vetted? </li></ul></ul>
  7. 7. Questions/Topics <ul><ul><li>Has CUFTS code been constructed as a SOA implementation? What is the potential for interoperability with other SOA applications? </li></ul></ul><ul><ul><li>What is the code-base? </li></ul></ul><ul><ul><li>How do you document library workflows? Do you use formal BPM notation? </li></ul></ul>
  8. 8. Questions Continued <ul><ul><li>What are the plans for governance, specifically with respect to identifying feature enhancements, support, and sustainability? </li></ul></ul><ul><ul><li>How should a library think about budgeting for CUFTS or other Open Source applications? </li></ul></ul><ul><ul><li>Lessons learned (good/bad/ugly) </li></ul></ul>
  9. 9. Questions Continued <ul><ul><li>What documentation is currently available or being prepared for CUFTS? </li></ul></ul><ul><ul><li>Has an implementation tool/package been developed to assist in the installation of the CUFTS software at other sites? </li></ul></ul><ul><ul><li>Are there any non-SFU partners or developers currently contributing to the CUFTS codebase or supporting the project in other ways?  </li></ul></ul><ul><ul><li>Is there an online support forum associated with CUFTS. </li></ul></ul>
  10. 10. Panelists / Organizer <ul><ul><li>Brian Owen , Associate University Librarian [email_address] </li></ul></ul><ul><ul><li>Kevin Stranack, reSearcher Associate [email_address] </li></ul></ul><ul><ul><li>John Little, ILS Support Section Head [email_address] </li></ul></ul><ul><ul><li>Michael Winkler, Director of IT at University of Pennsylvania Libraries [email_address] </li></ul></ul>