ADMIRAL 20101216 project partners meeting

From ImageWeb

Jump to: navigation, search
When: 16-Dec-2010, 11:00
Where: Room D31, Zoology Department, University of Oxford (http://www.zoo.ox.ac.uk/info/contact.htm)
Present: DMS, MW, GK, BA, AR, NJ
Apologies: SR

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).

This meeting page: ADMIRAL 20101216 project partners meeting

Previous meeting page: ADMIRAL 20101118 project partners meeting

Contents

Attendees

  • Expected to attend: David Shotton (PI, IBRG), Graham Klyne (Project manager, IBRG), Bhavana Ananda (IBRG), Sally Rumsey (PI, OULS). Anusha Ranganathan (OULS), Neil Jefferies <neil.jefferies@sers.ox.ac.uk> (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

A key goal for this meeting is to establish a path towards stabilizing the functionality and API for the library Databank service, and creating a stable deployment.

Other goals for this meeting will be to report on progress and coordinate continuing development:

  • towards completion of phase 1 of the project: desktop-to-silo dataset collection and submission, and reflecting the results back to the research users
  • towards deploying a second instance of the ADMIRAL data store,
  • researchers' feedback on ADMIRAL system and Databank dataset submission

We also report on and discuss progress in other activities related to the project.

Agenda

  1. Introduction, setting the scene, agenda review (DMS).
  2. Review actions from previous meetings
  3. Review recent progress and coordinate continuing development:
    • stabilization and live deployment of the RDF Databank service (AR/NJ)
    • toward ADMIRAL submission of datasets in the RDFDatabank Entity store (GK/BA)
    • reflecting submitted databank contents back to researchers (GK/BA)
    • toward issuing DOIs for datasets (AR)
    • on further deployment of filestore to research users (GK)
    • on interactions with test user groups. (GK)
    • outstanding issues for completion of phase 1 (GK)
    • other developments (GK)
  4. Technical and/or other detailed discussions (all).
    • Review progress for ADMIRAL phase 1 moving to phase 2
    • Outstanding issues for completion of ADMIRAL phase 1
    • Issues and visible Databank requirements for ADMIRAL phase 2
  5. A.O.B.
    • Wf4Ever kick-off meeting
    • Research Objects collaboration with Manchester Uni
  6. Wrap up, confirm actions (DMS).

Minutes

Review of actions

Outstanding from before last meeting:

ACTION: MW: to provide timescales to determination of minimum metadata for DOIs - continues.

  • DMS has seen draft spec, sent comments, and asked for finalized metadata requirement.
  • Expecting final requirement by early December

ACTION: GK/AR: circulate notes about implementation of content negotiation (non urgent, important) - Continues

ACTION GK/AR: prepare proposals for next meeting with NJ present (start with email/wiki). Done - see working notes at http://imageweb.zoo.ox.ac.uk/wiki/index.php/ADMIRAL_Databank_specification_proposal

ACTION GK: contact Behaviour group to discuss security requirements when Evo Devo system has been tested. Continues

ACTION DMS: Send copy of final DOI metadata requirements to GK when available. Continues

  • awaiting final requirements
  • if AR received details first, please circulate (AR notes nothing yet received from BL)

ACTION GK: take note of minimimal metadata for DOIs in planning minimal metadata for ADMIRAL submission. Continues

Summary of actions from last meeting:

ACTION: DMS fix meeting date with LK (Done - meeting held 13-Dec-2010)

ACTION: AR - circulate minimal DOI metatadata requirements if received before anyone else does

ACTION: DMS try to reschedule advisory board meeting for 13:30 rather than 14:00, to allow more time for SR who needs to leave by 15:00 (Done - scheduled for 14:30 to accommodate PJ)

Follow-on actions

Review recent progress

Stabilize RDF Databank specification and live deployment

(AR/NJ)

See discussion document: http://imageweb.zoo.ox.ac.uk/wiki/index.php/ADMIRAL_Databank_specification_proposal

Submission of datasets to the RDFDatabank Entity store

We have a functional submission interface, but there are some bugs and its is not yet sufficiently usable.

Our current sprint plan includes addressing a number of outstanding issues.

Reflecting submitted databank contents back to researchers

(GK/BA)

The initial dataset display has been implemented, and is being/has been updated in response to feedback from the Silk Group.

Issuing DOIs for datasets

(AR)

Further deployment of ADMIRAL filestore to research users

Induction meeting was scheduled, but then postponed to (Wed 15-Dec?) due to GK being caught up in Madrid air traffic fiasco.

Meeting held on 15-Dec-2010 - went well.

Also held exploratory meeting with Elephant Group (LK) - some interesting challenges here raised by exigencies of gathering and protecting field data

Interactions with test user groups

(GK)

Met with Chris Holland. Very useful feedback. Meeting notes: ADMIRAL 20101207 meeting CH

Met with Lucy King from Elephant group, interesting discussions about preservation of and access to sensitive field research data. Notes TBD.

Introduced Seb Shimeld's Evolutionary development group to ADMIRAL. Went well, but some new requirements emerging (esp. multiple collaborations). Notes TBD.

Other developments

(GK)

Request from JISC for benefits case / business case feedback about ADMIRAL - draft at ADMIRAL_Benefits_/_Business_Case.

Proposal to demonstrate ADMIRAL at the JISC conference in March 20111 - ADMIRAL_JISC_Conference_Demonstration_Proposal.

Technical and/or other detailed discussions

Review progress for ADMIRAL phase 1 moving to phase 2

Basic shared file store implemented and deployed to two groups. Actual deployment has gone well in both cases, with researchers keen to use simple file sharing with automatic daily backup to University HFS.

The Silk Group rapidly used up all their disk allocation, and wish to greatly expand their storage capacity to 4Tb. Having recently seen how easy it was to use ADMIRAL storage, SS immediately commented that he was inclined top broaden its use beyond what we had most recently discussed. I made a point of telling SS to let us know when he got down to his last 100Gb. All this suggests that researchers' use of ADMIRAL

Zoology IT support are deploying a JBOD iSCSI array which we should be able to connect to ADMIRAL: provides route for research groups to buy in storage capacity as needed for new research projects (just under £300/Tb is price mentioned - which is *much* cheaper that other managed storage options available).

About 5 montns behind original plan, for diverse reasons. Less progress than hoped on metadata services.

Dataset submission... going well, closing the lop from desktop to repository. Waiting live deployment of Databank. When demonstrated to CH, he said that he'd submit everything for preservation if we can resolve his disk capacity limitations.

Discussion of research objects ...

Sustainability: aiming to use ADMIRAL as test bed for provenance work as part of forthcoming 3-year EU project

Outstanding issues for completion of ADMIRAL phase 1

We are under some pressure from the JISC to show concrete benefits delivered to our research users. This is rather dependent on having a visible and stable Databank instance deployed.

Needed:

  • production/stable instance of databank
  • stable Web address for Databank instance
  • Databank authentication - username looks like SSO
    • SSO via WebAuth?
    • Note we use programmatic submission
  • real research data in Databank
  • Databank performance issues (??)

Later, may address through phase 2:

  • software version migration tools
  • user management tools
  • multiple collaborations (from EvoDevo)
  • Data Object model as input to Research Object debate
  • naming/scope rules - granularity of silo allocation - additional naming hierarchy?
  • access previous versions
  • retract manifest triples?
  • UI refinements
  • light and dark archives
  • disk usage calculation and quota management

Issues and visible Databank requirements for ADMIRAL phase 2

(from previous meeting - repeated here to maintain visibility)

Original work pakages for Phase 2:

  • WP5 Links to external web services
  • WP6 Formalization of annotations
  • WP7 DOIs for datasets
  • WP8 Licences for published datasets

WP7 and WP8 are relatively trivial. WP5 and WP6 are more ambitious.

We intend to use researcher feedback to drive specific improvements to ADMIRAL.

The implications for Databank:

  • DOI allocation and handling and servicing to be completed
  • Licence metadata: Databank to be licence-aware?
  • Manifest.rdf imports other RDF files within the dataset - implementation and test case
  • Metadata retraction?
  • File permissions within zip file
  • (embargo handling? not discussed in meeting)

BRII project did a lot of service linking - e.g. pubmed, that we might be able to use. (Ext: EPSRC. PubMed. Int: Philosophy. Medical Sciences. Oxford organizational units.) A possible link with OxPoints data was noted.

A.O.B.

GK attended Wf4Ever kick-off meeting in Madrid. Have increasing confidence that ADMIRAL can be used as a test-bed for developments around "Research Objects" and dataset provenence, providing cause and context for ongoing ADMIRAL-related activity and support for researchers.

DMS attended a meeting in Manchester at which participants agreed to work together to develop and realize the notion Research Objects... (DMS)

(DRYAD UK? DMS)

Wrapping up

Confirm actions carried forward

Confirm new actions

Next meeting

Per schedule, this will be 20-Jan-2011

Notes

Personal tools
Oxford DMP online
MIIDI
Claros