170 likes | 420 Views
MSU e-portfolio project – status report. Jim Green Academic Computing and Network Services September 9, 2005. What it is:. e-portfolio system supported centrally by LC&T still just a proposal pending analysis resources needed spec solutions available project status is imminent
E N D
MSU e-portfolio project – status report Jim Green Academic Computing and Network Services September 9, 2005
What it is: • e-portfolio system supported centrally by LC&T • still just a proposal pending analysis • resources needed • spec • solutions available • project status is imminent • multi-year, multi-phase project • possible related or spin-off projects
Who’s working on it • ANGEL Advisory Group – Byron Brown, chair • Instructional Technology Operations Group – Brendan Guenther, Jim Green, co-chairs • Jim Green, ACNS – leading outreach and planning efforts • Mike Buchanon, ACNS – technical lead
Drivers: • availability of ANGEL e-portfolio module • buzz in the higher ed community – Educause/ELI, CIC, etc. • groundbreaking e-portfolio work in College of Education, other colleges/departments
What’s been done so far • outreach • ANGEL e-portfolio group • discussion forums • resources • specification draft • preliminary planning • preliminary sandbox setup
Who’s in the ANGEL e-portfolio group • faculty, administrators, support staff • some departments that are represented: • Graduate School • English • Education • Libraries • Enrollment Services • Asst. Provost for Undergraduate Education • Division of Science and Math Ed. • …
e-portfolio broadly defined • primary types: student, faculty, institutional • other types: staff, teaching, lifelong, … • related applications: • CMS (ANGEL, LON-CAPA) • institutional repository (dSpace, Fedora) • web publishing (AFS) • personal storage (AFS) • online transcript • online CV/resume • “deanware”
Example e-portfolio functions • personal repository • artifacts – file + metadata • user-defined access control • ability to grant access to non-affiliates • co-curricular – not linked to individual courses • assessment – rubric support • “certified” artifact – locked from editing • system-wide searching/indexing • reflective tools, e.g. blogs • integration with CMS, other enterprise systems
Example e-portfolio policy issues • storage – how much space, quotas, etc. • e-portfolio lifecycle • FERPA • intellectual property – who owns e-portfolio elements? • assessment -- validity • institutional and departmental requirements – voluntary vs. compulsory • how “official” are e-portfolios and related data?
The short list • ANGEL e-portfolio module • OSPI – Open Source Portfolio Initiative • LON-CAPA • ANGEL will be considered first
ANGEL e-port in a nutshell • “My Info” -- personal data • “Artifacts” – files or links + metadata • “certified” artifacts • “History” – resume-like • “Blog” • “Objectives” – assessment, req. or stds. • “Publications” – for sharing
Timeline • sandbox – pre-alpha-test research – Fall, 2005 • limited pilot -- alpha test – Spring, 2006 • production burn-in – beta test – Summer, 2006 • phase 1 production release – Fall, 2006
Sandbox definition • pre-alpha test research • ANGEL will be first • out-of-the box software • get a rough idea of software capabilities • not a production system, may change, go down, etc. • no support structure • materials will be destroyed at some point
Limited Pilot definition • alpha test • small number of testers • simulate production use but not production load • support structure – appropriate to test size • changes limited to maintenance window • still a test system
Volunteer • Sandbox volunteers being recruited • Agree to give us feedback • Understand issues (no support structure, non-production system) and agree to participate in spite of them • ANGEL e-portfolio group volunteers also being accepted • email request to jfgreen@msu.edu
General Resources • Educause Learning Initiative (formerly NLII), http://www.educause.edu/eli, see “E-Portfolios” under “Learning Technologies.” • IMS ePortfolio Specification, http://imsglobal.org/ep/
Further information • Jim Green, Coordinator, Academic Systems • Academic Computing and Network Svcs. • jfgreen@msu.edu • 432-7239