1. What is an MLE? “Software tools and digital content that support learning” Comprised of many different modules, such as an SMS, LMS, eportfolio tool, blog, repositories for digital learning objects and many more Check out the MLE Reference Group to learn moreMLE Reference Group Or view the component parts

2. 5 of 8 Curriculum & Pedagogy National curriculum School curriculum inc. lesson plans Learning Management Systems (LMS) ePortfolios (record of learning) Course Management Systems Assessment tools Planning tools Communication Blogs Podcasts Chatrooms Noticeboards Social networking Discussion threads Audio conferencing Video/web conferencing Administration Student Management Systems (SMS) Student Record Transfer (SMS-SMS NCEA returns Calendaring Timetabling eReturns ENROL Resources TKI Websites Wikis Digital Learning Objects Library Management Systems Content Management Systems Authoring/publishing/editing tools Other content sources (open access ) Enabling Services IAM / SSO National Student Index Parental portal Transport mechanisms Metadata schema Interoperability standards Specifications Shared content

3. SMS ENROL Student record transfer e-asTTle PAT e-asTTle PAT Early notification eReturns Library system Metadata searching Web mail Digital content stores IdP Content Authoring Tools NSI SMS - directory integration eportfolio LMS Parent portal Online office suites National Standards Electronic attendance registers ENROL integration IAM Reusable and portable contentAssessment support Attendance support Authentication flows (existing) Data flows (existing) Data flows (proposed) Authentication flows (proposed) Or as a wiring diagram

4. Objective of the MLE activity To design and promote an –educationally relevant –open –modular –standards-based –sustainable approach to the development and use of MLE for (NZ) schools

5. Google docs Username: Password: LMS Username: Password: Hosted SMS Username: Password: Parent Portal Username: Password: Wiki Educator Username: Password: E-portfolio Username: Password: Library system Username: Password: The Problem

6. The solutions tried so far …and why we need something else 1.Synchronized passwords Some good examples Working very well for these schools But not easily transplanted 2.Centralized identity store E-asTTle (ESAA), ENROL (SIA) Provisioning and keeping up to date is too hard All teachers, students and parents would be majority of NZ population ESAA

7. What we have come up with The corner stones of our approach Non-centralized approach Full automation Actual single sign on Keep identity data at the source

8. Exciting stuff this will make possible Mash up pages – e.g. parts of LMS, ePortfolio and library system on one page Un-provisioned access for parents Generate credentials for all parents

9. Is it happening yet? YES over 40 schools already using it IDPs established in local loops (Christchurch, Wellington, Nelson) Commercial offerings from Watchdog, Edtech and Norcom Growing list of connected services (Pressure from users works better than pressure from MoE)

10. Testimony from a user You be the judge!

11. Are there any risks? YES - But none of them are new The technical side is the easy part Schools need good policies for managing identities and access Schools need to think about and manage risk Students need to learn what it means to have a digital identity

12. Questions