Institutional PLE

574 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
574
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Institutional PLE

  1. 1. Towards an Institutional PLE<br />David Millard<br />University of Southampton, UK<br />Other Team Members:<br />Hugh C. Davis, <br />Yvonne Howard, <br />Patrick McSweeney, <br />Chris Yorke, <br />Heidi Solheim, <br />Debra Morris<br />
  2. 2. Whatever Happened to those Digital Natives?<br />
  3. 3. Whatever Happened to those Digital Natives?<br />Reproduction<br />Photo/Visual<br />Digital Literacy<br />Branching/<br />Hypermedia<br />Socio-Emotional<br />Information<br />
  4. 4. Whatever Happened to those Digital Natives?<br />?<br />
  5. 5. “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…<br />We have emphasized co-design with students and staff, and ambitious enterprise-level integration.”<br />
  6. 6. Data Integration and Deep Linking<br />Room Booking<br />Timetabling<br />CRM<br />EdShare<br />Banner<br />Blackboard<br />
  7. 7. Data Integration and Deep Linking<br />Room Booking<br />Timetabling<br />CRM<br />EdShare<br />Banner<br />Blackboard<br />MS Sharepoint<br />
  8. 8. Data Integration and Deep Linking<br />SLE Portal<br />Room Booking<br />Timetabling<br />CRM<br />EdShare<br />Banner<br />Blackboard<br />MS Sharepoint<br />
  9. 9. Data Integration and Deep Linking<br />SLE Portal<br />Room Booking<br />Timetabling<br />CRM<br />EdShare<br />Banner<br />Blackboard<br />MS Sharepoint<br />Open Data<br />
  10. 10. Open Data<br />http://data.southampton.ac.uk/<br />
  11. 11. Co-design<br />
  12. 12. SLE Principles<br />1) Be location independent and platform agnostic<br />2) Enable a single point of access<br />3) Support the lifelong academic journey <br />4) Do fewer things better<br />5) Provide the shortest path to key services<br />6) Support flexible use<br />7) Give users control of their own data <br />8) Be personalizable but always have sensible defaults <br />9) Be open and inclusive by default<br />
  13. 13.
  14. 14.
  15. 15.
  16. 16. Groups as Primary Interface<br />App Store Functionality<br />
  17. 17. Our Experience<br />
  18. 18. Conclusions<br />
  19. 19. Conclusions<br />iPLE deals with a mixture of students and staff, who have PLEs of varying complexity<br />
  20. 20. Conclusions<br />iPLE deals with a mixture of students and staff, who have PLEs of varying complexity<br />Focused on Data Integration and Deep Linking<br />
  21. 21. Conclusions<br />iPLE deals with a mixture of students and staff, who have PLEs of varying complexity<br />Focused on Data Integration and Deep Linking<br />Co-design and Agile <br />Development with incremental build and delivery<br />
  22. 22. Conclusions<br />iPLE deals with a mixture of students and staff, who have PLEs of varying complexity<br />Focused on Data Integration and Deep Linking<br />Co-design and Agile <br />Development with incremental build and delivery<br />Groups as the Primary <br />Interaction, and App Store Model<br />
  23. 23. Conclusions<br />iPLE deals with a mixture of students and staff, who have PLEs of varying complexity<br />Focused on Data Integration and Deep Linking<br />Co-design and Agile <br />Development with incremental build and delivery<br />Groups as the Primary <br />Interaction, and App Store Model<br />Thank You! (David Millard, dem@ecs.soton.ac.uk)<br />

×