[ome-devel] Fiji OMERO access from non default group.

[Dominik Lindner (Staff)]

Hi again,

just as I wanted to add the previously mentioned code to the Java Gateway
I discovered, that exactly this method is actually already there:
https://downloads.openmicroscopy.org/omero/5.4.10/api/omero/gateway/facility/BrowseFacility.html#findObject-omero.gateway.SecurityContext-java.lang.Class-long-boolean-

You just pass the model class, e.g. ImageData.class, the object ID and
'true' for the 'allGroups' parameter. But the same remark still holds here:
It will return the object, but it will be shallow loaded, e.g if you load a
Project with this method, methods like "getDatasets" won't work on it,
because it's not fully initialized.

Regards,
Dominik

On 10 May 2019, at 12:02, Ian Dobbie <ian.dobbie at bioch.ox.ac.uk<mailto:ian.dobbie at bioch.ox.ac.uk>> wrote:

Hi,

Not sure if this should be in Devel or users list, sorry if it is in the
wrong place.


I have a script that accesses images from OMERO in Fiji from a dataset,
defined by the datasetID. If this data is in your default group this
works fine. If it is in another group, which you are a member of, then
this fails unless you also call

SecurityContext(group_id)

I have the data ImageID and am able to access the image but my code
fails unless I set the correct security context. Is there any way to
automatically find the correct Security Context to remove the need to
find the correct groupID manually before running the code?


As an additional point is there a central repository for user generated
Fiji (imageJ) scripts to automate analysis of data?


Thanks,

Ian
_______________________________________________
ome-devel mailing list
ome-devel at lists.openmicroscopy.org.uk<mailto:ome-devel at lists.openmicroscopy.org.uk>
https://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel


The University of Dundee is a registered Scottish Charity, No: SC015096
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20190515/40b389c1/attachment.html>