The document discusses the development of an Institutional Personal Learning Environment (iPLE) at the University of Southampton. A team led by David Millard focused on co-designing the iPLE with students and staff. They emphasized integrating university data and services like room booking, timetabling, and learning management systems. The iPLE also links to open university data and uses groups as the primary interface with an app store model. The iPLE aims to support students and staff through their academic journey by providing personalized access to resources and services in a flexible manner.

1. Towards an Institutional PLEDavid MillardUniversity of Southampton, UKOther Team Members:Hugh C. Davis, Yvonne Howard, Patrick McSweeney, Chris Yorke, Heidi Solheim, Debra Morris

2. Whatever Happened to those Digital Natives?

3. Whatever Happened to those Digital Natives?ReproductionPhoto/VisualDigital LiteracyBranching/HypermediaSocio-EmotionalInformation

4. Whatever Happened to those Digital Natives??

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…We have emphasized co-design with students and staff, and ambitious enterprise-level integration.”

6. Data Integration and Deep LinkingRoom BookingTimetablingCRMEdShareBannerBlackboard

7. Data Integration and Deep LinkingRoom BookingTimetablingCRMEdShareBannerBlackboardMS Sharepoint

8. Data Integration and Deep LinkingSLE PortalRoom BookingTimetablingCRMEdShareBannerBlackboardMS Sharepoint

9. Data Integration and Deep LinkingSLE PortalRoom BookingTimetablingCRMEdShareBannerBlackboardMS SharepointOpen Data

10. Open Datahttp://data.southampton.ac.uk/

11. Co-design

12. SLE Principles1) 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 use7) Give users control of their own data 8) Be personalizable but always have sensible defaults 9) Be open and inclusive by default

16. Groups as Primary InterfaceApp Store Functionality

17. Our Experience

18. Conclusions

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

20. ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexityFocused on Data Integration and Deep Linking

21. ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexityFocused on Data Integration and Deep LinkingCo-design and Agile Development with incremental build and delivery

22. ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexityFocused on Data Integration and Deep LinkingCo-design and Agile Development with incremental build and deliveryGroups as the Primary Interaction, and App Store Model

23. ConclusionsiPLE deals with a mixture of students and staff, who have PLEs of varying complexityFocused on Data Integration and Deep LinkingCo-design and Agile Development with incremental build and deliveryGroups as the Primary Interaction, and App Store ModelThank You! (David Millard, dem@ecs.soton.ac.uk)