iGoogle and widgets as a platform for integrating institutional and external services
Upcoming SlideShare
Loading in...5
×
 

iGoogle and widgets as a platform for integrating institutional and external services

on

  • 3,747 views

Workshop on Mash-Up Personal Learning Environments (MUPPLE’08)

Workshop on Mash-Up Personal Learning Environments (MUPPLE’08)

Statistics

Views

Total Views
3,747
Views on SlideShare
2,842
Embed Views
905

Actions

Likes
4
Downloads
40
Comments
0

17 Embeds 905

http://personallearningenvironments.wordpress.com 824
http://dagmaratple.blogspot.com 24
http://www.memeteka.net 12
http://translate.googleusercontent.com 8
http://feeds.feedburner.com 7
http://www.slideshare.net 7
http://dagmaratple.blogspot.se 6
http://wsl.cemed.ua.pt 4
http://www.newsblur.com 2
https://www.educ.umu.se 2
url_unknown 2
http://blogs.ua.pt 2
http://tommoyenple.blogspot.com 1
http://www.yatedo.com 1
http://prlog.ru 1
http://static.slideshare.net 1
http://www.365dailyjournal.com 1
More...

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

iGoogle and widgets as a platform for integrating institutional and external services iGoogle and widgets as a platform for integrating institutional and external services Presentation Transcript

  • iGoogle and gadgets as a platform for integrating institutional and external services Workshop on Mash-Up Personal Learning Environments (MUPPLE’08) Oskar Casquero Javier Portillo Jesús Romo Ramón Ovelar Manuel Benito
  • Index
    • Our vision of a PLE
    • Why do we focus on the institution?
    • Architecture of a PLE
    • Our prototype
    • Open issues
    • Conclusions
  • Our vision of a PLE
    • The environment every teacher and student uses everyday, at least within an institution.
      • A hub to route learning resources on a one2one or one2many basis.
    • Controlled by the final user but influenced by:
      • Other classmates (teachers or students)
      • Tutors
      • Institutions
  • Our vision of a PLE
    • A kit for every learner/teacher that provides:
    Search Create Distribute Contact
  • Our vision of a PLE
    • The artifact to encourage social networking.
    Network of PLEs  Network of people, resources… knowledge ! PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE PLE
  • Why do we focus on the institution?
    • An effective way to create a network of PLEs.
      • The institution is the link to lots of people and resources implied in the learning process.
  • Why do we focus on the institution?
      • Personal in PLE means that the user decides but other agents should advice and provide materials.
  • Architecture of the PLE
  • Architecture of the PLE
    • Kernel
  • Our prototype
    • Widgets
      • gadgets as the glue for the integration of services
    • Start page
      • iGoogle as the frame for the widgets
      • iGoogle within Google Apps
        • l ocally controlled environment (set of tools, group of users)
        • administrator can configure a default PLE for everybody
  • Our prototype
    • Cloud-computing
      • Google App Engine to extract and analyze the collective intelligence that emerges from the network of PLEs
    • Network of blogs
      • Elgg or Wordpress as a framework for creating the blogs that backup the data exchanged within a group of users who use the PLE
    • Authoring tool: eXe learning
  • Our prototype
    • Repositories for:
      • D ocuments  Google Docs + Sites (wiki)
      • Images  Flickr
      • Videos  Youtube
      • Bookmarks  Delicious
      • RLOs  own server
      • Posts  network of institutional blogs
    • Vertical search engines  Google CSEs
  • Our prototype
    • We use software from Google because
      • it masks many technical issues
      • i t offers a flexible infrastructure
    • Google Apps is a propietary platform, but other products can also be used
      • o pen nature of gadgets allow their placement in any container
  • Open issues
    • Widgets that connect institutional services
    • Development of collaborative widgets
    • Real integration (data flow) of services inside iGoogle, not just an interface integration
    • Manage different user groups within Google Apps (teachers, students, research groups…)
    • Get experience with the standards we need (SAML, OpenID, Oauth, OpenSocial, …)
    • Integration of eXe learning and iGoogle
  • iGoogle and gadgets as a platform for integrating institutional and external services [email_address]