ADMIRAL 20101118 project partners meeting

From ImageWeb

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

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 20101118 project partners meeting

Previous meeting page: ADMIRAL 20101021 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).
  • 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

  • The main focus of this meeting will be to report on progress:
    • 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,
    • on our interactions with the Library Services' data repository, and
    • progress with BL to issue DOIs for datasets
  • and also to review progress in other aspects of the project and related activities.

Agenda

  1. Introduction, setting the scene, agenda review (DMS).
  2. Review actions from previous meetings
  3. Review recent progress:
    • towards stable specification for RDFDatabank (AR/SR)
    • toward ADMIRAL submission of datasets in the RDFDatabank Entity store (GK)
    • 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).
  5. A.O.B.
    • Meeting with EIDCSR/SUDAMIH project staff
  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

Summary of actions from last meeting:

ACTION GK: follow up and confirm meeting with SUDAMIH/EICDSR James Wilson. Done

  • meeting held, brief report in AOB

ACTION GK/AR: hand over Databank test cases. done

ACTION DMS: copy AR with email to MW requesting DOI prefix allocation for OpenCitation project. Done.

ACTION AR: ask MW for similar prefix allocation for ADMIRAL project. Done

  • awaiting completion of ORA registration as DOI issuer "very soon" (week or two).

ACTION AR: follow up BL contact provided to gain access to DOI test server . Done

  • subsumed by previous action

ACTION DMS: ask NJ (cc:SR) to attend November meeting to discuss remaining technical issues, esp. auth/naming/indexing scope. Done

  • NJ cannot attend November, but will attend December meeting.

ACTION GK/AR: prepare proposals for next meeting with NJ present (start with email/wiki). Continues

  • AR to send email with outline ideas to GK. See also later discussion in this meeting.

ACTION DMS: provide link to Dryad naming conventions: send to Admiral partners list. Done

  • Copy forwarded to admiral-partners list by GK.

ACTION GK: plan to deploy ADMIRAL instance for IBRG. Done

  • deployment in progress, running late, hoping to complete today.

ACTION GK: contact IT support for IP address, etc., for evo devo deployment + IBRG deployment. Done.

ACTION GK: contact Evo Devo group when an ADMIRAL deployment is ready for them, to schedule "induction". Done'

  • Meeting scheduled for 6 Dec.

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

ACTION DMS: email LK about meeting to discuss securing Elephant field data (ask when she'll be in Oxford). Done

  • LK in Oxford for D.Phil viva in week beginning 13 December.
  • DMS to follow up and fix meeting date

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

  • awaiting final requirements
  • if AR received details first, please circulate

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

ACTION DMS: to decide date for next advisory board meeting (to not preceed EvoDevo deployment; coincide with phase1/phase2 transition). Done

  • Date set for 16-Dec-2010.

Follow-on actions

ACTION: DMS fix meeting date with LK

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

Review recent progress

RDFDatabank specification

Test suite is complete; AR has problems accessing repo, has sent zip file. Email seems to be missing.

Emails seem to be going missing.

ACTION: AR resend test suite files Done.

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.

Further deployment of ADMIRAL filestore to research users

A base system for the development group has been deployed and tested.

Need to create users and perform induction.

Interactions with test user groups

Meeting with Silk group is scheduled for 7-Dec. Planning to use demo of submission to elicit further requirements to inform development plans for phase 2 of the project.

Other developments

JZ leading Oxford element of EU wf4ever project, working with Dave de Roure; GK to be 80% employed as developer on data provenence package. Intending to continue using ADMIRAL as test bed, as any meaningful developments should stand independently of the workflow environment.

Dryad project setback - Vikas D. offered a much better job at last moment, is not coming. Looking for a replacement. Want to use ORA/Databank as test case for sharing Dryad metadata for submissions from Oxford researchers. Aiming to trial by next summer. SR interested in getting "publication from ORA" data - i.e. full text of published paper to preserve/republish in ORA. Interested in getting data from Dryad for BRII (linked data).

DaaS thought floated ... file system + SOLR as alternative to RDB?

Technical and/or other detailed discussions

Outstanding issues for completion of ADMIRAL phase 1

- real research data in databank - ADMIRAL and Databank bug fixes - databank performance issues - finish initial dataset submission interface (minimally usable submission and view) - stable Web address for Databank instance - authentication fixed username looks like SSO ? production/stable instance of databank? ? authentication? SSO via WebAuth

Later: - naming/scope rules - granularity of silo allocation - additional naming hierarchy? - access previous versions - retract manifest triples? - UI refinements - light and dark

- disk usage calculation and quota management

ACTION: GK send to AR ADMIRAL WebAuth setup links.

Issues and visible Databank requirements for ADMIRAL phase 2

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.

EIDCSR / SUDAMIH meeting

Met with James Wilson, Asif Akram, GK, BA. EIDCSR is running into complexities using HFS as archive. Data volumes mean HFS is strongly preferred system. But having problems with identification and access ciontrol, so also interested in Databank. Were asking about plans for Databank user authentication: one account or several per silo; plans for sharing / access control?

Availability

GK away for most of the next 2 weeks.

Wrapping up

(added after the meeting was closed)

Confirm actions carried forward

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

  • AR to send email with outline ideas to GK. See also later discussion in this meeting.

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

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

Confirm new actions

ACTION: DMS fix meeting date with LK

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

ACTION: AR resend test suite files Done.

ACTION: GK send to AR ADMIRAL WebAuth setup links.

Next meeting

Per schedule, this will be 16-Dec-2010

(This is also the date for a rescheduled advisory board meeting)

Notes

Retrieved from "http://imageweb.zoo.ox.ac.uk/wiki/index.php/ADMIRAL_20101118_project_partners_meeting"
Personal tools
Oxford DMP online
MIIDI
Claros