ePortfolios and the user experience

I was thinking the other day about the kinds of things, as a research student within a large institution, I might want from an ePortfolio and these are some of the things I came up with:

Tools

Blog tool: for reflective writing

Calendar: to track deadlines

Planner: to make ‘to do’ lists

Sticky Notes tool: for one-off notes

Cites Manager: to track bibliographic references

Folder tool: to store/organise/share docs

Wiki tool: for collaboration

Forum tool: for discussion

Media tool: to store/share/display visual media

Podcast tools: to store/share/play audio media

I would want something that works a bit like a real-world portfolio but with a little more flexibility… taking the benefits of the digital… enabling sharing and use of artefacts that, for whatever reason, just don’t fit into a ‘physical’ file structure. I’m also thinking that I’d like the software tool to be readable on a portable device like an iPod Touch.

Interestingly, many of the tools I want already exist in a Web 2.0 world and it would be feasible for me to cobble together an ePortfolio of all these things using existing free or open source software but that’s not an ideal solution… and that made me think of some other things around the user experience.

Tool features

As well as having the tools, you need to have the ability to save, store, backup, transfer and export your data, so there needs to be some way to collate all the data that is visible in your ePortfolio and compress it into a standalone file on a regular basis.  And then there are the other issues:

Issues around usability

The toolkit needs to be:

easy to use

well supported

portable

accessible

reliable

functional

integrated

networked

flexible

Then there are issues around the kinds of interaction that might be expected to go on with and through the ePortfolio:

Contexts

open/closed

specific/general

personal/social

formal/informal

audience/purpose

aims/objectives

ownership