talking wiith @pwalczysko, he pointed out to me that my creativity lead me into the cracks between intended use cases
In our application we end up having the same slide-scanner images multiple times with different annotations and image descriptions (the perks of a bi-lingual university).
So after importing the data once for one language, script runs through the project-dataset-image tree, retrieves the image path and imports them with
--transfer ln_s again in a second project.
Now, on reading the documentation again, it sais:
With in-place import, the data either resides completely outside of OMERO or is shared with other users […]
Now Petr pointed out to me that deleting the image that was imported with the
ln_s would lead to the single copy being deleted, given that it is the sole link and OMERO is assuming that the data lies outside of the ManagedRepository.
Here is a suggestion on how to make this more explicit in the documentation.
No to fix this I see the following work coming up:
- copy the data on a safe location in the file system outside the ManagedRepository.
- in place import for the FR and DE version
- copy all the annotations and descriptions from from the originals to the newly imported datasets.
Petr pointed also mentioned that there might be a simpler fix for this. @joshmoore could you tell me more about this?