There was a time when I was moving in both the worlds of the Sakai Collaborative Learning Environment and the Fedora Commons digital content repository. It seemed like a good idea to bring these two worlds together — Fedora as a content repository for Sakai learning objects. Back in 2006, I logged a ticket in Sakai’s tracker to see if anyone was interested. This morning I got notification that they are thinking of closing the ticket.
I’ve since moved away from both communities into other areas of interest, but felt one final duty of stewardship over this idea before it drifts out to sea. Perhaps integration between Sakai and Fedora Commons is already happening and this ticket is anachronistic. Perhaps this wasn’t such a good idea to begin with and it should die on the vine. Perhaps someone else will think this is a good idea and become the champion for it. At this point, though, my professional interests are elsewhere and I can’t carry this one forward.
Here is the text of the message:
| The following issue has been updated.|
| Updater: David Horwitz|
Date: 23-Feb-2010 06:32
MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice [http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines] Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly
|Components:|| Content service (Pre-K1/2.6), Resources|
|Affects Versions:|| 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1|
| Provide an alternative to the existing ContentHostingService interface that stores content in database tables, directories, and files with one that stores and retrieves content in a Fedora Digital Object Repository.|
(This post was updated on 03-Jan-2016.)