<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Adrian,<div><br></div><div> Thanks for your feedback. </div><div><br></div><div>You're asking about a tricky issue that's taken a bit of discussion and various different solutions.</div><div><br></div><div>Originally, in the very first implementation of the OMERO.editor, I did exactly as you've suggested and kept 'protocol' files and 'experiment' files separate.</div><div><br></div><div>The trouble is keeping them in sync:</div><div> - It's difficult to ensure that you always have the Protocol file for a given Experiment. (not deleted, renamed lost etc)</div><div> - You have to be sure that the Protocol hasn't been modified at all. Has to be "locked" as soon as you create an Experiment. Very tricky to "unlock" in the future because you'd have to keep track of (and update) all the Experiments that came from it.</div><div><br></div><div>Also, at least when I was testing it with users here, I found that they didn't really re-use a Protocol very much. There was always a small change they wanted to make that was outside of the experimental parameters they'd defined. I tried to minimise the need for this by adding "notes" to each step, but it was still a problem.</div><div><br></div><div>This will obviously vary depending on the type of experiments you're doing. E.g. high throughput techniques, or a lab where you're doing very similar experiments all the time might not need to change the Protocol very often.</div><div>It would also give you a lot more querying / searching power if you knew you had a lot of Experiments that used exactly the same Protocol (E.g. search by parameters etc).</div><div>If you were working on the server (not standalone Editor), you could store the values themselves in HDF tables, with columns defined by a Protocol's parameters.</div><div><br></div><div>This is analogous to the ISA-TAB format: <a href="http://isatab.sourceforge.net/format.html">http://isatab.sourceforge.net/format.html</a></div><div>Unfortunately we don't have the resources / funding to take the Editor in this direction at the moment.</div><div><br></div><div>NB: It is possible to build a custom search indexer for OMERO.editor files <a href="http://www.openmicroscopy.org/community/viewtopic.php?f=6&t=553">http://www.openmicroscopy.org/community/viewtopic.php?f=6&t=553</a> to help with querying them.</div><div><br></div><div><br></div><div> Regards,</div><div><br></div><div> Will. </div><div><br></div><div><br></div><div><br><div><div>On 25 Mar 2013, at 14:00, Adrian Jacobson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Dear OMERO developers,<br><br>The OMERO.editor is a great feature, but it might make sense to reduce the amount of information in the XML files of experiments.<br>Currently OMERO stores the content of the corresponding protocol plus the values for the variables within it in the experiment XML files. This is redundant, because one already possesses the protocol.<br>It might be more elegant to store just the value of the variables in an experiment in the corresponding XML file.<br><br>Regards,<br>Adrian<br>_______________________________________________<br>ome-devel mailing list<br><a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br>http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel<br></div></blockquote></div><br></div></body></html>