Hi Nicolaas, Thank you and the OAE team for your hard work on this new release.
I tried the new release and have a few questions: 1. The Google Analytics module only asks for the tracking ID - based on my experience, the tracking code needs to be included in the pages in order for GA to work but I do not see how to do that in the Admin UI. 2. The CSV user import is a very nice feature but I cannot find it in the Admin UI - any pointer? Thanks, Harry On Oct 29, 2013, at 4:43 PM, Nicolaas Matthijs <[email protected]> wrote: > The Apereo Open Academic Environment (OAE) project team is excited to > announce the second major release of the Apereo Open Academic Environment; > OAE Alpine Swift or OAE 2.0. > > Apereo OAE Alpine Swift brings a wide range of user-facing improvements such > as: > Following > Video support > Terms and Conditions > A number of usability refinements > Internationalization and Accessibility improvements > > Try it out > > OAE Alpine Swift can be experienced on the project's QA server at > http://oae.oae-qa0.oaeproject.org. It is worth noting that this server is > actively used for testing and will be wiped and redeployed every night. > > The source code has been tagged with version number 2.0.0 and can be > downloaded from the following repositories: > > Back-end: https://github.com/oaeproject/Hilary/tree/2.0.0 > Front-end: https://github.com/oaeproject/3akai-ux/tree/2.0.0 > > Documentation on how to install the system can be found at > https://github.com/oaeproject/Hilary/blob/2.0.0/README.md. > > The repository containing all deployment scripts can be found at > https://github.com/oaeproject/puppet-hilary. > > > Changelog > > Following > > It is now possible to follow other people, allowing for important and public > activities from that person to be shown in your personal activity feed. This > provides a way to learn more about the collaboration in which your peers are > involved, and offers an opportunity for serendipitous discovery of content, > discussions, people and groups at the same time. > > Video Support > > An integration with MediaCore (http://mediacore.com) is now available, > allowing for all videos to be uploaded and played inside of OAE. The > integration makes it possible for uploaded videos to be transferred to and > processed by MediaCore, generating a thumbnail and video that can be played > in all browsers. This video is delivered to the OAE user interface through > the MediaCore video player. > > The MediaCore video support can be enabled and configured on a > tenant-by-tenant basis through the administration UI. > > Terms and Conditions > > A Terms and Conditions agreement feature is now available. If configured, > this agreement is presented to all users when they sign in for the first time > and they will need to accept it before they can use the system. The terms and > conditions can be internationalized in multiple languages at the same time. > > The Terms and Conditions agreement can be enabled and configured on a > tenant-by-tenant basis through the administration UI. > > My Groups > > The My Groups page now follows the same behaviour as the My Library and My > Discussions pages when being viewed by other people. Only groups that can > already be seen by the person viewing your My Groups page will be shown. > > Monitoring > > Integration with Google Analytics is now available out of the box, allowing > for a better understanding around usage patterns and total usage to be > gained. This can be enabled and configured on a tenant-by-tenant basis > through the administration UI. > > TinCan API > > OAE is now capable of pushing activities to a Learning Record Store using the > TinCan (http://tincanapi.com) or Experience API. This API is a new > specification for learning technology that makes it possible to collect data > about the wide range of experiences a person has (online and offline). This > API captures data in a consistent format about a person or group’s activities > from many technologies, of which OAE is now one. > > The TinCan API support can be enabled and configured on a tenant-by-tenant > basis through the administration UI. > > Internationalization > > The OAE project has decided to adopt Crowdin > (http://crowdin.net/project/apereo-oae) as its official translation platform. > This allows for OAE to be translated through the Crowdin web UI without > needing to set up a local development environment. > > In addition to making it easy to translate all of the OAE keys, it provides > translation suggestions based on a Translation Knowledge Base and machine > translations. Crowdin provides a very useful overview of the translation > completeness of the different supported languages and makes it easy to see > which keys still need to be translated. A synchronisation script has also > been provided that will automatically make new keys available to Crowdin and > will pull the newest translations into the code base. > > Through this Crowdin integration, OAE Alpine Swift includes the following > complete translations: > Catalan > Chinese > Dutch > French > German > Spanish > Valencian > A special thanks goes to Frederic Dooremont, Toni Devís López, Samuel > Gutiérrez Jiménez-Peña, Harry Wang, Yildiray Ogurol and Mark Breuker for > providing these translations. > > Finally, OAE will now also automatically detect the preferred language based > on the user's browser settings, according to internationalization best > practices. We will only default to the language configured in the admin UI if > this has not been set. > > CSV User Import > > A tenant can now be pre-populated with a large set of users by uploading a > CSV user file. These accounts can be associated with a specific > authentication strategy and existing accounts will not be overridden. The CSV > upload can be done by a global or a tenant administrator. > > Usability Improvements > > A long list of usability refinements have been added. Some of the more > notable ones are: > Improved previews for activity feed items > Improved button wording and clarity > Automatic link recognition in comments and discussions > Keyboard acccessibility improvements (e.g. refocussing modal triggers after > modal is closed) > etc. > Automated testing > > A number of improvements have been made to the automated QUnit tests, > including making sure that all tests are automatically run after every commit. > > > Get in touch > > The project website can be found at http://www.oaeproject.org. The project > blog will be updated with the latest project news from time to time, and can > be found athttp://www.oaeproject.org/blog. > > The mailing list used for Apereo OAE is [email protected]. You > can subscribe to the mailing list at > http://collab.sakaiproject.org/mailman/listinfo/oae-dev. > > Bugs and other issues can be reported in our issue tracker at > https://github.com/oaeproject/3akai-ux/issues. > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
