EPMS (Electronic Portfolio Management System) main functionality and features

The objective in this section is to outline an agreed view of this.

This page is to do with functionality for individuals. The important related issue of organisational implications is dealt with there.

EPMS for the individual should allow:

• management of personal information
  • collecting items (e.g. posted, like blogs)
  • organisation of e-portfolio items
  • deletion, editing, possibly addition (usually through associated service)
• authorising or giving permission to others
  • tutors
  • employers
  • public agencies
  • colleagues
  • group members
• managing personal IPR
• viewing information that could be
  • distributed over a series of different information systems, some on secure servers
    • Diploma Supplements on a university server
    • employment records
  • heterogeneous
  • on personal computer(s)
  • on personal server(s)
• services and dialogue
  • collect feedback from others
  • reflect, share the reflections with others
  • share documents & evidence with others
• accessibility and usability as features

See the service-oriented architecture section for a way of implementing this functionality.

Questions:

• Is this a plausible and comprehensible (or more hopefully even optimal) approach to core e-p functionality?
• What differences are there between EPMS for the individual and for the organisation?