ole project webinr - conversation with cufts april 8 2009
DESCRIPTION
Conversation with Brian Owen and Kevin Stranack about CUFTSTRANSCRIPT
OLE Project & CUFTS (Open Source Serials Management)
a Webinar ConversationFeaturing Brian Owen, Associate University Librarian
& Kevin Stranack, reSearcher Associateof 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 1.the CUFTS
(Open Source Serials Management) application
2.The CUFTS Knowledgebase and the potential for being community maintained
Questions Continued
1.What is the roadmap for the future of CUFTS?
2.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 reportso Customizable interfaceso Import/export tools- Major code refactoring. Commence development on following:o Perl Moose support where appropriateo ORM / database / models enhancementso Business logic into data models, also unit testing for data modelso Switch to DBIx::Class from Class::DBo Investigate database type options for some data, e.g. COUCHdb- Rest APIs for data- CJDB and CRDB:o Template clean-upo 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 linkso ISSN display relocationo 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 APIso Move CUFTS public tools to standalone modeo Move to Chained Catalyst dispatcho 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
1.How can other libraries use CUFTS services model to match local workflows?
2.Who has been involved in CUFTS development?
3.How have the features been vetted?
Questions/Topics
1.Has CUFTS code been constructed as a SOA implementation? What is the potential for interoperability with other SOA applications?
2.What is the code-base? 3.How do you document library workflows?
Do you use formal BPM notation?
Questions Continued
1.What are the plans for governance, specifically with respect to identifying feature enhancements, support, and sustainability?
2.How should a library think about budgeting for CUFTS or other Open Source applications?
3.Lessons learned (good/bad/ugly)
Questions Continued
1.What documentation is currently available or being prepared for CUFTS?
2.Has an implementation tool/package been developed to assist in the installation of the CUFTS software at other sites?
3.Are there any non-SFU partners or developers currently contributing to the CUFTS codebase or supporting the project in other ways?
4.Is there an online support forum associated with CUFTS.
Panelists / Organizer
• Brian Owen, Associate University [email protected]
• Kevin Stranack, reSearcher Associate [email protected]
• John Little, ILS Support Section [email protected]
• Michael Winkler, Director of IT at University of Pennsylvania [email protected]