MSU e-portfolio beta
test project
Jim Green
Academic Computing and Network Services
June 20, 2006
What it is
 Hands-on testing and research to better
understand how e-portfolios can benefit
MSU
 Collaborative prototyping of MSU-specific
e-portfolio tools and templates
 Toward a production LC&T centrallysupported e-portfolio system targeted for
Fall, 2007.
Who’s doing it
 Under the auspices of ANGEL Advisory
Group
 Joint ACNS-VUDAT-Libraries-AIS
development team
 Jim Green, ACNS, project leader
Recent accomplishments
 OSP (Open Source Portfolio, http://osportfolio.org)
selected
 Testbed implementation up and running since late
April.
 Project team working on setup, configuration,
integration
 Recruit faculty and grad students to participate and
provide feedback
OSP
 Open source software

not mature
 Built on Sakai (open source CMS)
framework
 MSU will implement portfolio functions only

ANGEL will continue to be MSU’s centrallysupported CMS for the foreseeable future
basic e-portfolio
 Person-centric rather than course-centric

system will not include course enrollment data
 Will persist after the person leaves MSU
 User owns her/his portfolios and artifacts

there is debate on this
 User controls access to their portfolios
Requirements Overview
basic OSP
 My Workspace
 Resources tool

WebDAV
 CIGs = common interest groups



shared portfolio space
supports coordinator, reviewer, evaluator roles
long-lived – i.e., not courses

examples: undergrad, art majors
OSP portfolio functions
 Learning matrix

supports custom scaffolding
 Portfolio templates

also supports custom scaffolding
 Free form portfolio design
 Comments and reflection may be
implemented in any of the functions
OSP portfolio tools
 Forms – XML/XSLT
 Wizards -- XHTML
 Styles -- CSS
 Layouts -- XHTML
 Templates – XSL (XML stylesheet)
OSP config issues
 Tools
 User interface design choices
 ANGEL coordination
 CIGs


roles
who can create
 Guest users
Help
 Imagine how students will use the system

step-by-step actions
 Develop scenarios/use cases of system use
 Play in the sandbox

provide feedback on functionality and usability
 Participate in matrix, portfolio template design
prototyping
 Participate in beta testing
Timeline – current
projection
 sandbox, prototyping – Summer, 2006
 limited beta – Fall, 2006
 expanded beta and scale-up – Spring, 2006
 full production – Fall, 2007
Further information
 Jim Green, Coordinator, Academic Systems
 Academic Computing and Network Svcs.
 jfgreen@msu.edu
 432-7239
 PowerPoint and handout:
http://www.msu.edu/~jfgreen/presentations