A new (half-time) developer started on the ADMIRAL project yesterday. After the usual administrative details, and setting up as development environment, we did a mini sprint plan for the next 2 weeks of the ADMIRAL project. I say a mini-sprint plan, as we didn't do the full activity/user story selection, task breakdown and scope bartering, but rather reviewed the remnants of the most recent active sprint plan and identified key unfinished tasks to be tackled.
The next goal for the project is to complete the functionality covered by phase 1 of the project plan by the end of October, with front-to-back submission of research datasets to the Library Services Databank repository service, and providing visible web-based feedback to our research partners of the submitted datasets. This we intend to use as the basis for iterative improvements and enhancements in phase 2 of the project, with the researchers guiding us concerning what constitutes useful metadata to capture and expose with the submitted datasets.
The sprint plan for the period to 7 September aims to:
- review, debug and update documentation for the ADMIRAL system scripted creation procedure
- create a new ADMIRAL file sharing deployment for the evolutionary development group
- file store bug fixes (password over unencrypted HTTP channel; https access reporting server configuration error
- progress work on Shuffl RDF support
Review of sprint 10:
Plan for sprint 11:
We've also had a technical meeting with the Library Services developer of RDFDatabank (aka Databank), the data repository system: