The publication explores good practice in the use of e-portfolios as a support for learning. It is being launched in conjunction with an e-portfolios infoKit which covers the main drivers, purposes, processes, perspectives and issues around e-portfolio use.
For anyone interested in understanding what ePortfolios are, and what some of the different conceptual understandings of them might be, this is well worth a read. So to is the infoKit, which contains links to some great case studies, as well as links to related resources on Social Software and Effective Use of VLEs.
I recently attended a meeting in Wellington where the topic of ePortfolios was raised and where I was again reminded that before we can begin evaluating the usefulness or otherwise of ePortfolio Software it is important to understand just what we mean by an ePortfolio and how it is intended to be used. We had a presentation from Owen O’Neil (Manager of the Australian Flexible Learning Framework’s E-standards for Training Business Activity) titled: ‘what the e-Framework can do for you and interoperability standards for e-portfolios’ in which he introduced a Service Useage Model (SUM) for an ePortfolio that he has been a part of developing in the VET sector in Australia.
I really liked Owen’s SUM, it bore a lot of resemblance to the features of an ePortfolio described on page 7 of the JISC document (Understanding how ePortfolios Work), and focuses specifically on a three phase “collect-manage-present” model. As I listened it reminded me of the diagram I’d constructed as part of CORE’s ten trends for 2007 where ePortfolios were featured, so I thought I’d included it here for reference as it’s likely to become lost in the archives 🙂
Essentially, the model illustrates how artefacts need to be gathered from a variety of places where they have been created and possibly stored, then managed within a repository of some sort, and finally presented for different purposes. Important things here are that the portfolio process is (a) “owned” and managed by the individual, not by an institution or organisation, and (b) unencumbered by a lot of unnecessary extra features, most of which are present in a variety of other applications and environments.