Dear Susanne,
The annotations have to be added as if they were by the data owner. There are a few ways I might try this:
- OMERO.cli's "login" offers a --sudo option that an administrator can use to create an OMERO session as if they were another user. Rather than username/password, one could then use that same new session ID to log in to a graphical client as that data owner.
- A Java or Python script can use the same approach that the --sudo option's implementation uses. It is probably how Insight does "import as". Our restricted administrator integration tests in Java extensively attempt such sudo'ing to assure that it does not afford a means to circumvent the privilege restrictions.
- When using the update service to save new objects as an administrator (e.g., an annotation link and its new annotation child), set the objects' details.owner property to the desired data owner before saving.
If any of the above sound appealing and you need help with the details of making them work then please do feel free to ask, we are happy to dig up related code or help with scripting, depending on what fits best with your work. There may also be some other viable approach.
Cheers,
Mark
