Portal/WP/Architecture

From Steeple

[edit] 1 Architecture

Steeple Portal is architected to consume data and maintain indexes of it but not to store any data or metadata directly. Steeple will maintain indexes of data and metadata in the search system. It will also maintain indexes of users. Steeple will store data related to users and the portal (e.g. preferences and personal playlists).

The system is designed to be pluggable and all major parts can be replaced or configured by implementing one of the plugin interfaces (e.g search, player, media source). The look and feel of the portal can be customized via CSS and SiteMesh to provide a unqiue institutional experience.

Media:Architecture.png

[edit] 2 Technical design goals

• The look and feed should be easily to customize and control
• The system needs to be easily extensible and should have a plugin like structure. e.g. The flash video player should be easy to replace with a minimal amount of code changes (and certainly in only once place)
• The system should produce data feeds which can be consumed RESTfully