[ome-devel] OMERO.features API development

[Simon Li]

Some notes from our meeting yesterday:
http://www.openmicroscopy.org/site/community/minutes/minigroup/omero-features-meetings/2013-11-06-omero-features-google-hangout

Summary:
We're thinking of representing features as a 2D array, with metadata stored as key-value maps attached to the array, or individual columns or rows. These keys could describe things such as the feature name (column), sample metadata (row), algorithm parameters, calculation pipelines, etc.

This should work as an OMERO API- in order to retrieve features you'd pass in a set of key-value pairs, for instance to specify which features you want and which images/ROIs etc, and OMERO would handle the logic and return the feature table(s) matching those parameters. Since everyone has different requirements the keys could be anything, however we're trying to define a small set of standard keys- any suggestions are very welcome.

Outside of OMERO we still need a format for transporting features, so we're thinking some form of HDF5.

Simon


The University of Dundee is a registered Scottish Charity, No: SC015096