Development Updates

Sprint 59 – September 5, 2014

Sprint 59 saw further progress towards implementing the Avalon Media System at Indiana University. During this sprint we focused infrastructure matters such as restart documentation and notifications for monitoring alerts. We also started a series of video playback tests with the goal of ensuring the best possible playback quality in low bandwidth scenarios. Testing for mobile and desktop environments will be completed using a variety of low, medium, and high bitrate options in addition to the current Avalon settings.

Sprints 57 & 58 – August 2014

After completing Avalon’s upgrades to Hydra 7.1 and the latest versions of Blacklight, Ruby on Rails, and Bootstrap, the developers have dedicated this month to functionality and styling. As a part of this work, over 2,000 lines of code were changed to make Avalon more robust for future Blacklight upgrades. Some of the new perks include better responsive design performance and the ability to delete facet selections directly from the facet menu.

 

Sprints 55 & 56 – July 2014

July was marked by several exciting achievements. After completing extensive testing of Avalon 3.1 during Sprint 55, the team released Avalon 3.1 to the community. Northwestern University successfully implemented the new release on their production server, and Indiana updated their pilot server as well. The following sprint had the highest velocity to date. For those interested in our statistics, the team earned a total of 96 story points! 

 

Release 3.1 Now Available

We’re pleased to announce the release of Avalon 3.1. The major goal for our first dot release is to pave the way for production implementations of the Avalon Media System at Northwestern University and Indiana University, the Avalon software development partners. We’ve achieved production at Northwestern University and are looking forward to taking this next step at Indiana University.

 

Release 3.1 adds the following capabilities:

Tags:

Sprint 54 – June 27, 2014

The Avalon team has been busy balancing improvements, testing the Avalon 3.1 source code, and eliminating bugs in preparation for our next release. Avalon html pages have been updated with search engine optimization metadata and microdata to increase the clarity and usefulness of information provided in Google search results about Avalon media items. We’ve also updated the Avalon Collections Guide wiki page to reflect the new features of our upcoming release.

Sprint 53 – June 13, 2014

In Sprint 53, the Avalon team completed work on LDAP-based access control and made significant improvements to the error messages generated by the batch ingest process. We’re working to strengthen the information provided about Avalon media items in Google search results with Schema.org and Google Webmaster Tools serving as our main resources in this process.&nbsp

Sprint 52 – May 30, 2014

In our last sprint, the Avalon team continued its progress on a major feature of 3.1, allowing Avalon collection managers to use LDAP groups to provide access to content. With Avalon 3.1, content permissions may be assigned to user groups created within Avalon, to LTI courses, and to LDAP groups. Enabling LDAP groups requires a simple configuration. The organization of LDAP groups and use of LDAP active directories vary by institution, so we are exploring the most efficient method for Avalon to search for LDAP groups.

Sprints 49, 50, & 51 – April 18, May 2, & May 16, 2014

 

Since the release of Avalon 3.0, the team has focused on putting Avalon in production at Northwestern University as well as adding features needed for IU’s move to production. We expect to implement and release the latest features by the end of June as a minor release 3.1.

 

Release 3.0 Now Available

 

Release 3.0 of the Avalon Media System is now available. Both Indiana University and Northwestern University will be using this release to set up production environments and we hope other institutions will join us.

 

Release 3.0 adds the following capabilities:

  • provide authorization for item access from your learning management system by integrating Avalon as an LTI tool (Learning Tools Interoperability is a standard used by many course management systems)

Tags:

Sprint 48 - April 4, 2014

 

We have an Avalon release candidate! We've tested and tagged the code and completed technical documentation about how to configure permalinks integration. We had new eyes look at our manual installation process. Since our production environments are going to look different from your production environments, standalone instructions for the various components such as Fedora, MySQL, Solr, Red5, Matterhorn and others have been provided to help get Avalon users up and running without too much trouble.  

 

Pages