With this sprint, the Avalon team completed work on one of the main new features of Release 3.3: importing descriptive metadata from an online public access library catalog (OPAC) into Avalon. This may be accomplish via batch ingest by using a bibliographic record identification number. The metadata import functionality will be configurable to meet local cataloging practices and currently includes catalog key, Online Computer Library Catalog (OCLC), and Library of Congress Control Numbers (LCCN) identifier types as options.
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.
We have been a little delayed in posting our last two sprint demos but the delay was worth the wait. During the last month, the Avalon team has been nailing down some pretty impressive features prior to our next release.
During the 42nd sprint of the Avalon Media Project, the team made major progress on our 3.0 features... and then some! Our player and content is now embeddable even when the content is restricted. Avalon can now support permanent URLs (although at this point we have only configured it to work for Northwestern, which uses CNRI's Handle System). We continued work on campus and course-based access control through learning tools interoperability (LTI).
Sprint planning on Friday the 13th. What could possibly go wrong? Well...nothing. It was a swell sprint planning session. The team closed out ALL of the stories plus some additional non-spooky bugs.
Remember the 15th of November, when the Avalon team completed over 50 points in a single sprint? This sprint finally got us moving towards new features for Avalon 3.0. A big priority is master file management; we were able to make some big strides in making sure the system can move, leave in place, or delete master files. Our next sprint will focus on making Avalon aware of where files and derivatives are being stored.
Our November 14 webinar was superb! With zero technical glitches and great questions and feedback, we felt it was a success. Jon Dunn (Project Director, IU), Mark Notess (Product Owner, IU), and Julie Rudder (Product Owner, NU) led the webinar.
If you were unable to attend, don't fret. The webinar recording and slides can be viewed at your leisure.
Contact Us | Facebook | Twitter | Listserv | RSS