As many of you know I do some part-time consulting with the IMS Global Learning Consortium (www.imsglobal.org) in addition to my UM teaching and other stuff. One of the cool features of IMS is a weekly report that we just send around to each other. Given that we are pretty distributed, a weekly report helps folks know what is going on.
I decided that I would start putting an edited version of my weekly report up on my blog. It will help me remember what I have done when it comes time for my annual Faculty report. I redact the sensitive bits and particular vendor names.

I have caught up after my book and first two week of class. Here is my IMS work for the week
– I forwarded some SimpleLTI artifacts to Lisa for possible inclusion in the DN
– I started work on completing a formal IMS document connecting Common Cartridge to LTI (Real LTI – not Simple LTI) – This has gone well so far and I should have a good draft for Kevin to circulate in the CC group early next week.
I have done some related stuff in my teaching and UM role:
– We are adding LTI support to a new UM tool called “LectureTools” (http://www.lecturetools.org/) This is a free tool developed by a UM faculty member named Perry Samson that supports online and live lectures and student interaction – it is used around the world – we are adding IMS LTI to it to integrate it into Sakai at UM and potentially to other LMS’s as time passes. IMS LTI will automate nearly all of the configuration and setup and greatly improve the user experience for the students in particular in this application – as the roster provisioning will be completely implicit when the tool is used via LTI.
– I have an independent study class with 12 students – my goal is for them to all write IMS LTI compliant tools – One is developing a delicious like tool in Google AppEngine, another is writing a FireFox plugin to support IMS LTI, others are getting to know Ruby to write some tools in Ruby.
– I wrote a framework for supporting IMS LTI in a general Google AppEngine context. It makes it really easy to build an application. (www.cloudcollab.com)
– I wrote a new application for a course I am teaching – to runs crowd-guessing experiments online. The tool was built and deployed using IMS LTI on Google AppEngine using my new Python LTI framework – I wrote the program and had it in production and integrated into UM