2006-01-26 B,B,D,C

Agenda

• Review of last week's notes/issues
  • Updates to Data Model; need to finalise (JRS/JMB, others?)
  • What did Jason forget to send?
• Week-in-review
  • Baltimore
  • Boston
  • Dundee
    • Grant items (JRS)
      • Updating OMERO and Shoola Docs
      • Collaborations?
    • Josh
      • Discussion: Need to add group column. Should we encapsulate details? (See Omero Object Model for an intro into the problem.)
      • Status/Timeline/Illness Etc.
• Week-to-come
• And as always, WhoNeedsWhatFromWhomByWhen

Notes

• User Access Features for the Client: Jean-Marie has something working, still have a conversation pending with Jason about it.
• Jean-Marie and Donald are working on the documents for Shoola (this will include some 'New Developers' introduction documents)
• Brian and Chris finishing up Resurrect (OMERO2->OMERO3 transformation tool) this week, starting rendering engine Friday/next week.
• Developers note: Josh is going to be adding the new access control model to the database soon. (Basically ok'd).
• Word of the day: ossify (to become or change into bone or bony tissue).
• The time line for getting the demo ready by the end of February should be on track (pending Jason's requirement for documentation time).

Action Items

• Still need a conversation between Jason, Jean-Marie, and Josh to deal with user access features in the client (may need to be expanded to a few other things as well).
• Chris + Brian are making a 'list' of data model fields that are no longer needed or need to be added.
• Chris is going to write the pixel converter for resurrect this weekend.
• Josh is going to document the "three commandments" for saving data to the OME3 database.
• Jason lets Josh know what's needed in the way of Omero doc.
• Josh will get the callback functions Brian & Chris need for rendering ready for early next week.