e-Literate

Present is Prologue

Tag: JotSpot

  • Imagining a WeLE

    A while back, I noted with some interest Michael Korcuska’s screencast showing off a prototype of some functionality planned for Sakai 3. Some recent related conversation has come up on the Sakai listservs regarding the possibility of including wiki-like capabilities as core functionality of Sakai 3 and how this might overlap with and complement the capabilities in the screencast. I will argue here that, if combined carefully and enhanced with one more idea that has been floating around for Sakai 3, we end up with something quite new and interesting in the world of learning environments. I propose calling this new and interesting something a “Wiki’ed Learning Environment”, or WeLE.

    (more…)

  • Google Soon Adding JotSpot to Google Apps

    Thanks to fellow Oracle blogger Jake Kuramoto for pointing to this ZDNet piece revealing (among other things) that JotSpot is about to become part of the Google Apps package. Long-time e-Literate readers know that I was lucky enough to be able to interview JotSpot’s co-founders in the early history of this blog, and that they had a profound influence on my thinking about educational technology. (Some of the intellectual roots of the LMOS concept can be traced back to that interview.)

    To my mind, this is big news for educational technology. JotSpot is a fantastic platform for building long-tail educational tools. The fact that it is becoming a first-class citizen in the Google ecosphere opens up many great possibilities.

  • Towards an Education Inflected Architecture

    The title of this post was also the title of a talk by Barbara Taranto, the Director of the Digital Library Program at the New York Public Library at yesterday’s FIT conference. I just love it. An “education inflected architecture” is exactly what I crave. But beyond that, Barbara poses exactly the right challenge:

    For faculty and the organizational structures that support their work, it has been a bit of a rough ride –mastering new tools for collecting, analyzing and organizing information and at the same time accepting the responsibility of managing the outcome of all the collecting, analyzing and organizing activities that so persistently carry on. But for software developers, including some very prominent academic ones, it has been a free-for-all, an ideal market for real life R&D. Every week, or perhaps even every day, there is a new tool or a “better way” to do one’s job, a new piece of software to have and to learn and to use, a new widget, gadget, and for some, a new toy that needs no marketing other than to say it is a solution to a problem we didn’t know we had. And so for a very long time the focus of administrative activity has been on this shifting, volatile environment and how best to adapt to the “new student” and how best to create the “new university” in order to meet the needs of the “users”, generic-faced as they may be, even when the idea of the new university is not even well articulated by its greatest proponents.

    But amidst all the busyness, the balance and direction of the academe seems to have moved beneath our feet. The lauded best practices of instruction and research are often driven by software development and the overbearing individualist psychology of the consumer rather than by any higher purpose. We are encouraged qua instructors to describe our work –even our passion– as a “service” to others, and to proscribe future work as a functional unit –an economic widget; and qua researchers, to insist on further resources to meet our individual needs. In my mind, the model is dysmorphic and very possibly unsustainable–certainly undesireable. I suggest that for education practice to right itself, to flourish and evolve, and for students and academics to get back to the work of learning we need to shed the technology carapace and develop a new education inflected archtecture.”

    To sum up, we have to stop deciding what we’re trying to accomplish based on what our tools make easy (or hard) to do and start deciding what our tools need to look like in order to help us with what we’re trying to accomplish. That’s…well…a lot harder than it sounds. Because computers are essentially stupid, they force us to explicitly map out even the very basics of what we’re trying to do. It’s easy to make these maps incompletely or even inaccurately, in part because some of what we’re trying to articulate explicitly is inherently tacit knowledge.

    So what to do? I think we need to fundamentally change our software development practices. Agile development, a family of development techniques that seeks to tighten the feedback loop for developers so they don’t drift too far into theory land, certainly gets us part of the way there. My experience with software development teams creating applications for which they themselves are not the primary users is that they are best not left unsupervised for long periods of time. But I think we need more, too. Barbara is right: we need an education inflected architecture. Or, to put it another way, we need an architecture that can be inflected (or influenced, or evolved) by educators.

    In a recent fourpart interview, JotSpot CEO Joe Kraus gives us some hints as to what that might mean. (more…)

  • Is Sakai a Platform or a Product?

    Ben Brophy, a UI designer at MIT, muses about whether Sakai is a platform or a product. His initial answer is that it should be both. But he worries about the implications of having it as platform:

    The conference ended with a Q&A session with the Sakai board members. I asked how decisions about what’s included as the ‘core tools’ will be made. The response I got from one board member was “I’d like to see Sakai include six discussion boards. The user can try them all and decide which they like best.” No other board member disagreed.

    That’s been bugging me ever since. Even assuming that each school’s IT department will pick a default set of tools (a possibility mentioned by the board member), does it make sense to have Sakai include every tool built? Can there be no standards for inclusion? If I’m developing a new attendance-taking tool that I want to be able to post grades, what do I do if there are 6 gradebooks?

    This isa problem, for sure. But it’s not one that I’d be looking to the Sakai community to solve for me. (more…)

  • Bloglines: Still Sucky After All These Years

    Apparently, Bloglines CEO Mark Fletcher replied to June Oshiro’s blog regarding their broken feed reader. June hits the nail on the head with her reply:

    But Mark! You don’t address the second fundamental problem. I find this ironic and indicative of the whole issue – I complain that customer support is virtually non-existent, and you seem to pretend I never mentioned it. So let me ask you – do you believe that the issue of tech support not responding is fixed? Are you monitoring that situation as well? Mark, you are the leader of Bloglines – your employees take their cue FROM YOU about company priorities. If you don’t emphasize the importance of responding to customer concerns, who will?

    Here are some questions I’d like you to think about. Why doesn’t anyone from support read the discussion forum? Why isn’t there a bulletin board detailing known issues (and estimated time until they’re fixed)? Why did customer support ignore 4 out of 6 attempts to contact them? (I was polite. I even said “pretty please.”) Why couldn’t anyone tell me, over two weeks of emails, that there was nothing wrong with my feed, and that the problem was on the Bloglines end?

    The difference in attitude between Bloglines and a company like, say, Jotspot is night and day. Jotspot shows the kind of obsession with good customer service that a web services company needs to have while Bloglines…well…does not.

  • Group Processes (Including Learning Processes) Should Be Wiki'ed

    As many of you know, I am a fan of JotSpot. One of the interesting things that came out of my interview with JotSpot co-founders Joe Kraus and Graham Spencer is that they plan to build workflow syntax and functionality into their wiki product. Which brings me to Scott McMullan’s post…. (more…)

  • Interview with JotSpot Co-Founders

    Update: I have now posted a new (printable) version of the PDF with all DRM turned off. Note that it is located at a new URL.

    Here it is [PDF]!

    As you read the interview, I want to suggest that you think about the following words from Patterns of Software: Tales from the Software Community (which I quoted once before when discussing pattern languages and learning objects): (more…)