OMERO.editor Where next - PowerPoint PPT Presentation

1 / 12
About This Presentation
Title:

OMERO.editor Where next

Description:

To record a complete description of the experiment. ... Semantic wiki is an overkill? Could use markup to identify parameters. Save as html / database? ... – PowerPoint PPT presentation

Number of Views:53
Avg rating:3.0/5.0
Slides: 13
Provided by: LifeSc4
Category:
Tags: omero | editor | next | overkill

less

Transcript and Presenter's Notes

Title: OMERO.editor Where next


1
OMERO.editorWhere next?
  • (After Beta3)

2
Goal of Editor? (1)
  • To record a complete description of the
    experiment. Like a lab notebook that someone else
    can understand! (Not just the protocol
    description)?

Fix and Stain Cells Prepare formaldehyde by
dissolving 1.85g powder in 10mls PBS. Warm in
fume cupboard till solution is clear. Filter
through 0.2uM filter. This is 37 solution
Lab note-book
Word documents, Spreadsheets etc
Web sites http//lamondlab.com/f7immunostainprotoc
ol.htm
3
Goal of Editor? (2)
  • To make a nice UI for viewing protocols (text /
    tables etc) within insight?

4
Goal of Editor? (3)
  • To develop a data-model for an experiment or at
    least a format for recording an experiment?
  • Eg usefulchem(wiki)
  • Experiment
  • Objective
  • Procedure
  • Results
  • Discussion
  • Conclusion

e.g. MAGE-TAB
5
Goal of Editor? (4)
  • To be an electronic lab notebook? (The experiment
    is the home, link to the data)

UsefulChem http//usefulchem.wikispaces.com/ Chem
Tools http//chemtools.chem.soton.ac.uk/projects/b
log/ eCAT http//www.axiope.com
6
What Editor does now(Should it continue to do
these?)
  • Separates Experimental variables from Protocol
    description
  • Clear fields, load defaults etc.
  • Easy to view the important metadata
  • Hierarchy
  • Simple data types (Text, number, table, date,
    time, link, image, Ontology term, checkbox,
    drop-down menu)

7
Problems
  • Protocols and Experiments in Editor dont look
    like biologists expect Experimental variables
    not in context.
  • Editor files not nicely displayed by other
    software.
  • Editor files not understood by other software.

Which of these should I aim to solve? Solving any
of these requires a change in OMERO.editor file
format
8
File Format Options?
  • MAGE-TAB
  • Protocols with parameters
  • Software can understand format (although
    protocols are free-text)
  • Easy to edit in other software (Excel)
  • Other reasons for using Tabs are not applicable
    to OMERO.editor
  • MAGE-TAB document consists of several TAB files
    1 for protocols, the others describe microarray
    set-up and workflow.
  • Wiki / semantic wiki
  • Semantic wiki is an overkill?
  • Could use markup to identify parameters.
  • Save as html / database?

9
File Format Options?
  • XML
  • This is current format.
  • Can include other XML with no changes.
  • Difficult to read without OMERO.editor
  • Reading imported XML is dependent on the format
    of the XML. Some easy (eg OME-XML), most are much
    harder (eg GelML, MAGE-ML etc).

GelML in OMERO.editor
10
File Format Options?
  • XHTML
  • All the advantages of XML, but can be displayed
    by any browser.
  • Can place parameters in context within text.
  • Supports tables, hierarchy etc.

11
Mapping MAGE-TAB to editor/XML
12
(No Transcript)
Write a Comment
User Comments (0)
About PowerShow.com