The DataVault sprints ahead

Phase three of the DataVault project is now earnestly underway.  Two weeks ago we held the first of our monthly DataVault project meetings, with Mary McDerby and Thomas Higgins (University of Manchester) visiting us in Edinburgh.  One of the changes we are making to this final six month phase is to move to fortnightly development sprints.

We’re now almost at the end of the first sprint, so reviewed the outputs during a Skype call today.  We use Trello to manage a backlog of tasks, which then get selected for the next sprint. Most of the development tasks are now completed or almost finished.  We also started planning the stories to be tackled in the next sprint, however due to Easter, this will be a little shorter than normal:


In the first sprint (sprint 1) we undertook some rationalisation of the API (as it has grown arms and legs over time), added an enhanced auditing feature (using the PREMIS ontology), added an improved runtime configuration option, and provided better error reporting for a problem that occurs when the CSRF tokens timeout.  As always, all of this can be seen in the project’s github account.

In the next sprint we’ll be fixing a few bugs and some of the terminology used (replacing ‘restore’ with ‘retrieve’ when getting some data from the DataVault), and adding better application logging.

Leave a Reply

Your email address will not be published. Required fields are marked *