Institutional PLE

23
Towards an Institutional PLE David Millard University of Southampton, UK Oth er Team Members: Hugh C. Davis, Yvonne Howard, Patrick McSweeney, Chris Yorke, Heidi Solheim, Debra Morris

description

 

Transcript of Institutional PLE

Page 1: Institutional PLE

Towards an Institutional PLEDavid MillardUniversity of Southampton, UK

Other Team Members:

Hugh C. Davis,

Yvonne Howard,

Patrick McSweeney,

Chris Yorke,

Heidi Solheim,

Debra Morris

Page 2: Institutional PLE

Whatever Happened to those Digital Natives?

Page 3: Institutional PLE

Whatever Happened to those Digital Natives?

Digital Literacy

Reproduction

Information

Branching/Hypermedia

Photo/Visual

Socio-Emotional

Page 4: Institutional PLE

Whatever Happened to those Digital Natives?

?

Page 5: Institutional PLE

“We define an Institutional PLE as an environment

that provides a personalised interface to University

data and services and at the same time exposes that

data and services to a student’s personal tools…

We have emphasized co-design with students and

staff, and ambitious enterprise-level integration.”

Page 6: Institutional PLE

Data Integration and Deep Linking

EdShare Blackboard BannerRoom

Booking CRM Timetabling

Page 7: Institutional PLE

Data Integration and Deep Linking

EdShare Blackboard BannerRoom

Booking CRM Timetabling

MS Sharepoint

Page 8: Institutional PLE

Data Integration and Deep Linking

EdShare Blackboard BannerRoom

Booking CRM Timetabling

SLE Portal

MS Sharepoint

Page 9: Institutional PLE

Data Integration and Deep Linking

Open Data

EdShare Blackboard BannerRoom

Booking CRM Timetabling

SLE Portal

MS Sharepoint

Page 10: Institutional PLE

Open Data

http://data.southampton.ac.uk/

Page 11: Institutional PLE

Co-design

Page 12: Institutional PLE

SLE Principles

1) Be location independent and platform agnostic2) Enable a single point of access3) Support the lifelong academic journey

4) Do fewer things better5) Provide the shortest path to key services6) Support flexible use

7) Give users control of their own data 8) Be personalizable but always have sensible defaults 9) Be open and inclusive by default

Page 13: Institutional PLE
Page 14: Institutional PLE
Page 15: Institutional PLE
Page 16: Institutional PLE

Groups as Primary Interface

App Store Functionality

Page 17: Institutional PLE

Our Experience

Page 18: Institutional PLE

Conclusions

Page 19: Institutional PLE

ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexity

Page 20: Institutional PLE

ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexity

Focused on Data Integration and Deep Linking

Page 21: Institutional PLE

ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexity

Focused on Data Integration and Deep Linking

Co-design and Agile Development with incremental build and delivery

Page 22: Institutional PLE

ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexity

Focused on Data Integration and Deep Linking

Co-design and Agile Development with incremental build and delivery

Groups as the Primary Interaction, and App Store Model

Page 23: Institutional PLE

ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexity

Focused on Data Integration and Deep Linking

Co-design and Agile Development with incremental build and delivery

Groups as the Primary Interaction, and App Store Model

Thank You! (David Millard, [email protected])