The document discusses the development of the Feedforward project, emphasizing the complexity of personal information flows and the need for better service configuration. It highlights the convergence of various services and notes that while some user support is provided, additional assistance is required from external services. Technical details about the project’s architecture, tools used, and upcoming releases are also included.

1. FeedForward project MDR SIG 2008-02-12 Scott Wilson

2. http://www.flickr.com/photos/aussiegall/395227944/sizes/o/ Put up your antennae! “… I’m not explicitly seeking particular content here - I’m establishing finely-tuned-antennae to catch useful intelligence …” Paul Walk, on the topic of “discovery to delivery”

3. Personal information flows are really complicated and go in both directions. http://www.readwriteweb.com/archives/visualizing_social_media_fatigue.php

4. thankfully things are starting to converge in a way that makes things easier to process and manage

5. … though configuring all these services is still complicated and users need support. We do some of that in the application, but we also need some support from services, registries, etc. http://www.flickr.com/photos/dogbomb/526961087/

7. FeedForward architecture plan, early 2007 What’s changed? + SWORD + TiCToCs + OAI-ORE(?) OAI-PMH(?) XSPF + Intute?

8. A FeedForward view of information flow

9. Enough of that, show the demo!

10. More info, download etc : http://legolas.cetis .ac.uk We’ll get a proper domain name soon, we promise Next release due end April FeedForward is Written in Eclipse/SWT. Uses Rome, Rome Propono, some Nebula widgets, and some leftover bits of Plex, RELOAD etc. It makes very extensive use of the Eclipse async job API. Its all up on SVN with an MIT-style license. Give us feedback, requests, ideas on our trac site @ http://legolas.cetis.ac.uk/trac