Its CC-BY licensed so feel free to take sections and reuse them.

While this paper marks sort-of-the-end of the formal project, much more is happening in the world of FeedForward…

However, our initial choice, IESR, turned out to be problematic. Basically, while there was a goood set of machine APIs we could make use of, there just wasn’t enough usable content. While a lot of repositories had information in IESR, not many had their RSS registered, even where it was supported.

Our second choice came about through getting involved with the JISC Users & Innovation Programme: the tictocs project created a repository of table-of-contents feeds for academic journals. Tictocs collected loads of useful feeds, and worked with the publishers to improve their support. This was just the content we needed. Sadly, there was no API.

Eventually, I just gave in and built my own service – Jopml (Journals into OPML)!

Jopml is a Ruby on Rails application built using the data exported from TicTocs (as a .csv dump), but makes it easy to write a machine interface by building OPML output directly from the query. So http://jopml.org/feeds?q=polymers gets you the HTML search results, while http://jopml.org/feeds.opml?q=polymers gets you the same but in OPML, ready to import into a feedreader.

With this service in place I could add new functionality into FeedForward. First, you select the “Import journal feeds from Jopml.org” menu option:

Jopml menu option in FeedForward

Next, you enter some search terms and click “Search”. The dialog box updates to show the number of hits. When you’re happy, you click OK to add them to your application.

Jopml dialog box

(Note that as the service uses Ferret you can use booleans, phrases and all the usual Ferret query options)

And you’re done!

Feeds added

This functionality is currently in the source code in subversion, but should make it to the next release.

While I developed Jopml to add this feature to FeedForward, there is also nothing to stop anyone from making use of it for their own applications. If you make something interesting, let me know!

This map takes four modes into account:

1. Feel: split into seeing and hearing
2. Do: split into mouse and keyboard

See it here (click for full version):

One thing this does is develop a feel for the different modes of access.

Actually implementing these modes is very difficult in today’s applications as things like keyboard and text-to-speech are platform-specific. So seeing the full keyboard and speech experience will have to wait until M2 at the earliest.

(Note SWORD is on here – I’ve got that basically working now, but its not for Release 1 as I really need to sort out dependencies as they overlap with those for other Atom code I use.)