950 likes | 1.1k Views
eText Integration Options. Updated on January 6, 2012 CMS. eCollege. Power School. Power School. PSN. PSN+. Integration with Pearson LMS Platforms. Integration Scenarios by Platform. Course-Aware vs. Non Course-Aware Integrations.
E N D
eText IntegrationOptions Updated on January 6, 2012CMS
eCollege Power School Power School PSN PSN+ Integration with Pearson LMS Platforms
Course-Aware vs. Non Course-Aware Integrations • Course-Aware: Allows instructors to share notes and highlights and a customized Table of Contents with students. • Non Course-Aware: With the exception of Disaggregated scenarios, users can create notes, highlights and bookmarks for themselves. • Disaggregated: No personalization features. Lacks notemaking, highlighting, bookmarking, and searching capabilities. No left nav ToC, glossary, index or custom baskets
Current Integration Scenarios • Course Aware • Scenario 1: Simple URL Linking/ Stand Alone • Scenario 2: Advanced Linking • Scenario 3: Integration API • Scenario 7 Trusted Platform/Non-SMS Integration API • Scenario 9: Course Aware eCollege Integration (TPI) • Scenario 11: LTI • Scenario 12: Course Aware Stand Alone (Limit of 2 Simultaneous Users Per User ID) • Scenario 14: iPad • Non Course-Aware • Scenario 4: Disaggregated (Contexual) • Scenario 5: Self-Study • Scenario 6: Disaggregated with Self-Study Personalization • Scenario 8: Stand Alone • Scenario 10: Non-Course Aware eCollege Integration (TPI) • Scenario 11: LTI • Scenario 14: iPad • Scenario 15: School iPad (RUMBA Authentication) • Scenario 16: School Portal (RUMBA Authentication)
Integration Scenario 1: Simple Linking Using a simple URL linking mechanism, the course creation and membership are managed by the eText platform. User Experience Flow: Used by, but not limited to: WPS, Course Compass, Pegasus
Integration Scenario 1: Simple Linking: Instructor 2nd & Subsequent times
Integration Scenario 1: Simple Linking: Student 2nd & Subsequent times
Integration Scenario 1: Direct Login Login directly to the eText through a login page. The course creation and membership are managed by eText User Experience Flow: Used as a direct method of accessing eText
Integration Scenario 1: Direct Login: Instructors 2nd and Subsequent times
Integration Scenario 1 Direct Login: Instructors 2nd and Subsequent times
Integration Scenario 1: Direct Login: Students 2nd & Subsequent times
Integration Scenario 1: Direct Login: Students 2nd & Subsequent times
Integration Scenario 2: Advanced Linking This approach will enable the eText platform to use the course information from the host LMS to automate course creation & membership using a static Course ID. Now Deprecated
Integration Scenario 3: Integration API This model incorporates a web services API to enable a more robust mechanism to communicate course information & course membership from the host LMS platform to the eText platform. Used by: Mastering, EPIC
Integration Scenario 4: Disaggregated (Contextual) This model applies when the desire is to limit users to a specific range of pages within the eText & not allow any personalization (notes, highlights, bookmarks). User Experience Flow: Used by, but not limited to: WPS, Course Compass, Pegasus
Integration Scenario 5: Self Study This scenario allows instructors & students to make private notes, highlights & bookmarks. User Experience Flow: Used by, but not limited to: XL, WPS, Course Compass
Integration Scenario 6: Disaggregated with Self Study Features This scenario limits users to a particular page range, but allows instructors & students to make private notes, highlights & bookmarks. User Experience Flow: Used by, but not limited to: XL, WPS, Course Compass
Integration Scenario 7: Non-SMS Integration API This model incorporates a web services API to enable a more robust mechanism to communicate course information & course membership from the host LMS platform to the eText platform. User Experience Flow: Used by: PSN+, PSN