I’ve finally gotten around to creating a quick demo of one of the use cases I wrote for SPAWS – sharing a comment.
So, here are the steps in the use case:
- Browse a widget store
- Download a widget
- Submit a review of the widget in the widget store
- Search for the same widget on a different widget store
- The description page for the widget should contain the review submitted to the other widget store
Seems easy enough – lets go!
1. Browse a widget store
Here’s a widget I’m going to review in my local Edukapp:
2. Download a widget
Well, I don’t really need to do this, as I can play with a live preview on the site, but lets take it as read I’ve had a go with the widget, and have formed an opinion.
3. Submit a review of the widget in the widget store
So, I create an account and log into Edukapp, and submit a review; here it is:
4. Search for the same widget on a different widget store
On ITEC, lets find the Weather widget; luckily its pretty obvious on the “featured” page:
5. The description page for the widget should contain the review submitted to the other widget store
Yep, there it is!
Note that, because its an “external” review, ITEC hasn’t provided a link for the user who submitted it. SPAWS does send a URL with the “Agent” paradata that links to the user profile back on the original site, but its up to stores whether they want to use that, or to just style external reviews without any links.
Note also that you can set up a similar kind of demo using two different instances of Edukapp (just make sure in store.properties you give each one a different value for “spaws.submitter.name” or they won’t show up in the other store as it filters out any paradata it thinks it submitted itself).