From ImageWeb

MEETING CANCELLED

Contents 1 MEETING CANCELLED 2 ADMIRAL project monthly meeting: 18-Mar-2010 2.1 Attendees 2.2 Goals 2.3 Agenda 2.4 Minutes 2.5 Notes

MEETING CANCELLED

Due to unavailability of key partners, we decided there was little purpose in holding this meeting. We'll try and do better next month.

ADMIRAL project monthly meeting: 18-Mar-2010

When: 18-Mar-2010, 11:00

Where: Room D31, Zoology Department, University of Oxford (http://www.zoo.ox.ac.uk/info/contact.htm)

Lunch will be provided after the meeting.

Please report to the Zoology Reception on arrival, and ask to be directed to Room D31 (up two floors in lift at back of building, then left out of lift, right down central corridor, last door on left).

MEETING CANCELLED

Attendees

• Expected to attend: David Shotton (PI, IBRG), Graham Klyne (Project manager, IBRG), Diana Galletly (RA, IBRG), Ben O'Steen (RA, OULS).

• Apologies for absence received: Sally Rumsey (PI, OULS).

• Other partners and members of the Advisory Board: Simon Hodson, Paul Jeffreys, Alex Kacelnik, Peter Murray-Rust, John Wilbanks and Max Wilkinson are notified for information and welcome to attend if they wish to and are able, but are not expected to attend.

Goals

• For all partners to understand what progress has been made to date, and how this relates to our original expectations.
• To understand the next steps to be addressed.
• To identify interactions between partners that are needed to ensure continued progress of the project.
• To allow face-to-face discussion of technical and other matters that may be helpful.

Agenda

1. Introduction, setting the scene, agenda review (DS).
2. Review progress to date, noting divergence from the original project plan:
   • user data audits and requirements gathering (DS).
   • test system setup and access control configuration (DG).
   • production server installation and live service deployment (GK).
   • security modelling (GK).
   • DataBank submission requirements gathering (GK and BO).
3. Interactions with related projects (DS).
4. Discuss forthcoming events and deadlines (GK).
5. Articulate the next steps to be addressed (which our agile approach allows to differ from those indicated by the original plan):
   • by IBRG (e.g. dataset submissions, annotation) (GK).
   • by OULS (e.g. DataBank submission requirements, embargo) (BO).
6. Identify required partner interactions, particularly for the next month, to ensure forward progress (GK).
7. Technical and/or other detailed discussions (all).
8. Wrap up, confirm actions (DS).

Minutes

(TBD)

Notes

• Live project plan: ADMIRAL planning
• Previous monthly meeting: (None)
• Next monthly meeting: ADMIRAL 20100415 monthly meeting