SPAWS: Its all started coming together…

Another progress update on my mini project, which is about sharing paradata (user comments, stats etc) from web app stores using a distributed network store (for more info, check out this post).

One of my big worries when I started out was that I’d get to the end of the project and there wouldn’t be any stores I could work with – luckily it seems that the ITEC web app store will be live by then, and I’ve already seen their development server showing user comments on widgets pulled from an Edukapp instance I’ve been running locally, which is great!

Hopefully once I get the SPAWS-as-a-service running somewhere we can play with the ROLE store too.

So, what have I added to SPAWS recently?

  • Added ability to sign paradata published by SPAWS using GPG
  • added sharing sets of statistics – views, likes, embeds, downloads – about web apps/widgets using this JSON recipe.
  • Added contextual information along with paradata – so the page where the review first appears, for example (this came up from our advisory group)

In Edukapp I’ve added more SPAWS support, including:

  • Automatically pull in external reviews and statistics on each widget detail page
  • Configurable caching of data pulled in from SPAWS – so you may only pull in the latest paradata once every 24 hours, for example.
  • Automatic publishing of new/updated user reviews to the LR using SPAWS

For the ROLE Widgetstore I’ve started work on a basic SPAWS-as-a-service web app so that they can experiment with it; the ROLE store is currently a PHP-based application so it can’t use the SPAWS library directly.

As a side effect of the project I’ve also had a couple of pull requests merged into LRJavaLib that make working with paradata easier – hopefully other developers will benefit from that.

On the to-do list:

  • Have Edukapp periodically publish its stats. I was wondering if its worth doing whenever it stores a new set of stats data in its cache, or just do it as a scheduled task every 24 hours.
  • Support ratings. I have to decide how to do this – either as a standalone recipe, or added to the stats recipe as average rating + number of ratings.
  • Support tagging paradata events
  • Figure out how to identify OpenSocial gadgets
  • Get the SPAWS web service up and hosted somewhere.
  • Look at sharing similar/related info, e.g. from the MoreLikeThis processor in Solr
  • Figure out whether its worth supporting CAM as well as ActivityStreams-style JSON paradata
  • Add some sort of whitelist/blacklist facility to SPAWS for determining which sources of external information you want to use (and also make it possible to exclude all the crappy test data I keep generating).
This entry was posted in apps, development, open education, widgets and tagged . Bookmark the permalink.

2 Responses to SPAWS: Its all started coming together…

  1. Pingback: What I’ve starred this month: July 28, 2012 JISC CETIS MASHe

  2. Pingback: Digital infrastructure for learning materials: update July 2012 : Digital Infrastructure Team

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s