Stanford is interested in discussing the design and technical requirements for adapting Samigo so that it can support high stakes. Indiana, Michigan and rSmart are interested in participating in this discussion as I expect are others.
Most universities deal with multiple systems of record for identities - HR, student systems, alumni systems, etc. Many campuses have developed home-grown identity match tools to reconcile the same identity from more than one system of record. Higher Education has yet to produce a generic, community source identity match engine that can be used at multiple institutions. Such a generic ID match engine is one goal of the CIFER project, and UC Berkeley has made considerable investment in this goal. This presentation will describe the ID Match engine, the CIFER ID Match API, integration between the ID Match Engine and Open Registry, and administrative interfaces for resolving fuzzy matches. The goal is to submit this project as an Apereo incubation project during calendar year 2013, and hopefully recruit additional campuses to support the migration of this ID Match engine to a community project.
Many schools adopt Sakai because, as an open-source platform, each campus can meet local needs by making changes to the source code. Yet when is it sensible and sustainable to make local customizations? How do you weigh and prioritize the feedback and requests of a diverse population of faculty and students? And once you've committed to making changes, how do you establish an effective and repeatable process for implementing, testing, and evaluating efficacy?
With such a vibrant development community, we don't always have to reinvent the wheel. How can we discover and leverage customizations made by other schools in a sometimes chaotic, open-source community? And how best to manage campus expectations regarding new development, when just because we can make local changes doesn't always mean we should?
Integrating third party site information into your Sakai CLE course should be seamless and free from pain. This session will highlight some best practices as well as potential trouble spots with highlights from our experiences integrating with Kaltura, ScormCloud and other third party sites or services.
The last several quarters have brought us game-changing new innovations for bringing content from your SIS and LMS into uPortal. Many of these focus on the Courses portlet, but the Calendar, Map, and Notification portlets also play an important role.
We will look at the cool new advances that are available now, and some that are under development. We will hear about or directly from several schools working with these technologies and the methods they've found to be effective in this area.
The University of Michigan and UCT have both deployed Sakai 2.9 into production soon after it was released. During testing before, during and after deployment, numerous performance problems were discovered and resolved. This includes such things as:
This BOF is aimed at a technical audience to share the diagnostic and testing strategies and the lessons learned from 2.9 deployments at ours and other institutions.
Did you know Sakai has a robust course Evaluation System? Join peers to discuss and coordinate the latest and greatest developments with this useful tool. Find out what's coming in EvalSys 1.5 and help troubleshoot common bugs and known issues.
> University of Wisconsin - Madison has developed a suite of portlets that display a dashboard into the university's HR system. Employees can view pay stubs, tax statements, benefits enrollment information, time recording, and their contact information. Managers can view pending employee time management tasks such as approving absence, payable time and leave requests. The portlets have existing integration implementations with PeopleSoft HR and Cypress, a document management solution, but are pluggable to be usable with any backend data source.
by Benjamin Oshrin and Chris Hyzer
When needs for exchanging identity data across applications cannot be met using simple standards like LDAP, custom integration work is generally required. Operations such as creating identity records, provisioning identity data, and managing group data are common across institutions, yet are implemented using custom code.
This session will introduce the REST-oriented CIFER APIs, designed to provide a common mechanism for these sorts of integrations. A status report will be provided on the active development of the Core Schema, SOR-Registry API, ID Match API, Registry Extraction API, and Group API.
by Hui Jin and Bryan Holladay
Columbia University is working on enhancements to the syllabus tools to make it more robust and user friendly. The enhancements are being done by Longsight and are slated for completion in April 2013. Columbia plans to pilot the enhanced tool in summer before a full role out in Fall 13 term.
The enhanced Syllabus tool will have the capability of attaching date and time stamp to items to allow it to be linked to the calender. In addition, instructors will be able to create multiple items with or without date all at once. The tool will also have bulk update feature to allow updates to all titles, link to calendar, conversion of draft to post and delete. A table of content view is also being developed for easier read for both instructors and students.
2nd–7th June 2013