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 ““:
This module provides support for treating the end-user-created data objects in Sakai, across all Sakai applications, as uniform “entities”, for other applications to process them without API dependencies on the specific “entity producing” application. An entity is an object with properties; property names come from a well know vocabulary; property values are either simple strings or references to other entities.
An Entity, and the service which produces them, the EntityProducer, can also declare that they have common characteristics, other than the ability to produce entities as objects with properties. These are:
- URL able – the entity has a URL and will respond with an access request
All may not be lost — there is mention in the document of a JDBC package:
This module adds support for direct and Hibernate access to back-end databases. Connection pooling. Hibernate stuff
Certainly much harder to interface with, but I’m also appreciating more how powerful and complex the Sakai system is. Perhaps Fedora integration would have to happen at the “module” level (whatever module would be dealing with digital objects — I haven’t found it yet).
p style=”padding:0;margin:0;font-style:italic;” class=”removed_link”>The text was modified to remove a link to http://collab.sakaiproject.org/access/content/group/1118328820812-113628/Proposals/sakai_framework_proposal_reorg.pdf.(This post was updated on 28-May-2014.)