First up Scott Wilson (@scottbw) describing potential use of learning registry to bring together ‘paradata’ (activity/usage data) for ‘widgets’ (or apps) across different widget (app) stores – the idea that you could have the same app in different stores, and want to aggregate the reviews or ratings from each store. Put in bid to JISC under rapid innovation call for a project ‘SPAWS’…

Terry McAndrew (from JISC TechDis) – want to network experience with resources – identify accessible practice/purposes. Terry says most ‘OER Problems’ are social not technical. Asks – can we find learning registry output via Google?

Walt Grata showing tools that he has built on top of Learning Registry … (on github):

• ‘Landing pages’ for content – that can be indexed via Google (think this is new, and not up at github yet)
• Harvesting tool – to grab stuff from a node and put into another storage mechanism – e.g. couchdb,  postgresql, etc etc

Pat Lockley – slides

• Chrome plugin, code on github
• No-one will search outside Google – so take learning registry to Google. Chrome plugin finds all links on the page, and checks each one on the learning registry – and looks for some common attributes – like ‘title’ or ‘description’ etc. – and can then manipulate browser display to make use of this data.
• WordPress Widget  – code on github
• plugin for WordPress to display content from a learning registry (node) in a wordpress blog

Steven Cook – used Cake (PHP framework) to extract and ‘slice’ data from learning registry node. Also pulling data from other sources – like Topsy. Code on github. Talking about how can’t expect Learning Registry to do the hard work here – have to expect to pull out data, cache it, etc. Notes learning registry API isn’t completely RESTful (? not sure what the issues are) .