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

Questions/Topics Overview of the CUFTS (Open Source Serials Management) application The CUFTS Knowledgebase and the potential for being community maintained

Overview of

the CUFTS (Open Source Serials Management) application

The CUFTS Knowledgebase and the potential for being community maintained

Questions Continued What is the roadmap for the future of CUFTS? What is the timeline for development and release of future services?

What is the roadmap for the future of CUFTS?

What is the timeline for development and release of future services?

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

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

Questions Continued How can other libraries use CUFTS services model to match local workflows? Who has been involved in CUFTS development? How have the features been vetted?

How can other libraries use CUFTS services model to match local workflows?

Who has been involved in CUFTS development?

How have the features been vetted?

Questions/Topics Has CUFTS code been constructed as a SOA implementation? What is the potential for interoperability with other SOA applications? What is the code-base? How do you document library workflows? Do you use formal BPM notation?

Has CUFTS code been constructed as a SOA implementation? What is the potential for interoperability with other SOA applications?

What is the code-base?

How do you document library workflows? Do you use formal BPM notation?

Questions Continued What are the plans for governance, specifically with respect to identifying feature enhancements, support, and sustainability? How should a library think about budgeting for CUFTS or other Open Source applications? Lessons learned (good/bad/ugly)

What are the plans for governance, specifically with respect to identifying feature enhancements, support, and sustainability?

How should a library think about budgeting for CUFTS or other Open Source applications?

Lessons learned (good/bad/ugly)

Questions Continued What documentation is currently available or being prepared for CUFTS? Has an implementation tool/package been developed to assist in the installation of the CUFTS software at other sites? Are there any non-SFU partners or developers currently contributing to the CUFTS codebase or supporting the project in other ways? Is there an online support forum associated with CUFTS.

What documentation is currently available or being prepared for CUFTS?

Has an implementation tool/package been developed to assist in the installation of the CUFTS software at other sites?

Are there any non-SFU partners or developers currently contributing to the CUFTS codebase or supporting the project in other ways?

Is there an online support forum associated with CUFTS.

Panelists / Organizer Brian Owen , Associate University Librarian [email_address] Kevin Stranack, reSearcher Associate [email_address] John Little, ILS Support Section Head [email_address] Michael Winkler, Director of IT at University of Pennsylvania Libraries [email_address]

Brian Owen , Associate University Librarian [email_address]

Kevin Stranack, reSearcher Associate [email_address]

John Little, ILS Support Section Head [email_address]

Michael Winkler, Director of IT at University of Pennsylvania Libraries [email_address]