Agenda

• Schedule for these calls; Thursday PM UK OK?
• Format for calls?
• Next Data Model release.
• Who is supporting OME Server?
• Reports on Current OMERO iterations; Blitz integration and Metadata Workflow (what are links?)
• Current http://trac.openmicroscopy.org.uk/omero/milestone/3.0-Beta4 not really helpful. What to do?
• Need to define next sets of iterations, and decide how this is defined written up, and logged. Suggested iterations (these dates are relaxed; OK?):
  • Oct 13 - Oct 24
    • Metadata Workflow (relax DB, synch'd data model
    • validation of Bio-Formats changes to DV file per Melissa)
    • evaluation of Permissions
    • Note: would be good to know what will be shown on the 24th (Josh)
  • Oct 27 - Nov 7
    • Permissions and Metadata (Permissions turned on, enabled in Clients, Metadata supported in clients
    • add one more file (Zeiss AVI?), Delete turned on in clients)
    • OMERO.web (as discussed, need 2-3 days of rapid evaluation, testing, and fixing)
  • Nov 14 - Dec 1: Loose end tying, and ?
• Need plans for rollout of OMERO.scripts and OMERO.fs.
• Discuss integration of webadminforblitz
  • licenses
  • ease of use

Notes

• Meetings

  • Is Thursday 15:45 UK an ok time?
    • Curtis is flexible
    • Thursdays are bad for Kevin
    • 15:45 UK is a fine time.
    • But what day?
      • Send an email to others to see what the best day is.

• Next data model release

  • No Andrew. Tabling...
  • Need to announce when he gets back
  • Curtis: very happy with everything from a modelling perspective
    • A matter of testing the code generation.
    • Currently is working on efficiency questions

• OME Server

  • No status.

• Iterations

  • transitioning to blitz in previous iteration
  • starting to get metadata support improved in next iteration
  • relevant for Melissa in terms of metadata retrieval from files
    • Ok? Yes. Q: Just working on DV? Starting, but will be working on multiple.
    • Q: What does this mean? ... more explicit support for metdata? in insight?
      • UI standpoint includes viewing and interacting with metadata
      • Defining a workflow for the user so that it's not overwhelming
      • Work on usability side.
      • Sounds good. Let Curtis know if there's anything he can do to help. * Labs in Madison can be guinea pigs. Using OMERO? 2 sci. were using 2.3 * Were using categories which means the upgrade is painful. * Planning to migrate to 3.1. * The metadata workflow is central to Loci. Would be enthusiastic to work on that.
  • What are the targets for the 24th?
    • Insight: a small component in the UI (no data)
    • Server: Loosening things up?
    • Editor: everything is on the instrument model, need a whole branch.
      • Screen/Plate/Well is well-defined. Or Leica.
      • Also working on the performance of the blitz-based importer * Working on granularity * Curtis: also seems weird to be hand-writing code when we have code-generation * Josh: We would need to generate the slice * Curtis: Was planning on doing that. Can auto-generated the Prx delegation. * Curtis: Would like to release ice bindings. It would be good to agree. * Chris: It would help to remove all the single argument methods
  • Who's going to clarify the milestone page?
    • Tickets are ok for us, but not explicit for outsiders
    • @

• Scripts & FS

  • Discussion Chris/JM/Colin: Need to write up bullet points on what's required from client
    • Colin just committed all the code. Mac works. Linux probably works. Windows is broken.
    • Q: Need to sort out deploying it in the grid. A: Perhaps right
  • Scripts
    • @Figure out omero_Scripts_ice question
    • Will make sure it works again (a la Beta3), and can be rolled out as it stands.
    • Would also like to rollout a ROI batch stuff if possible.
    • With Gateway, CellProfiler & one other matlab application working.

• WebAdmin

  • Generally runs, is on mage.
  • Upgrade, create users/groups.
  • The most important functionality.
  • @Ola will commit under components/tools