2007-11-09 Omero Review Meeting
Attending: Alexia, Andrew, Brian, Chris, Donald, Jason, Jean-Marie, Josh, Lars, Melissa, Will
- Beta-2.2
- Tix?
- No tickets left they have all been closed or moved forward
- Anything post-release?
- Nothing
- Shall we release?
- Sounds like we are good to go, will let Jason know to make the announcement.
- Tix?
- Beta 3.0
- General clean-up of tickets (lots of tix have been dropped in Beta3 that are just sitting there; put the ones we won't do in future)
- Can everyone please look through your tickets and see if you need to move things from Beta 3 that should be elsewhere?
- model
- removing the pixels.setDefaultPixels(true) and similar for beta3?
- should improve importance, simplifies some operations, but is a bit of "convention"
- could add methods getDefaultX() and setDefaultX(X x) to make it more explicit
- removing the pixels.setDefaultPixels(true) and similar for beta3?
- server
- Scripting and Analysis-- Final Plan
- compression
- Most of the changes to support variable compression inside the thumbnail service is non-trivial and further discussion is needed to see if it can get done in time for Beta 3
- projections
- Do we want to do the projections real time or have the user make some choices, submit, and create another pixels?
- JM: Might need to do both. This may require a lot of changes in the client to support multiple pixels.
- Do we want to do the projections real time or have the user make some choices, submit, and create another pixels?
- Secure login and LDAP (per Matthieu@Rockefeller-- 'why would I use LDAP-based authentication when passwords are sent in the clear?')
- Already doable.. just needs to be turned on and documented
- Tix? Tickets need to be created for this in Beta 3
- Webadmin
- More use of Data Model?
- Support for OME web UI (functionality, and content, not design)? (We said we would support the OME Server web functionality-- is time to start thinking about that).
- Jason: Lots of options here, but we don't want "feature creep" and a web-based insight.
- Brian: Should we be looking at a web-based "server side" batch importer, or allow the importer client to access remote mounts? Or both?
- Jason: Basic visualization would be a nice web-based feature.. nothing too rich
- Ola: Doesn't want to replace insight, just augment some of its existing features with a web-based implementation
- importer
- Test suite
- This must be top priority!!
- Incell Screen-plate-well support
- Need to have the new XML model supported before we can get this done (this is coming from Curtis)
- Melissa can start looking at "the basics" fairly soon on this.
- Jason: working on Evotech data and will have it delivered to Melissa
- Adding file formats (Ugh!) (We are agreed to slowing down this process, in favor of getting the testing framework implemented)
- HCS file formats (Should we start exercising parts of the SPW data model; we have an excellent use case here with the Incell1000 files. Obviously, we won't support the SPW data in the client yet, but can consider this after the new year. Bio-Formats supports Evotec, shall we add Incell 1000. Also note I have contacted Cellomics twice, no response.)
- Test suite
- insight
- tagging functionality-- definition and implementation
- JM is working this now. We may need a few things brought over from the client to the server and this will need some discussion.
- compression
- Measurement
- Donald and JM have a good plan of what is going to need doing, and should have a first presentation available by Beta 3
- tagging functionality-- definition and implementation
- ProtocolEditor
- Where to next? Need to sort out ideas of incorporating different data models
- Will: Where do we go next with ontologies, what are they going to be used for? What software is going to read them? A lot of the ontologies are in the OBO format, how should we integrate with that?
- Jason: Querying the data annotations is going to be critical and structure and rules are going to have to occur to make the system work.
- Will is going to see if we can use the existing protocol editor features in phenote/obo and integrate it into our stuff.
- Where to next? Need to sort out ideas of incorporating different data models
- Extension to the Hierarchy Viewer
- JM doesn't know yet if this will get done in time for Beta 3
- General clean-up of tickets (lots of tix have been dropped in Beta3 that are just sitting there; put the ones we won't do in future)
- Admin things
- Office furniture come Nov 24.
- Colin Blackburn starts Dec 1.
Action Items
- Josh: Create tickets for LDAP Secure login and gather requirements, etc.
- JM & Ola: Work out some of the new Pojos bulk services.
- Brian & Chris: Work out XML modelling features required for the importing of screen-plate-wells
- Brian get Michael to generate some small incell sample sets for testing
- Jason: working on Evotech data and will have it delivered to Melissa
- Brian: Put together a list for Jason to review