I’ve been working to get JBoss Seam tied into Fedora, and along the way thought it would be wise to stop and document a core concept of this integration: the centrality of Fedora Disseminators in the the design of the Ohio Digital Resource Commons. Although there is nothing specific to JBoss Seam (a Java Enterprise Edition application framework) in these concepts, making an object “render itself” does make the Seam-based interface application easier to code and understand. A disseminator-centric architecture also allows us to put our code investment where it matters the most — in the repository framework — and exploit that investment in many places. So what does it mean to have a disseminator-centric architecture and have objects “render themselves”?
Also tagged asset actions, digital libraries, DRC, Fedora, java, seam
Video Tour of OPAC Discovery Layer Tools:
Fair Use Versus the NFL with YouTube Caught in the Middle:
George Mason University Sued by Thomson Reuters over Zotero:
XML Tower of Structural Metadata:
Updates on the EndNote/Zotero Lawsuit:
Clay Shirky on the Need for Better Information Filters: