With emerging technologies such as jQuery, jQuery mobile, jQuery UI, SASS, Fluid, JSON and others. We would like to discuss best practices to incorporate all technologies throughout the uPortal framework and portlets without conflicts.
Discuss standards, proper aliasing, and development techniques that would help the uPortal community. The deliverable of this session should be updated documentation in the Jasig wiki.
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.
by Darren Kraker and Tom Cubanski
With an expanding landscape of devices and technologies that access university data, Cal Poly has adopted a service based approach to deliver personalized content. In migrating from uPortal 3 to 4 many custom channels were re-written and DAOs were replaced with service layers. This enabled our native mobile application through OAuth2 authenticated REST services to deliver a range of public and personal data to students, faculty and staff.
With service layers in place mobile applications have a secure methods to acquire data. By leveraging student developers, Cal Poly has built native applications on Android and iOS to optimize performance for a better user experience. Mobile devices that use OAuth2 eliminate the need for storing passwords on the device. OAuth2 also puts the user in control of which devices have access and have the ability to revoke access as needed.
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.
Discuss changing technology in the mobile environment. uMobile was originally developed to use Titanium Studio by Appcelerator, although there is discussion of uMobile using PhoneGap and being purely native for both Android and iOS. Discuss new mobile environments such as Windows 8, Ubuntu, Firefox OS, and Blackberry 10.
Also discussion on future portlet development using DAOs and JSON feeds that could be used for both uMobile apps (having native portlet views) and uPortal portlets.
2nd–7th June 2013