Electronic Labbook

[dzmacdonald]

• The user should be able to define their experiment on a per project, dataset and image basis.
• The user (P.I.) should be able to define a standard format for the experiments performed in their lab.
• users should be able to search by experiment details
• users should be able to link to other ontologies.

[jmoore]

Discussion:

1. What is an <experiment/>?
   • What/how is it defined? (minimum description.)
2. Where is it stored?
   • What is stored? (Binary attachments, XLS,...)
3. Client implementations (interaction) or do it ourself.
   • Eclipse RCP for Shoola <--> Protege
   • Catalyzer talks to Omero?
   • We are the widget GUI?
4. Import things from other labbooks?
   • Does that suffice? (No editor.)

RDF

Pros

• Lucene
• Sparql (or no sparql and only Lucene?)
• Protege (good community.)
• Linking to other ontologies

Cons

• Security
• Performance
• No FKs to Omero DB

Self

Pros

• Choice:
  • Possibly write no mask builder.
  • Possibly use EMF/ecore.
  • XSD->XSLT->XUL

Cons

• Simple (only enums, radio boxes, fields)

[jburel]

closing