ADMIRAL PlanMeeting 17
From ImageWeb
Sprint 17 Planning meeting
Meeting held on: 26-Jan-2011, 10:00 - 12:00 Present: GK, BA
| Sprint | Dates | Effort | Planning meeting | Review meeting |
|---|---|---|---|---|
| Sprint 17 | 26 Jan - 11 Feb | 13 days | sprint 17 planning | sprint 17 review |
Agenda
Primary goals ..
- Introduction, agenda bashing
- Calendar review for next weeks
- Review identified activities and identify activities required for phase 1
- Review or analyze tasks for selected activities
- (Estimate effort for tasks)
- Finalize sprint plan
- Review meeting and wrap up
Meeting
Calendar review
- 26 Jan
- GK: teleconferences
- 2 Feb
- Wf4Ever telecon
- 7 Feb
- Meeting?
- 11 Feb
- GK: away PM
Sprint duration and available effort
Duration 13 days: 26-Jan to 11-Feb
Committed activities:
- Sprint planning (GK:0.5, BA:0.5)
- Sprint review (GK:0.5, BA:0.5)
- Other activities (GK:1.0)
- Non-project time (10%) (GK:1.0, BA:1.0)
Time available to schedule after committed activities:
GK: 10 days
BA: 11 days
Focus for sprint
Top:
- Help researchers to submit real datasets
- More data storage capacity for Silk group
- Follow-up with Evo Devo group
- Deploy to additional research groups
- Discuss deployment with Behaviour Group
- Discuss requirements (possibly for field deployment) with Elephant group
- Fix submission interface to use revised Databank interface
Medium:
- Prepare demonstration system for #jisc11 conference
Ongoing:
- Improve dataset annotations based on researcher feedback
- Dissemination, feedback, sustainability
Activity analysis
ADMIRAL documentation
- Write up VM deployment instructions when migrating users to a new system (GK)
ADMIRAL deployment to Silk Group
(Awaiting availability of increased disk storage capacity through departmental NAS)
- Chase up availability of new disk storage (GK)
- Create new deployment to use new departmental NAS (iSCSI) (GK/BA)
- Install NAS-dedicated network connection for ADMIRAL host (GK)
ADMIRAL deployment to Evolutionary Development Group
(New version of ADMIRAL deployed, needs user passwords to be reset)
- Email SS to arrange meeting to update user password (GK)
- Email SS/HT to arrange meeting to discuss use of ADMIRAL storage on a date when DMS is available (GK)
ADMIRAL deployment to Behaviour Group
- Arrange meeting to discuss storage requirements, access requirements and users to be configured (DMS)
- Create and test an ADMIRAL instance (GK/BA)
- Introduce researchers to system; create accounts (GK/BA/DMS)
ADMIRAL deployment to Elephant Group
- Follow up contact with LK; any news?
- Think about distributed/field deployment of ADMIRAL; data synchronization issues (GK - priority 3)
Databank deployment with real datasets submitted (priority 1)
- Work with researchers to select and submit datasets, preferably with associated open access publication that can be included (DMS/GK)
- Work through submission process; discuss process and resulting published data with researchers
Databank interface changes
(The dataset viewing interface, and maybe other aspects was broken by a new Databank deployment)
- Fix up ADMIRAL to work with new Databank deployment (AR is away)
- Chase AR for updated Databank test suite
JISC conference demonstration
(Awaiting stand-alone Databank VM image from AR, and repair/upgrade of lab MacBook)
- Create demo deployment of ADMIRAL
- Chase AR for Databank VM image
- Deploy local copy of Databank
Also:
- Review Databank host/silo configuration in running system
- Consider possibility of providing working ADMIRAL system to Peter Sefton (Fascinator) while doing this.
ADMIRAL features (priority 2-3)
- When confirming submission old dataset, show version, id, date (BA - priority 2)
- Dataset confirmation page: display summary of content (not scheduled)
- Dataset selection page: default expand top-level dirs only (not scheduled)
- User administration web tools (not scheduled)
- [Support multiple collaborator groups - suggested by SS, requirement not fully clear] (not scheduled)
Technical debt and bugs (priority 2-3)
- First click in view submitted dataset doesn't display data - why? (BA - priority 2)
- Dataset tree used in submission and display: refactor (common code in single module, etc.) (BA - priority 2)
- Replace href from tree display in dataset selection page (BA - priority 2)
- Refactor HttpUtils to use object for session data (host, silo, user, password) (BA/GK - priority 3)
- HTTP visibility of common shared directories; e.g. /shared/, /collab/, etc. (hard) (not scheduled)
- ADMIRAL to use proper signed server certificates
- Allow creation of ADMIRAL accounts for which data already exists
Activities not scheduled this sprint
DOIs for datasets
(Awaiting finalization of Datacite service and implementation in Databank)
- Identify any ADMIRAL UI changes required
- Implement required changes
Embargo requirements
- Continue embargo requirement discussions with researchers in the context of a working system
User administration interface
(Currently, user admin is by shell scripts. We are thinking about fronting these with a simple web interface.)
- Brief survey LDAP user admin tools
- Propose outline design for user configuration tool
- Review and discuss proposed design
- back-end integration
- Front-end interface
- Flexibility
- Simplicity
- Testability
- Create test framework for design
- Implement design
Feedback: data management plans
(To plan)
Feedback: research data flows
(To plan)
Support for multiple collaboration groups
(Tentative requirement from Development Group)
Selective display of datasets for submission
(Tentative requirement from Silk Group: when selecting dataset for submission, provide option to display only those data that belong to the currently logged in user. Awaiting feedback from real system use.)
Review meeting and wrap up
Our live project plan is recorded using index cards. This page summarizes the planned activities.
