University of Wisconsin - Madison is using Maven and Jenkins to manage build and deployment of uPortal and portlets across five different environments from one central UI. The WAR Overlay feature of the Maven WAR Plugin is used to inject environment specific configuration into uPortal and each portlet. Jenkins automatically builds and deploys portlets in the development and test environments when changes or new releases are detected reducing developer overhead and turnaround time. A key-pair based token encryption tool is used to securely store credentials a version control system allowing them only to be decrypted at build time on the target server.
Overview of Student Success Plan (SSP) technical application architecture - code layers, libraries/frameworks, APIs and other integration points. Intended for developers who might be interested in either working on SSP code directly or integrating SSP with institutional data feeds and applications.
Stuck getting started with Sakai CLE? Not sure where to look for help, tools, patches & recommendations? Learn the approaches that experienced developers and implementors use for building, configuring and deploying Sakai, managing customizations, registering bugs, finding patches and making recommendations to the community. Learn how to be a JIRA ninja and all about "indie" tools. Hidden tips and tricks to help you get the most of what's out there. Learn the things that experienced Sakaigers "just know" all in one session!
The Apereo Open Academic Environment is a platform that focusses on group collaboration between researchers, students and lecturers, and strongly embraces openness, creation, re-use, re-mixing and discovery of content, people and groups. A core principle is enabling actual end-users to drive innovation from the inside and contribute in a number of different ways.
During the summer of 2012, the number of stakeholders in the project shrank, and changes were made to the project?s anticipated usage and deployment model, as well as the initial project scope. In September 2012, the OAE team embarked on a re-architecture of the code base, targeting a much higher scale and a multi-tenant cloud-compatible deployment model, where a single installation can host multiple institutions at the same time.
This session will provide a summary of the revised goals and their motivation, as well as a brief architectural overview of the new system. A full demo of the new re-implemented functionalities will be done, and we will conclude with a discussion of timelines and priorities.
In addition to and separate from uPortal itself, Jasig also sponsors a comprehensive range of compelling, off-the-shelf portlet projects you can use to assemble an effective campus portal quickly. The twelve months since the last conference have brought us several major, exciting new developments int his space.
This session is a "Year in Review" for Apereo portlet projects, highlighting the most important updates in features, user experience, technology, and best practices. We will also discuss exciting new work under development now.
If you're thinking of implementing uPortal or uMobile, or if you already have uPortal and need to catch up with new developments in portlets, this session is for you. This is a high-level, highly-visual overview: uPortal and Java platform knowledge is not required.
The presentation will give an update on the current status of Dashboard tool, covering the following three areas:
1. The load test result and performance enhancement: Dashboard tool has been introduced in 2012 and received great interest within the Sakai Community. Columbia University has run the tool since spring 2012, but had to take the tool offline in Fall, due to serious database contention problem. Dashboard team has been working to address the performance problem. UMich has also run the dashboard load test in the cluster environment with the following settings: (1) Sakai 2.9 baseline; (2) Sakai 2.9 with Dashboard service thread turned on; (3) Sakai 2.9 with active Dashboard tool usage. We will compare and summarize the results for those three scenarios, and provide insights for future tool improvement and adoption.
2. Mobile Dashboard Project: Typical use cases of the Sakai Dashboard tool fits nicely into the mobile device paradigm. With this in mind, the University of Michigan is in the midst of refining the Dashboard's mobile interface. The project has sought continuous user feedback, starting with requirements for presentation, then in refining the interface. We will talk about the data used to guide the project and show some of the work in progress.
3. Longsight’s contribution to Dashboard tool: A quick overview of dashboard internal processing highlighting on recent inclusions relating to out of cluster background processing and aggregating older actions to the dashboard.
by Benjamin Oshrin
Virtual Organizations (VOs) consists of participants from multiple real organizations, such as universities. Collaborators come together for a period of time and a specific purpose, often (but not exclusively) to perform research, leveraging tools such as wikis, mailing lists, and calendars. VOs have identity management requirements varying from fairly simple to wildly complex, usually leveraging federated or social identity.
COmanage provides a tool for the identity management needs of VOs. This session will introduce COmanage and its capabilities, including how onboarding of new collaborators can be standardized and simplified, and how COmanage can be the core of a Collaboration Management Platform.
by Tom Cramer
Hydra is a repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. It is an ecosystem of components that lets institutions deploy robust and durable digital repositories (the body) supporting multiple "heads": fully-featured digital asset management applications and tailored workflows. Its principle platforms are the Fedora Commons repository software, Solr, Ruby on Rails and Blacklight. Come learn about this exciting new open source initiative and see how you and your organization can benefit and get involved.
University wide Learning Analytics projects need to be able to get, clean, merge and then analysis various data sources. This can be expensive in time, cross organizational boundaries and you will probably find inconsistencies in quality and coverage of the data you need to get a full picture. You may even miss part of the picture because of Bring Your Own Device (BYOD).
An emerging standard called the experience API has the potential to alleviate this problem. This API is a standard way of getting information from LMS's, web browsers, mobile apps etc and placing the activity streams into a Learning Record Store for future analysis. The data is clean, communication follows standards and you have the opportunity to keep track of tooling outside your organizational silo's.
This presentation is split into two parts. The first delivers an overview of the experience API and Learning Record Stores. The second drills into Sakai CLE specific details. Outlining a strategy for incorporation.
2nd–7th June 2013