In the pre-meeting symposium, participants will contribute to the national dialogue about the need for high quality measurement of student learning through multiple expert assessments of the quality of student work rather than standardized testing. They will explore in depth the potential of e-portfolios as well as the barriers to their widespread adoption.
This symposium grows out of the work of AAC&U’s VALUE Project (Valid Assessment of Learning in Undergraduate Education). VALUE provides national leadership for new ways of thinking about assessment.
An overview of different portfolio technologies in use today and guidance on the pros and cons of different approaches. Think through how to match your portfolio goals with available technologies.
Explore the varied uses of portfolios (from institutional assessment to achieving learning goals to personal presentations), recieve a tour of several OSP implementations, and gain a detailed overview of the functionality of each component of OSP. The session will begin with an overview of the goals and motivations universities have for using portfolios, and include examples of different types of portfolios implemented at various institutions.
Does your institution need to do program assessment? Are you looking for better information than you can get from surveys and final grades? Attend this session for a step by step guide to do program assessment with portfolios (a process used at Portland State University for over 12 years.)
With co-presenter, Wende Morgaine.
I admit I've been lurking in a very slackernly manner in all the discussions in the Sakai community about content authoring, 3akai, UX, K2, Sakai NG and other unpronounceables, so I'm sorry if all this is a day late and a dollar short. Feel free to ignore me if you're part of Sakai and are way too far gone for any more input. After all, these are just thought experiments ;) If you're not part of Sakai, you might learn something about Drupal at least, so it may well be worth your time.
I draw some lessons here from Twitter and Drupal not to suggest that Sakai duplicate them, but rather that we hold those models in mind as we move Sakai forward. Even without these experiments, some of these ideas may be in our thinking about Sakai, so if they are familiar, take it as a vote of confidence. But if not, I'd like us to have at least thought through why we would not take them as inspiration or why we would choose another path.
In the lessons I draw from Twitter and Drupal below, I may come off as a bit of a zealot. Frankly, I have a greater appreciation for Twitter and Drupal as tools that I have for Sakai as a tool—my greatest appreciation for Sakai has always been for its community. But I would like to appreciate Sakai-the-tool as much or more than Twitter and Drupal, and I think I could, given the directions I see Sakai heading now.
But why Twitter and Drupal? When I'm thinking about all this Sakai stuff, my first thought is to reach for existing models. And the models I reach for are the handy ones. Why? Because there must be some reason I keep certain tools handy. There are lots of good tools, but the ones that fit so comfortably in my hand are well-worn for a reason. I also know them well—keen edges and ugly nicks—and so can draw the best lessons from them.