Even as I am neck deep in a podcasting and iTunes U implementation here at PSU, I am gearing up for the next BIG project for us. That project is figuring out how to create a platform can support all sorts of web-based content production — I had written a post about when is a blog not a blog that seemed to get quite a few people thinking and talking here at my campus and beyond. The big thing that we have started to really explore and explain is that the tools that support this whole blogging thing really have the power to support a lot of what is going on on our campuses. Let’s see, ePortfolios? Yep. Blogs? Obviously. Personal note taking? Sure. What else? Well, anything that relies on faculty, staff, or students creating and publishing content.
Just yesterday I was lucky enough to be in a meeting with an amazingly open-minded faculty member who was asking for a blog platform to support his writing course. No problem … but, the big thing here is that we were joined by the people who actually support enterprise applications on my campus — you know the smart guys who think in terms of 100 thousands users and routinely deliver. They were there and it made me think bigger about what we can do to offer a single solution to a single faculty member with a tiny class (25 students) that would teach us about how we could scale to say 5,000 faculty and 80,000 students.
If you look back at some of the requirements we were looking at a few months ago the last time the blog team got together, not much has changed. It still needs to stand up to the pounding that an application like this will get on a big campus — but now we are thinking a whole lot about building a platform that enables all the things we need. We are going to try and build some sort of personal content management solution that can support blogging, portfolios, personal web pages, resumes, syllabi, you name it. Call it what you will, but in my mind we are attacking a paradigm shift here — I am looking to tear down the WYSIWYG tool du-jour domination on our campus. What we want is a space that empowers people to think about content, information architecture, self expression, and self-reflextion instead of how do I do that with DreamWeaver, then SFTP it, and then … see what I am saying? It is time to move to the next level.
What I am planning to do is task several smaller, more focused groups to look at the needs behind ePortfolios, behind personal note taking spaces, behind personal website tools, and so on. We’ll then roll those requirements up to the larger PCM Platform team and start constructing a solution. We have a starting platform in mind that I think can really get us close “out of the box,” but we’ll see.
As we started to talk, it became clear that we can create a handful of custom apps that will glue our solutions together to create all sorts of novel solutions. If students are publishing into their personal webspaces, then we’ll have to find innovative ways of pulling content into other locations. Here’s an example … if a class is blogging, but they are doing it into their personal spaces, the faculty member will want to aggregate every student’s post into a single class blog that she can control and manipulate as if it were a multi-user blogging environment itself. That is where we build.
I know this is a rambling mess, but my thoughts are still coming together. As they develop, I will share more. Any thoughts for me so far?