`THE OPEN LIBRARY ENVIRONMENT PROJECT: RECONCEPTUALIZING TECHNOLOGY FOR  MODERN LIBRARY WORKFLOWS KLA / CULS Fall Conferen...
Today’s ILS Environment <ul><li>Does not fit modern scholarly process </li></ul><ul><li>Workflows designed to manage colle...
Tomorrow’s ILS Environment? <ul><li>Libraries want a system that is: </li></ul><ul><ul><li>Flexible </li></ul></ul><ul><ul...
<ul><li>Current open source projects do address  some  aspects of current ILS limitations </li></ul><ul><ul><li>Great plac...
How Do We Achieve That? <ul><li>Convene the academic library community to design an open, reconceptualized library managem...
<ul><li>Solicitation of interest – last spring </li></ul><ul><ul><li>Over 100 academic libraries – large & small, public &...
<ul><li>Base design on Service Oriented Architecture principles </li></ul><ul><ul><li>Training with SOA expert consultant ...
<ul><li>SOA = Service Oriented Architecture </li></ul><ul><li>Design approach </li></ul><ul><ul><li>Independent software p...
Before & After SOA
<ul><li>BPM = Business Process Modeling </li></ul><ul><li>Design approach </li></ul><ul><li>BPM process </li></ul><ul><ul>...
<ul><li>Flexible, adaptable, and community-developed software framework for managing libraries that support research, teac...
<ul><li>Supports wide range of resources, accessed by wide range of customers, in a variety of contexts </li></ul><ul><li>...
<ul><li>Designed to adapt to & integrate with other enterprise systems such as research support, student information, HR, ...
<ul><li>Design of a reference implementation that support  basic  functionality of legacy ILS products </li></ul><ul><li>S...
<ul><li>System architecture definition </li></ul><ul><li>Service Oriented Architecture design will be used </li></ul><ul><...
<ul><li>Capacities to migrate legacy library data </li></ul><ul><li>Schematic framework enabling integration and interoper...
<ul><li>Develop a generalized, extensible concept of a resource that represents variety of entities, both physical & virtu...
<ul><li>Support for variety of user and administrative interfaces </li></ul><ul><li>Reference implementation will conform ...
<ul><li>Beginning to outline basic functions and processes that will be supported </li></ul><ul><li>Will need community in...
OLE Project Activities & Plans <ul><li>Weekly conference calls for Core & Advisory Partners </li></ul><ul><li>First in-per...
<ul><li>What happens once we have a design document? </li></ul><ul><li>Starting to gather information on institutions inte...
<ul><li>OLE Project is dependent on active participation by as many libraries as possible to reflect full range of ideas <...
<ul><li>Questions or Comments?? </li></ul><ul><li>oleproject.org </li></ul>Mary Roach Assoc. Dean, Technical Services Univ...
Upcoming SlideShare
Loading in …5
×

OLE Project - CULS Presentation

670
-1

Published on

Presentation on the OLE Project to the College & University Libraries Section, Kansas Library Association, Lawrence, KS, Oct. 24 2008

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
670
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
48
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • OLE Project - CULS Presentation

    1. 1. `THE OPEN LIBRARY ENVIRONMENT PROJECT: RECONCEPTUALIZING TECHNOLOGY FOR MODERN LIBRARY WORKFLOWS KLA / CULS Fall Conference October 24, 2008 Mary Roach Associate Dean, Technical Services University of Kansas Beth Forrest Warner Officer for Grants, Research Support & Library Assessment, University of Kansas
    2. 2. Today’s ILS Environment <ul><li>Does not fit modern scholarly process </li></ul><ul><li>Workflows designed to manage collections based on outdated assumptions </li></ul><ul><li>Collections changing more rapidly that systems: </li></ul><ul><ul><li>Data </li></ul></ul><ul><ul><li>Mass digitization </li></ul></ul><ul><li>Result? Dissatisfaction with current systems </li></ul>
    3. 3. Tomorrow’s ILS Environment? <ul><li>Libraries want a system that is: </li></ul><ul><ul><li>Flexible </li></ul></ul><ul><ul><li>Agile </li></ul></ul><ul><ul><li>Customizable </li></ul></ul><ul><ul><li>Able to address the challenging and changing complex needs of modern academic / institutional libraries </li></ul></ul><ul><ul><li>Responsive to new technologies and to scholars’ information needs and expectations </li></ul></ul><ul><ul><li>Community Open Source-based </li></ul></ul>
    4. 4. <ul><li>Current open source projects do address some aspects of current ILS limitations </li></ul><ul><ul><li>Great place to start, but it is time for a somewhat different approach </li></ul></ul><ul><li>Time to completely rethink current approach & functionality for today’s academic library management system </li></ul><ul><li>Can build on, and expand from, current systems </li></ul><ul><ul><li>Apply Service Oriented Architecture (SOA) principles for flexibility, agility, interoperability </li></ul></ul><ul><ul><li>Apply Business Process Modeling to identify and standardize basic core processes </li></ul></ul><ul><ul><li>Place more focus on integration with other enterprise systems </li></ul></ul>Hasn’t This Problem Been Solved?!
    5. 5. How Do We Achieve That? <ul><li>Convene the academic library community to design an open, reconceptualized library management system to meet today’s – and tomorrow’s – information management needs </li></ul><ul><li>Secure project funding </li></ul><ul><li>Identify project participants </li></ul><ul><li>Create design specifications </li></ul><ul><li>Develop new system </li></ul>
    6. 6. <ul><li>Solicitation of interest – last spring </li></ul><ul><ul><li>Over 100 academic libraries – large & small, public & private, and other national / large research & archives responded positively </li></ul></ul><ul><ul><li>Core group selected to submit </li></ul></ul><ul><ul><li>proposal to The Andrew W. </li></ul></ul><ul><ul><li>Mellon Foundation </li></ul></ul><ul><ul><li>Proposal funded for $495,700 </li></ul></ul><ul><ul><ul><li>1-year project </li></ul></ul></ul><ul><ul><ul><li>Design phase </li></ul></ul></ul><ul><ul><ul><li>6 Core Partners </li></ul></ul></ul><ul><ul><ul><li>10 Advisory Participants </li></ul></ul></ul><ul><ul><ul><li>Timeframe – Sept to July 2009 </li></ul></ul></ul>Project Beginnings Core Partners Advisory Duke University Columbia Univ. Lehigh University Orbis Cascade Cons. Library & Archives Canada Rutgers Univ. National Library of Australia Univ of Chicago University of Kansas Univ of Florida University of Pennsylvania Univ of Maryland Marshall Breeding Whittier College
    7. 7. <ul><li>Base design on Service Oriented Architecture principles </li></ul><ul><ul><li>Training with SOA expert consultant </li></ul></ul><ul><ul><li>Goal: Design higher-level workflows for major library operations </li></ul></ul><ul><li>Use Business Process Modeling principles to analyze processes </li></ul><ul><ul><li>Training with BPM expert consultant </li></ul></ul><ul><ul><li>Goal: Standardized methodology to describe library business processes to inform workflow development </li></ul></ul><ul><li>Gather community input to inform system design </li></ul><ul><ul><li>Webcasts, website for comments </li></ul></ul><ul><ul><li>Regional BPM meetings to gather process input </li></ul></ul><ul><li>Working meetings of partners to: </li></ul><ul><ul><li>Conduct workflow analysis </li></ul></ul><ul><ul><li>Produce business process specifications </li></ul></ul><ul><li>Produce design document to inform development </li></ul><ul><ul><li>Draft for community comment late spring 2009 </li></ul></ul><ul><ul><li>Final design document and report to Mellon Foundation in July 2009 </li></ul></ul><ul><li>Begin working on proposal to Mellon Foundation for build phase </li></ul>What Will We Do?
    8. 8. <ul><li>SOA = Service Oriented Architecture </li></ul><ul><li>Design approach </li></ul><ul><ul><li>Independent software pieces </li></ul></ul><ul><ul><li>Pieces can be interchanged or repurposed more easily </li></ul></ul><ul><ul><li>Pieces can be combined to create new services or systems </li></ul></ul><ul><ul><li>Business experts and IT experts work together </li></ul></ul><ul><li>SOA Process </li></ul><ul><ul><li>Create high-level map of how the business should work </li></ul></ul><ul><ul><li>Deconstruct workflows </li></ul></ul><ul><ul><li>Define reusable services </li></ul></ul><ul><ul><li>Recombine services into a system that meets our requirements </li></ul></ul><ul><li>Think Legos™! </li></ul>What Is SOA??
    9. 9. Before & After SOA
    10. 10. <ul><li>BPM = Business Process Modeling </li></ul><ul><li>Design approach </li></ul><ul><li>BPM process </li></ul><ul><ul><li>What needs to be done </li></ul></ul><ul><ul><li>How to do it </li></ul></ul><ul><ul><li>Separate from the systems and services that do the work </li></ul></ul><ul><ul><li>Mid-level detail </li></ul></ul><ul><ul><li>As-Is vs. To-Be process definitions </li></ul></ul><ul><li>Synergistic with SOA </li></ul>What is BPM??
    11. 11. <ul><li>Flexible, adaptable, and community-developed software framework for managing libraries that support research, teaching, and higher learning </li></ul><ul><ul><li>Seeks to improve how ILS software serves library mission </li></ul></ul><ul><ul><li>Transforms support for core business processes to address evolving practices </li></ul></ul><ul><ul><li>Software development & governance are community-based </li></ul></ul><ul><ul><li>Focuses on better integration of ILS functionality into institutional cyber infrastructure </li></ul></ul><ul><ul><li>Complements human interactions, reducing repetitive tasks, freeing staff to focus on higher value support to researchers & scholars </li></ul></ul><ul><ul><li>Scalable support for high levels of service & low incremental cost </li></ul></ul>Scope Statement: Vision
    12. 12. <ul><li>Supports wide range of resources, accessed by wide range of customers, in a variety of contexts </li></ul><ul><li>Provides structures for extending & adding new types of resources, customers, and contexts </li></ul><ul><li>Designed, built, owned, and governed by and for the library community on an open-source licensing basis </li></ul><ul><li>Developed using SOA methods in a modular and technology-neutral framework that ensures interoperability of library business systems with variety of solutions to avoid risk of single-vendor dependencies </li></ul>Scope: Principles
    13. 13. <ul><li>Designed to adapt to & integrate with other enterprise systems such as research support, student information, HR, repositories, etc. </li></ul><ul><li>Provides modular application infrastructure that integrates with new & existing academic and research technologies and business processes for current and future business needs of the community </li></ul><ul><li>Creates reliable & robust framework for identification, documentation, innovation, development, maintenance, and review of software necessary to furthering mission & operation of libraries </li></ul>Scope: Principles (cont.)
    14. 14. <ul><li>Design of a reference implementation that support basic functionality of legacy ILS products </li></ul><ul><li>Support functions beyond existing ILS core </li></ul><ul><li>Expect functional scope to expand and evolve – OLE broadens current notion of ILS to incorporate / support additional functions such as: </li></ul><ul><ul><li>Manage intellectual property and rights </li></ul></ul><ul><ul><li>Build and maintain content repositories </li></ul></ul><ul><ul><li>Link content with learning management systems </li></ul></ul><ul><ul><li>Facilitate authentication & authorization </li></ul></ul><ul><ul><li>Integrate with institution-wide financial services </li></ul></ul>Scope: Business Processes
    15. 15. <ul><li>System architecture definition </li></ul><ul><li>Service Oriented Architecture design will be used </li></ul><ul><li>Service contract specification that enables development by larger community without restriction to original developers </li></ul><ul><li>Data models & possible standards implied by SOA; replication of mature & interoperable functionality </li></ul>Scope: Architecture & Data Models
    16. 16. <ul><li>Capacities to migrate legacy library data </li></ul><ul><li>Schematic framework enabling integration and interoperability with campus, institutional, or national systems with respect to range of enterprise functions </li></ul><ul><li>Support for consortial applications of OLE software </li></ul><ul><li>Facilitation of inter-institutional cooperative programs </li></ul><ul><li>Integration with external data services such as OCLC, ILL services, resource vendors, etc. </li></ul>Scope: Integration & Interoperability
    17. 17. <ul><li>Develop a generalized, extensible concept of a resource that represents variety of entities, both physical & virtual </li></ul><ul><li>Development of logical requirements that support role-based actions and responsibilities </li></ul><ul><li>Support business logic needed for interoperability </li></ul><ul><li>Management of security relationships between systems to ensure stability & data integrity </li></ul><ul><li>Data governance & security to support individual privacy </li></ul><ul><li>Support federated authentication / authorization technology </li></ul>Scope: Data Governance & Security
    18. 18. <ul><li>Support for variety of user and administrative interfaces </li></ul><ul><li>Reference implementation will conform to community developed specification for interoperability </li></ul><ul><li>Services will be configurable to accommodate community, disciplinary, and format-specific taxonomies </li></ul>Scope: Discovery & User Experience
    19. 19. <ul><li>Beginning to outline basic functions and processes that will be supported </li></ul><ul><li>Will need community input and interaction to fully define and develop these functions </li></ul>Scope: Basic ILS Functions
    20. 20. OLE Project Activities & Plans <ul><li>Weekly conference calls for Core & Advisory Partners </li></ul><ul><li>First in-person meeting held at Duke University </li></ul><ul><ul><li>Training in SOA principles and approaches </li></ul></ul><ul><ul><li>Scope document refinement </li></ul></ul><ul><ul><li>Community participation planning </li></ul></ul><ul><li>First open Webcast held </li></ul><ul><li>2 nd in-person meeting scheduled for Nov. 6-8 at Rutgers University </li></ul><ul><ul><li>Training on Business Process Modeling (BPM) methodologies </li></ul></ul><ul><li>Regional meetings to gather input on business processes (Nov./Dec.) </li></ul><ul><li>Additional SOA training & open webcasts planned </li></ul><ul><li>Draft report out for general comment & review late next spring </li></ul><ul><li>Report / design document due in July 2009 </li></ul>
    21. 21. <ul><li>What happens once we have a design document? </li></ul><ul><li>Starting to gather information on institutions interested in participating in a build phase </li></ul><ul><li>Will begin working on proposal to Mellon Foundation for build phase funding this winter </li></ul><ul><li>Intent is to have proposal for build phase to Mellon Foundation next summer </li></ul>OLE Project Activities & Plans
    22. 22. <ul><li>OLE Project is dependent on active participation by as many libraries as possible to reflect full range of ideas </li></ul><ul><li>Stay current on project developments via the project website ( oleproject.org ) </li></ul><ul><li>Provide feedback on documents and reports </li></ul><ul><li>Participate in webcasts </li></ul><ul><li>Consider becoming an active partner for the build phase </li></ul><ul><li>Participate in regional project meetings </li></ul><ul><ul><li>KU is planning a business process meeting in late Nov/early Dec. – watch for announcement with details soon! </li></ul></ul>Getting Involved
    23. 23. <ul><li>Questions or Comments?? </li></ul><ul><li>oleproject.org </li></ul>Mary Roach Assoc. Dean, Technical Services University of Kansas [email_address] Beth Forrest Warner Officer for Grants, Research Support & Library Assessment, University of Kansas [email_address]

    ×