Demo

Sprint 38 - November 1, 2013

 

This week was all about refinement. We started work on refining a new skin for the MediaElement.js player so that the player has nice sizable buttons that are optimized for both desktop and touch browsers. We refined and finished testing our migration tools and documentation for the various installation methods, so if you installed Avalon 1.0 you should be only six steps away from using Avalon 2.0!  We also started on one of our big priority stories for Avalon 3.0, which is to skip the transcoding step for media that has already been processed.

 

Sprint 37 - October 18, 2013

 

With Avalon 2.0 ready for public consumption, the team spent this sprint working on documenting our migration paths for the different installation methods. Our last two sprints have been devoted to setting up the distribution of our releases so we talked quite a bit about how to streamline the process so we can hit our releases more efficiently.  The team looked into our new media player, MediaElement.js, some more to figure out how to contribute new features and bug fixes. We have a plan!  

 

Sprint 35 - September 20, 2013

 

Who is at code release for Avalon 2.0?  We are! During our demo, the team decided that we had reached code release, which will allow the team to focus on updating methods for everyone to test out Avalon 2.0.  Bugs have been squashed, labeling has been updated and improved, and documentation is being written. A few of our bugs were fixed and pushed upstream to the Hydra Project--we are very pleased to contribute back to the community!

 

Sprint 34 - September 6, 2013

 

Avalon 2.0 is much closer to seeing the light of day. We have a tried and true method for allowing migration of fixtures and people from 1.0 to the shiny new release 2.0.  Collection information used to be saved as a string but now Avalon 2.0 has a collection model allowing anything from 1.0 to be migrated to 2.0 with just one command!

 

Our punch list includes: final round of testing, some improvements to the interface, more documentation (is there ever enough?) and updating our installation methods. Fingers crossed that you will be seeing Avalon 2.0 very soon!

Sprint 33 - August 22, 2013

 

This sprint the team focused figuring out a method for migrating the content and roles/permissions from release 1.0 to release 2.0.  The team also spent quite a bit of energy on identifying bugs and fixing them.  Although we are not yet at code release we are much closer!

 

Watch the full recording of this week's demo.

Sprint 32 - August 9, 2013

 

Avalon version 2.0 has officially hit a feature freeze!

  • The software now has an "About" page that can be used to show the health of the various components. You can see what version you are running of all of the components to. 

  • Blurry, black thumbnails in your results are a thing of the past.  Thumbnails and poster images can be set before publishing each image. Batch uploading also allows for the offset to be set for the thumbnail and poster image too. 

Sprint 31 - July 26 Demo Recording

 

As Release 2.0 is nearing, the Avalon team has been working to include a few new features as well as refining the player. Upgrading to Hydra head 6.0 fixed a number of bugs that kept on popping up. The developers continued to work on incorporating features into the collection/unit workflow and now collections can be deleted and units can be browsed. We were able to do some testing and bug fixing on the mediaelement.js player which looks good and behaves in a more predictable manner. Avalon is maturing before our very eyes!

Sprint 30 - July 12 Demo Recording

Sprint 28 - June 14 Demo Recording

 

After last week's venture into exploring administrative units, this week the team focused on how collections can be employed by Avalon.  Administrative units can now create and manage collections of items. This will be an easy way for collection managers to add content to a specific collection, and our metadata specialists spent a lot of time thinking of how those relationships would be captured in each MODS record. We are also happy to report that both IU and NU's pilot systems are up and running! 

 

Sprint 27 - May 31 Demo Recording

 

This week the team worked on adding new functionality to Avalon. We introduced the concept of units to Avalon Media System. The term "unit" refers to an Administrative Unit, which can be made up of many collections and items. We also added some snazzy auto complete features to select unit managers. Besides units, more investigation of the mediaelement.js player occurred during this sprint. IU and NU spent some time getting their pilot systems set up. We're just about ready to see what Avalon 1.0 can really do! 

 

Pages