LEAP2A type usage

Belongs to Portfolio interoperability prototyping > PIOP types

entry in PebblePad

 * Thought
 * Comment
 * Review
 * Note
 * CR Reflecting on Learning (for all types)
 * Webfolio Page
 * TR Thought/Reflection
 * TC Thought/Conclusion
 * TP Thought/Planning
 * MO+MW+MOT Meeting Outcome + Why + Target Date
 * APS Action Plan / Strengths
 * APW Action Plan / Weaknesses
 * APO Action Plan / Opportunities
 * APTh Action Plan / Threats
 * Proforma
 * Evidence fields (AbE, AcE and the Evidence field of Experience)

entry in ePET

 * Blog
 * Comments
 * Personal Statement
 * Skill description

ability in PebblePad

 * Ability

ability in ePET

 * Skills (divided between the definition here, and the description of personal skill, as an entry)
 * Learning Outcomes
 * Hobbies

achievement in PebblePad

 * Achievement

achievement in ePET

 * Qualifications (achieved)

activity in PebblePad

 * Experience
 * Activity
 * APSt + APH + APST Action Plan / Steps to success

activity in ePET

 * Work Experience
 * Action plan actions

meeting in PebblePad

 * Meeting

meeting in ePET

 * Meetings
 * Presentations (or may be represented as a sub-class?)

person in PebblePad

 * APRP | MRP people resources (if singly: as a list, comes under resources)
 * user information

person in ePET

 * Personal Details

plan in PebblePad

 * API (from Action Plan) (+ APT) represents actual goal
 * Action Plan (common fields): CD field contains "Current Situation"

plan in ePET

 * Action Plan
 * Action Plan, Objectives field forms actual goal

resource in PebblePad

 * File
 * APRB | MRB book resources
 * APRW | MRW web resources
 * APRP | MRP people resources (as a combined text field only: singly as person)
 * APRT | MRT training resources
 * APRM | MRM multimedia resources
 * APRO | MRO other resources

resource in ePET

 * Associated File

selection in PebblePad

 * Blog (information about feed, not individual entry)
 * Webfolio
 * CV

selection in ePET

 * CV