Integrating Google Tools with Sakai Duffy Gillman Sr. Software Engineer The rSmart Group David Haines CTools Developer Digital Media Commons University

  • View
    212

  • Download
    0

Embed Size (px)

Text of Integrating Google Tools with Sakai Duffy Gillman Sr. Software Engineer The rSmart Group David...

  • Integrating Google Tools with SakaiDuffy Gillman Sr. Software EngineerThe rSmart Group

    David Haines CTools DeveloperDigital Media CommonsUniversity of Michigan

  • CONTEXTAnd Now Heres Some...12th Sakai Conference Los Angeles, California June 14-16

  • Google Offerings... are Vast... ...we are covering a small patch of ground today.

    CLE Integration - OAE had its own efforts

    Augmentation of - One could build a Google LMS CLE interesting... but not our focus12th Sakai Conference Los Angeles, California June 14-16

  • Why Are We Thinking About This?Infrastructure - Google is likely to be a university email and calendar provider.Extension - Google provides tools we cant afford to make.Innovation - Google allows simple creation of web tools through App Engine.Compatibility - Lots of work is done in Google by faculty and students. How can those artifacts be available in Sakai?12th Sakai Conference Los Angeles, California June 14-16

  • What Does Google Have to Offer?12th Sakai Conference Los Angeles, California June 14-16?

  • What Does Google Have to Offer?12th Sakai Conference Los Angeles, California June 14-16?searchdocumenteditingstoragevideoemailsocialnetworkingbloggingchatforumssite hosting/editing...to name a few thingsSSOgroupingfederation

  • Why Might We Want These Functions From Google?Offloading Maintenance/SupportCloud/ScalabilityWell-developed UI (mostly)Google Market Share/CachetStudent/Faculty UseGrowth of Apps for EducationBang for the BuckCommon integration across tools (?)Collaboration outside of institution12th Sakai Conference Los Angeles, California June 14-16

  • HISTORYAnd Now Heres Some...12th Sakai Conference Los Angeles, California June 14-16

  • 2008 Call to Community12th Sakai Conference Los Angeles, California June 14-16https://confluence.sakaiproject.org/display/SAKDEV/Google+Integration

  • Community InterestResponses from 18 individuals (17 institutions) Non-scientifically produced summary of interest:12th Sakai Conference Los Angeles, California June 14-16Link to Google DocEdit Google DocEmbed Google GadgetIntegrate gTalkReplace CalendarIntegrate Calendar feedYouTube Lecture VideosOffline SakaiSakai Sites -> Google GroupsSakai within Google SitesSingle Sign-On (SSO)Source:https://confluence.sakaiproject.org/display/SAKDEV/Google+Integration

  • What Has Sakai Community Done?Sakai Maps (Edia)Google Docs (rSmart)reCAPTCHA (?)Gradebook2 (GWT)BLTI for Google App Engine (Dr. Chuck)iGoogle Widget for CamTools (Cambridge)12th Sakai Conference Los Angeles, California June 14-16

  • THOUGHTS ON INTEGRATIONAnd Now for Some...12th Sakai Conference Los Angeles, California June 14-16

  • Why Does Google Matter (here)?Offers free / cheap useful tools -Search, Email, Calendar, Docs, Chat

    Offers new tools -spreadsheet,maps, video

    Offers infrastructure -Domain customized Google Apps

    Offers innovation -App Engine for your tools, new tools from Google

    Already in use by students and faculty12th Sakai Conference Los Angeles, California June 14-16

  • Different Reasons for IntegrationReplacement - Use Google calendar and emailSupplement - Make Google tools seem like Sakai tools (spread sheet, maps....) Make Google documents appear to be Sakai documentsExtension - Make it easy to write Google apps that appear to be Sakai tools.Expose - Sakai widgets in iGoogle

    These are complementary.12th Sakai Conference Los Angeles, California June 14-16

  • Easy Integration TargetsPublish Google document in Sakai (rSmart - demo later)

    Import Google calendar feed

    BLTI loose integration with Google App engine apps

    CambridgeiGoogle gadgets12th Sakai Conference Los Angeles, California June 14-16

  • Plausible Integration TargetsBased on rSmart approach should be able to make Google artifacts visible as if they were Sakai artifacts with Sakai viewing permissions.

    E.g. spreadsheets, maps, youtube video

    Limitations:- Integrating presentation not creation. Creation and editing permissions are all Google.- Versioning: How assure that document doesn't change before grading?12th Sakai Conference Los Angeles, California June 14-16

  • Uncertain Integration TargetsCalendar, email archive, resources, chat

    Replacing infrastructure brings up thorny issues:

    Permission model -> Google != SakaiGroups -> Google != Sakai

    12th Sakai Conference Los Angeles, California June 14-16

  • Considerations and TradeoffsAuthz Issues - mapping Sakai / Google concepts and keeping information in synch

    SSO - Coordinate local and Google login

    Grading - control of Google artifacts

    Control / Legal - Enforcement of Institutional policies

    Flexibility - Dependent on Google implementation and policies12th Sakai Conference Los Angeles, California June 14-16

  • DISCUSSION of the FUtureAnd Now Heres A...12th Sakai Conference Los Angeles, California June 14-16

  • What to Expect from GoogleAppears to be "concrete interest" but we can not (at this point) rely on Google to solve any of these issuesGoogle Docs API 3Revision History potential requirement for gradable submissions12th Sakai Conference Los Angeles, California June 14-16

  • Potential Projects (a few...)Publish document artifacts for grading

    Smooth offloading of creation / editing to Google tools

    OAuth / OpenID compatibility (not just for Google)

    Calendar integration / replacement

    Email archive replacement

    Chat replacement

    Task list as Sakai tool (as an experiment)12th Sakai Conference Los Angeles, California June 14-16

  • INTERMISSIONAnd Now for An...12th Sakai Conference Los Angeles, California June 14-16

  • Google Documents IntegrationAnd now heres a12th Sakai Conference Los Angeles, California June 14-16

  • What Should it Do?12th Sakai Conference Los Angeles, California June 14-16

  • Low Hanging Fruit

    Provide Access to Google Documentsin Resources Tool

    Not EVERYTHING... but a good start12th Sakai Conference Los Angeles, California June 14-16

  • Benefits

    Lets Google do its thing

    12th Sakai Conference Los Angeles, California June 14-16Crazy,Wacky,Web 2.0^Just share the documents

  • Why not Google in an iframe?12th Sakai Conference Los Angeles, California June 14-16Google

  • Problem: Wrapping SakaiNavigation...

    (kind of minor)12th Sakai Conference Los Angeles, California June 14-16

  • Problem: Wrapping GoogleDoes Google Know Your Users?12th Sakai Conference Los Angeles, California June 14-16In Sakai I may be:

    duffy@myuniversity.eduDo I even exist in Google?Who Am I There?huggybear_54@gmail.com ?duffy@gmail.com ?

  • Problem: Wrapping Google12th Sakai Conference Los Angeles, California June 14-16If Google appears in a Sakai iframe,you still need to log in... (somehow)

  • Problem: Wrapping GoogleSolution is probably Google Apps for Education, and fancy synchronization work12th Sakai Conference Los Angeles, California June 14-16Ill get to that later...

  • Without Further Ado...What does it do?12th Sakai Conference Los Angeles, California June 14-16

  • FunctionsAuthor Browses Google Docs AssetsDocument Selected for LinkFormat ChosenMetadata SetUsers in Site May Download via LinkAuthor may DeleteClicking Edit Forwards to Google (where one must log in)12th Sakai Conference Los Angeles, California June 14-16

  • WHATS IT MADE OFAnd Now..12th Sakai Conference Los Angeles, California June 14-16

  • Google Docs Integration CodeContributed:https://source.sakaiproject.org/contrib/rsmart/google-contentComponents:Google Doc ContentResource EntityGoogleDocsServiceOAuthServiceGoogle Docs Link Helper12th Sakai Conference Los Angeles, California June 14-16

  • Dependenciesrsmart-common-tool-lib(utilities for UI)

    oauth(tool for managing oauth providers and tokens)12th Sakai Conference Los Angeles, California June 14-16

  • Google Java Client APIsJava library encapsulating calls to Google Web ServicesProvide API Calls for Numerous Google Tools12th Sakai Conference Los Angeles, California June 14-16

  • Google Java Client APIs12th Sakai Conference Los Angeles, California June 14-16

  • CONTEMPLATIONAnd Now A Bit Of...12th Sakai Conference Los Angeles, California June 14-16

  • But I Still Want Google in an Iframe!Big issue: synchronizing access controlSeems to place requirements on the institution - Google Apps for Education, at the very leastProbably also requires Single Sign On (SSO) w/ Google12th Sakai Conference Los Angeles, California June 14-16

  • Google Apps for EducationEstablishes a Google domain matching your institutions domain nameProvides Google accounts to all your users12th Sakai Conference Los Angeles, California June 14-16Red Flag: What about guest accounts? Federated access?

  • Single Sign-OnMay not be possible for institution (eg. LDAP authentication) - access rights shared, but multiple loginTwo methods:Adopt Google as institutional SSO providerDeploy a SAML-based authentication mechanism (both Shibboleth and CAS apply)12th Sakai Conference Los Angeles, California June 14-16

  • SynchronizationTo be researched; especially performanceSakai would probably push access rulesPotentially a Security Advisor in Sakai could reference Googles access rules12th Sakai Conference Los Angeles, California June 14-16

  • Whats Next?And Now?12th Sakai Conference Los Angeles, California June 14-16

  • Battle T