|Title (Goal)||Explore and document the potential for VIVO to provide unique new functionality to Sufia and other Fedora-based Hydra tools by leveraging largely existent work and extending VIVO to communicate directly with Fedora 4, Sufia, and Blacklight|
|Primary Actor||As a repository system architect, I want to know what functionality I will be able to offer my stakeholders and end users by taking advantage of largely existing tools and interfaces.|
|Scope||This is a major feature having broad implications for Fedora, Hydra, and VIVO|
|Level||This is a high-level use case aimed at a technical audience|
|Story||As a repository system architect, I need to provide more flexible collection management and customizable collection experiences than the Fedora and Sufia tools provide out of the box, and am looking for a solution that does not require extensive code modification with every new repository|
Note this use case is based in part on a complementary Fedora use case entitled Reasonable curator's admin interface. Here is the story from that use case:
- W3C Linked Data Platform (LDP)
What exactly is Apache Camel? from Stack Overflow
(somewhat cryptically) "Apache Camel is messaging technology glue with routing. It joins together messaging start and end points allowing the transference of messages from different sources to different destinations. For example: JMS -> JSON, HTTP -> JMS or funneling FTP -> JMS, HTTP -> JMS, JSON -> JMS"
Enterprise Integration Patterns (EIP) are blueprints for how we could best design large component-based systems, where components can be running on the same process or in a different machine. They basically propose that we structure our system to be message oriented -- where components communicate with each others using messages as inputs and outputs and absolutely nothing else. They show us a complete set of patterns that we may choose from and implement in our different components that will together form the whole system.