Leap2A interoperation scenarios

Belongs to the 2009-03/Leap2A specification

=Portfolio Interoperability Prototyping Interoperation Scenarios= These are not to be confused with the practice scenarios - see Leap2A practice scenarios. They are the situations in which information would actually be transferred between systems. As can be readily seen, there is no clear limit or specification to the information involved, which is one reason why the Leap2A practice scenarios are so important in defining that.

Scenario I: Transfer of complete portfolio information
Here, the need is to transfer of as much info as possible and desired from one system to another, as the individual holding the portfolio moves from one setting, using one portfolio system, to another setting, using a different system; The motive is to avoid losing valued materials which are going to be reused later, and to avoid the necessity to re-enter information that has already been entered in another system (along with all the potential for inconsistency, as well as time wasted.)
 * a sub-case would be transferring information from an educational e-portfolio system to a employer-based system.

Scenario II: Transfer of specific information supporting transition
This is to do with transferring information to support various kinds of transition, and it is supposed that these kinds of transfer have much in common:
 * think of the multiple examples in different contexts of something like CV or application form, with covering letter or statement
 * UCAS (etc.) is the context for one particular case of this

Scenario III: Intra-institutional services
An institution has a MIS, VLE and separate portfolio system. Each system has defined areas in which it keeps the student's personal information. The student-owned information is mostly held in the portfolio system, but some information common to portfolio and administrative use is held principally in the MIS (or Student Records System) and transferred from there to the portfolio system as required. When one system is required to access or display portfolio-related or common information belonging to another system, it issues a request to that other system, and information is returned in the format of this specification.

(candidate) Scenario IV: Distributed content
Moved to discussion, as it seems worthy of discussion before including here.