through RSS and APIs
Lisa J. Rogers, Research Associate
Institute for Computer Based Learning, Heriot-Watt University
• Two UKOER phase i projects
– Open Engineering Resources Pilot
• Additional OER Technical work with
– RSS Feed Deposit for OER
– Tracking OERs
– Aggregation of OERS
• Collated resources and existing
descriptions into central database and
• Batch uploaded resources and
descriptions to web 2.0 file sharing sites
using their APIs.
• Bulk upload resource descriptions and
links to Jorum Open using RSS.
Core-Materials Usage Stats
Number of Total number of views Number of
Resources subscribers /
YouTube 128 videos 17,417 20 subscribers
Flickr 860 images 25,940 7 contacts
Scribd 157 40,706 32 subscribers
documents (2,261 downloads)
SlideShare 157 35,240 3 followers
Viewing Statistics for CORE-Materials resources (Sept 2009 – March 2010)
Open Engineering Resources
• Dissemination to web 2.0 sites and Jorum
Open by individual partners.
• No central database.
• Cross search web 2.0 sites using APIs to
• Resources carefully tagged to allow this
Aggregation of OERs
• Provide and document demonstrators
• Google Custom Search
• Yahoo Pipes!
• Query through APIs
• Many APIs have official and unofficial
examples of code to help you get started
• In my experience technical support has
been helpful (if you are persistent)
– Reported bugs in Scribd API and in
SlideShare API which have been fixed
– Suggested new feature for SlideShare API
which has been implemented
• These approaches may not be scalable
– Limit on number of results returned
– How are results combined?
– Works for a finite number of sources
– Current approach relies on tagging (how to extend
• Viable solution for building smaller collections
– Open Engineering Resources Search
– Collections of OER (UKOER Phase 2?)
• Open Engineering Resources Search
• Returns results tagged ukoer, engscoer
• Can filter by partner (each partner
assigned unique tag (i.e.
• Rob Pearce continuing to develop this