Future Catalog
Posted on Feb 09 2010 15:03  Comments 0 / Systems Trackbacks 0

Edward want to start something. I think you could look at this site by Karen Coyle and then start your own wiki for comments.

"redeveloping our library into a local knowledge hub and to enhance participation of the local community"

Cocoon, XML, Pipelines
Posted on Feb 11 2010 21:32  Comments 0 / XML Trackbacks 0

Does it Work

The concept of "component pipelines" makes SoC easy. Each component within a pipeline is usually tasked with a particular concern. For example, rendering the same content to a Cell Phone or to a Web Browser becomes a simple matter of plugging in the appropriate "style" component into the pipeline, allowing the "styler" to work independently from the content provider.

Individual pipeline components are often compared to XML "Lego Blocks." This is because, like Lego blocks, pipeline components can be assembled into any number of configurations to quickly tailor the required XML solution. Web developers are not limited to the available component suite, but can write their own enterprise-specific "custom components" by extending existing components or by implementing the appropriate component interface.

A basic Cocoon pipeline would aggregate one or more data sources generating a single XML SAX stream that then is "piped" through the necessary transform components (including transforms that can augment content; for example, SOAP or SQL Transformers), transforming the XML as required before finally being serialized to the desired format.

Open Library Environment
Posted on Feb 17 2010 16:48  Comments 0 / Libraries Trackbacks 0

from the OLE project :

Characteristics of the OLE Framework

Flexibility: Supports a wide range of resources; accessed by a wide range of customers in a variety of contexts; provides structures for extending and adding new types of resources, customers and contexts.

Community ownership: Designed, built, owned, and governed by and for the library community on an open source licensing basis; sustained by the community with the assistance of a thriving vendor marketplace; evolves over time through transparent processes that enable and respond to input and innovation from the community.

Service Orientation: Developed using the methods of Service Oriented Architecture (SOA) and implemented with Web Services to be a modular and technology-neutral framework that ensures the interoperability of library business systems and accommodates a diversity of solutions without the risks posed by single-source providers; can be customized to support local needs.

Enterprise-Level Integration: Designed to adapt to and integrate with other enterprise systems such as research support, student information, human resources, identity management, fiscal control, and repository and content management.

Efficiency: Provides a modular application infrastructure that integrates with new and existing academic and research technologies and business processes for improved efficiency and effectiveness of the institution; meets current and future business needs of the community.

Sustainability: Creates a reliable and robust framework to identify, document, innovate, develop, maintain, and review the software necessary to further the operation and mission of libraries.