Open Source Porfolio
We started our training of OSP today via interactive webinar from threecanoes.com.
Here are my notes. There were four other programmy people in the room who fundamentally understand a lot of what was covered. I belong in the category of instructional designer who gets the sense of what's going on and was able to follow along until we got into the "predicate" discussion portion (see bottom right).
Essentially, here's the scoop, as I understand it- Sakai (our learning management system, called Isaak here at Brock) has optional tool called Open Source Portfolio (OSP) which allows you to plug in Resources (primary place for files) and Assignments (primary place to accept files/text from students) into a larger assessment framework. The primary mode of assessment is through Matrices which allow you to set up via Forms a structure for the criteria at a course, program or university-wide level.
The forms are created by the developer using XML.
For those of you still with me, XML is a hierarchal, markup language that consists of artifact, meta-data, structured data, schema.
Sample forms exist in the tools that we can customize as per our needs. We are currently running a pilot with Psychology 4th year capstone class with Dr. Tanya Martini. Ideally, she will consult with us on desired inputs and the developers will modify the xslt templates to create a structure that works with her desired assessment.
Users will then interact with the matrices to complete the forms which will include instructions and the option to multiple select or answer via free text.
The primary means of showcasing the data is via the portfolio itself. Which if rendered properly should look just like a nice clean webpage that links to all the input the user has entered.
That's as much as I understand. I'm expecting Matt to now chime in with some of his notes and then we'll have a fuller picture. I may have to edit this as a result :)
Open Source Porfolio
We started our training of OSP today via interactive webinar from threecanoes.com.
Here are my notes. There were four other programmy people in the room who fundamentally understand a lot of what was covered. I belong in the category of instructional designer who gets the sense of what's going on and was able to follow along until we got into the "predicate" discussion portion (see bottom right).
Essentially, here's the scoop, as I understand it- Sakai (our learning management system, called Isaak here at Brock) has optional tool called Open Source Portfolio (OSP) which allows you to plug in Resources (primary place for files) and Assignments (primary place to accept files/text from students) into a larger assessment framework. The primary mode of assessment is through Matrices which allow you to set up via Forms a structure for the criteria at a course, program or university-wide level.
The forms are created by the developer using XML.
For those of you still with me, XML is a hierarchal, markup language that consists of artifact, meta-data, structured data, schema.
Sample forms exist in the tools that we can customize as per our needs. We are currently running a pilot with Psychology 4th year capstone class with Dr. Tanya Martini. Ideally, she will consult with us on desired inputs and the developers will modify the xslt templates to create a structure that works with her desired assessment.
Users will then interact with the matrices to complete the forms which will include instructions and the option to multiple select or answer via free text.
The primary means of showcasing the data is via the portfolio itself. Which if rendered properly should look just like a nice clean webpage that links to all the input the user has entered.
That's as much as I understand. I'm expecting Matt to now chime in with some of his notes and then we'll have a fuller picture. I may have to edit this as a result :)