OhioLINK was excited and privileged to participate in the second annual Google Summer of Code — a program to inspire young developers and provide students in Computer Science and related fields the opportunity to do work related to their academic pursuits during the summer, and to support existing open source projects and organizations. This is the first of three posts summarizing the efforts of three students; this one details the work of Juan Pablo Garcia Ortiz, a Ph.D. candidate at the University of Almeria in Spain, to build a JPEG2000 JPIP Streaming Server and Client Browser Viewer Applet. This is an edited version of his final report.
The word “Successful” in the title, when juxtaposed with “Standards-Compliant” and “Accessible,” should be big, bold and flashing (except that the flashing style would then go against web accessibility best practice). The goal is to embed a video clip into a web page that validates as “XHTML4.01 Transitional”, includes a Closed Captioning text track to be displayed in the web page, and could be viewed in one of three flavors: Windows Media, QuickTime, and Real. And the content being presented is about using accessible technologies in the classroom, so it had to be “right.” This task was much harder than I thought, and I’ll offer much harder than it should have been. Piecing together sources too numerous to mention, I managed to make it happen … with just a few caveats. Here, documented for all time, or at least until dltj.org goes away or the next major browser/streaming-client revision (which ever comes first) is how it can be done.
No Service Oriented Architecture posting today, but here is a glimpse of the topic of the next one — the title is: “Web Services: A means to a Service Oriented Architecture end.” In the meantime I wanted to thank everyone for their public and private comments, and to ask to keep ‘em coming. The big push for writing about SOA this week was a lead up to a meeting of the OhioLINK Technical Advisory Council (TAC) today. On TAC’s agenda was a question about looking at SOA as a design strategy for new and migrated services. These blog postings served several purposes: 1) propel the topic a little further in the library community [presupposing that it was a worthy topic]; 2) serve as background information for today’s meeting; 3) flush out comments from the library community [which it did -- thanks again!]; and 4) form the basis of a whitepaper on SOA at OhioLINK. TAC agreed to keep looking at it and endorsed the writing of the whitepaper. Keep the comments and observations coming!
This is part three of a continuing series on the application of the Service Oriented Architecture (SOA) design pattern to library systems. In the first part, the SOA concept was compared to a transportation network and the basic foundation for defining SOA was set down. The second part described what a “service” in SOA could be and proposed an example using OCLC’s WorldCat interface with item status information being pulled from a library catalog system. That part also left off with a teaser about the juxtaposition of “inventory control system” with “local catalog system” — a foreshadowing of the topic of this post: what to do about the Monolithic (er… “Integrated”) Library System.
This post is the second in a series about the application of the Service Oriented Architecture (SOA) system design pattern to library services. The first post in this series focused on defining “Service Oriented Architecture” using the analogy of a transportation network. This post goes into some detail about what makes a “service” in this architecture and offers an example using a hypothetical use case: a union library catalog (Open WorldCat) making a statement about the availability of a book.
This post is the first in a series over the next few days that in total will attempt to lay the groundwork for a discussion of applying the Service Oriented Architecture (or SOA) software design pattern to systems and solutions in the library space. It starts with comparing the SOA concept with a multi-modal transportation network. Subsequent posts will outline use cases and describe how SOA can be applied to libraries.
Theis of the high-level sense of passion and commitment inherent in the Fedora community. I’ve posted some answers back to the FEDORA wiki on behalf of OhioLINK, and am also including the responses here as it fits into the “Why FEDORA?” series of blog postings. (If you are reading this through a RSS news reader, I think you’ll have to actually come to the DLTJ website and scroll down to the bottom of this post to see the table of contents of the series.) On with the responses!
Where can faculty, administrators, librarians and technology gurus all meet to discuss learning, libraries, technology and the convergence of these activities? At the– The Convergence of Learning, Libraries and Technology Conference, of course!
Be a part of ODCE 2007! The Ohio Digital Commons for Education partners — Ohio Learning Network, OhioLINK, and the Ohio Supercomputer Center/OARnet — are seeking interactive and engaging proposals for presentations, pre-conference workshops and technology demonstrations. Proposals are sought for the following topics:
- E Squared – Effectiveness and Efficiencies
- STEM2: Science, Technology, Engineering, Mathematics and Medicine
Up until about an hour ago, Technorati refused to update, and having reached the 31-day point of no updates I was starting to wonder what to do about it. I came up with two theories for which I put in fixes to the configuration and theme setup of DLTJ, but in the end I’m not sure if either definitively provides a solution for anyone else in the same situation. In the spirit of helping out one’s neighbors, though, here are the theories and fixes. DLTJ is a standalone (e.g. not hosted) WordPress 2.0.4 installation, so YMMV.
Okay — this seemed like a lot harder than it should have been. At the very least, it took piecing together information from a number of places in order to make it happen. The goal is to use a Go Daddy Turbo SSL Secure Certificate (the $19.95/year one) to secure an OpenLDAP server. On the surface, this shouldn’t be so hard. The tricky part comes because the requested SSL cert is not signed by a recognized Certificate Authority root; instead, Go Daddy uses an intermediary certificate and the tricky part is making sure the whole chain of SSL certificates line up properly. There is a wealth of documentation for using intermediary certificates with web servers, but I found very little for OpenLDAP servers. I hope by posting this into the blogosphere you will find it useful someday, too.