2006-06-22 Project-wide 3:45 BST

Agenda

• Review of last project-wide meeting notes/issues
• Week-in-review
  • Baltimore
  • Boston
  • Dundee
    • OME and OMERO inteoperability status and plans. (Jason)
    • Sample OME file status (Jason)
    • OME 2.5 Hello Worlds from Baltimore and Dundee? (Jason)
    • Circular deps. and prioritizations during integration (JAM)
    • Changes: new libraries, et al.
    • Vacation planning — which iterations are empty? (JAM)
    • Did anyone look at IAdmin? (JAM)
    • Roi questions for data generation (JAM)
  • Madison

Notes

• As a reminder, please do review and add to the existing meeting notes before the meeting. All participants are reminded and encouraged to review and add items which are of interest to them.
• The OMERO server is still on track for our second milestone (which is due next week). Following this, we will be working on our security model and looking at OME <-> OMERO integration, which is one of our big next steps. Additionally, with the potential for an OME development team being put together to handle OME <-> Java integration at NIH, we should look at how to get to get both the OME and OMERO teams working together in the very near future. Josh and Ilya suggest we define some of the terms of "Interoperability" such as how "real time" is it going to be? What data can be lost between the two? What is the quality of service (time lag) between the two databases, Etc. One suggestion is that we look at the OME API reading OMERO, and the OMERO API reading OME. Jason suggests we resolve these definition issues by getting some feedback from developers and users about what requirements everyone feels they need, and come up with a preliminary definition in the next couple of weeks.
• There was some discussion about the minimal spec requirement for a file to be "OME Compatible" and Josiah suggested we have requirement spec levels. For example, an OME Spec 1 format might just have pixel data, whereas a OME Spec 2 file might also contain channel information. We also talked about how far we should go into (if at all) the files that may not be in the users hands (such as microscopy ini files).

Action Items

• Moving forward with interoperability, we need to poll developers and users about their requirements for interoperability between OME and OMERO.
• Jason and Ilya please get together within the next week to work on a release schedule for the OME spec.
• Brian, Chris, and Curtis need to talk to import formats, bio-formats, and whether we should import access files (and how to do that).
• Please make sure you get your vacation time marked in the calendar by next week.