Although we were a little concerned right about this time last week, you came through with a wonderful suite of applications with OhioLINK as the mentoring organization for the Google Summer of Code. In the end, we are blown away not only by the increase in quantity over last year, but also the quality as well. We received seven for the video snapshot idea, five for the grid-based bulk video conversion tool, one each for the JPIP-based disseminator and applet client, plus a half-dozen proposals for things we didn’t have on .
Calling all accessibility technology experts! What follows is a line of thinking about using characteristics of the FEDORA digital object repository to enable access to content through non-graphical interfaces. Thanks to Linda Newman from the University of Cincinnati and others on the Friday morning DRC Developers conference call for triggering this line of thinking.
In a recent post defining universal disseminators for every object in our repository (if the last dozen words didn’t make sense, please read the linked article and come back), I hinted at having an auditory derivative of each object, at least at the preview level. During today’s conference call, Linda asked if such a disseminator could be used to offer different access points for non-GUI users. Well, why not? Let’s look back at the “presentation” part of the disseminator label:
Michael J. Giarlo wrote a very nice summary of my FEDORA trilogy (only three parts so far — I think there are more good things to say about FEDORA; and besides, I like Douglas Adams’ concept of what a trilogy should be), and added a piece that I hadn’t considered:
- Having one’s objects stored as XML on the filesystem also opens up opportunities to see how tools which act thereupon might be glued into the repository infrastructure. One such example might be for an XML-aware search engine (such as amberfish, Lucene, or Zebra). Since you’ve got low-level access to these files, it would be fairly simple to tack on a search & indexing system that is independent of your choice of repository.
Another reason to consider the FEDORA digital object repository system, if having the ability to put all of your content in one place and reducing the complexity of digital preservation aren’t enough, is the capability to create and define behaviors that the content can perform. In the FEDORA world, these behaviors are called disseminators.
Edited by Peter Murray, OhioLINK. This document represents a summary of comments on the Sakai Developers mailing list on April 26-28, 2006 to a question posted by this document’s editor regarding possible integration points between Fedora and Sakai. The resulting threads were:
Student applications for the Google Summer of Code program are being accepted starting on May 1st. In preparation for that date, OhioLINK has finished up its list of ideas and other supporting documentation. We welcome student applications seeking to further the development of information technology in academic libraries in Ohio and around the world. Questions about the program? Take a look at Google’s . Questions about the suggested projects or about OhioLINK? Contact Peter Murray.
This is the list of project ideas so far. Please take a look at thefor updates.
Selecting an open source license was really much harder than I thought it would be. The OhioLINK executive director and I talked for about 90 minutes over the course of yesterday afternoon to reach a conclusion. The factors driving our decision where:
- A license that promoted the “open source” availability of our code
- A license that sought to ensure balance between our desire as an “upstream” provider of the source code to add enhancements to the base source code with the desire of any potential commercial entity to “add value” by providing a level of support for the DRC application that we cannot provide
Google is sponsoring the Summer of Code, a program designed to introduce students to the world of Open Source Software Development. OhioLINK is pleased to participate again as a , furthering the development of information technology in academic libraries in Ohio and around the world. We have describing OhioLINK’s participation and projects; take a look, augment or add your own (feel free to read the project documentation through the ‘Wiki’ link above and suggest other ideas), and . Questions about the program? Take a look at Google’s . Questions about the suggested projects or about OhioLINK? Contact Peter Murray.
In previous post I described to how easy it would be for Fedora to be integrated into Sakai and offered as reference the Entity.java interface as evidence. Well, it isn’t quite that easy. Two big clues:
- It is in the “legacy” part of the source code tree; and
- The interface has only getters (no setters).
Pretty damning evidence.
I still haven’t figured it all out yet, but there is this commentary in a document from last month with the title ““:
“The Sakai Project is a community source software development effort to design, build and deploy a new Collaboration and Learning Environment (CLE) for higher education. … The Sakai Project’s primary goal is to deliver the Sakai application framework and associated CMS tools and components that are designed to work together. These components are for course management, and, as an augmentation of the original CMS model, they also support research collaboration. The software is being designed to be competitive with the best CMSs available.”1