Etherpad is/was a nice little online tool that allowed writers to collaborate in real time. Thus made it very good for groups of people working remotely to brainstorm ideas or collaborate on creating a document. It also made it a popular app in schools where small groups could work together on a writing task and the teacher could correct, cajole and support on the spot. Everybody's edits showed up as a different colour and it was extremely easy to use with very few barriers to entry. Unfortunately, as with so many of these online tools, there wasn't really a sustainable business model to keep it going and the whole gameplan was to sell to someone with deep pockets. That someone came alang this week in the shape of Google who not only bought the product, but the whole development team too. Some would say that Etherpad was a simpler and better rival to Google Wave and they were just using their overmighty position to buy up a small but innovative rival. The more charitable might suggest that Google recognised talent and a great idea when they saw it and rewarded the creators accordingly. All well and good, but what happened next caused a minor web furore. They announced the demise of Etherpad. The word spread around Twitter like wildfire, and the number of negative comments on the announcement increased rapidly. Nobody held out much hope as the designers were doing what they always set out to do, and make a decent return on their investment. Everybody was pleasantly surprised when a new announcement was made releasing the code for Etherpad as an open source offering. It's now down to the education community to take the code on and launch a new "Etherpad" on a server somewhere and make it even better.
Obviously there is general satisfaction that a popular web tool has appeared to have been saved (as long as someone has the time/effort/technical know-how), however, it does expose the greater question, namely, how can we rely open content created in the Cloud when it is at the whim of the owners as to what happens to the platform that it was created in? 2 weeks ago I carefully planned my lesson for Ofsted using Quikmaps, a really simple Google Maps mashup that allows very easy doodling on top of a Google map. All was well until 30 minutes before the lesson when Quikmaps disappeared. Luckily for me I could do a quick rehash and work with Umapper instead (which I would have used anyway, but for a problem with saving the maps - you need to create individual user logins, something that you don't need to do with Quikmaps) and it all turned out fine. It turns out that Quikmaps hadn't disappeared for good, they'd simply scheduled site maintenance for when nobody would be using their application - Thanksgiving!
These 2 cautionary tales reinforce the need to plan for every eventuality when committing data and mission critical applications to the Cloud. How secure is your data? Can you export it? What happens when the web application front end goes down?
So, what does all this have to do with Incerts? For a start, Incerts is, and has always been, a Cloud application. The obvious major benefit of this is the ability to access your data and work on your assessment system wherever you may be. However, it also exposes it to the vagaries of the web - when your web connection is down, so is your access to Incerts. Furthermore, your vital assessment data is in the hands of a third party. How does Incerts mitigate against these issues? Firstly, Incerts is subject to the Data Protection Act which places very stringent conditions on what Incerts does with your data. Secondly, Incerts recognises that having the service available all the time is critical to schools and therefore the company spends your annual hosting subscription on the best web servers money can buy, and replicates the service in different physical locations so that if one data centre went down, it would be replaced seamlessly by another one. Lastly, and perhaps most importantly, users can export their data at any time via School View and Class View. Taking a prudent view of data security would suggest that despite Incerts' fantastic reputation for keeping the service running for virtually 100% of the time, users should regularly export their data to spreadsheets - say, at the end of every half-term.
