<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">I can confirm that Ice definitely works on Android as I've used Mumble on my Android phone no problem.</span><div class="" style="font-family:arial,sans-serif;font-size:13px">
</div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Douglas</span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 18 November 2013 20:21, Josh Moore <span dir="ltr"><<a href="mailto:josh@glencoesoftware.com" target="_blank">josh@glencoesoftware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Johan,<br>
<div class="im"><br>
On Nov 15, 2013, at 2:22 PM, Johan Henriksson wrote:<br>
<br>
>>> Finally: How are the LSIDs for images coming along? Have they actually<br>
>>> adopted?<br>
>><br>
>> How do you mean? In having them automatically resolve as was the original<br>
>> intent of the LSID spec? Not at all. We nor anyone we know of is running<br>
>> such a service. Neverthwless we still do use LSIDs as core identifiers.<br>
>><br>
><br>
> I was rather thinking about how new images obtaining LSIDs, and is it then<br>
> done within OMERO or is it at the microscope? Here you have to excuse my<br>
> very naive knowledge about LSIDs. I see from<br>
> <a href="http://www.openmicroscopy.org/site/support/ome-model/developers/id-and-lsid.htmlthat" target="_blank">http://www.openmicroscopy.org/site/support/ome-model/developers/id-and-lsid.htmlthat</a><br>
> assigning project LSIDs directly could be fairly easy but I don't<br>
> recall that I ever entered an ID when installing OMERO(?)<br>
<br>
</div>OMERO internally assigns LSIDs on import and export, allowing you to link data from<br>
one instance back to its source. The mechanisms are in place for supporting third-party<br>
LSIDs but this is not turned on, primarily because no one generates them. If you are<br>
interested in doing this at the scopes, please let us know.<br>
<div class="im"><br>
<br>
> I was otherwise figuring, if the LSIDs are not widely assigned to images<br>
> right now, and if we want to push LSIDs, maybe one could autogenerate them<br>
> in OMERO as the hash of the original file + timestamp. Or something along<br>
> this style. Resolving the LSIDs somehow appears easier than getting them in<br>
> use (technical problem vs social/political problem)<br>
<br>
</div>The current implementation is to use the primary key of the object hashed with a<br>
UUID for the OMERO instance, though that could likely be made flexible.<br>
<br>
Cheers,<br>
~Josh<br>
<div class="HOEnZb"><div class="h5"><br>
> /Johan<br>
>><br>
>><br>
>>> cheers,<br>
>>> Johan<br>
>><br>
>> Regards,<br>
>> ~Josh.<br>
<br>
_______________________________________________<br>
ome-devel mailing list<br>
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk">ome-devel@lists.openmicroscopy.org.uk</a><br>
<a href="http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel" target="_blank">http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel</a><br>
</div></div></blockquote></div><br></div>