Open joshmoore opened 1 month ago
Hello, @joshmoore . I am glad to receive your message and have tagged it :) Thank you.
This repository was created to gather and include some acquisition data that does not seem to be included when packing/unpacking with omero-cli-transfer. For example, if you look at this page: https://github.com/Qureator/omero-acquisition-transfer/blob/master/omero_acquisition_transfer/transfer/pack/exports/instrument.py, you will see that items like objectives or imaging environments fall into this category.
These codes may not be suitable for the latest omero-cli-transfer GitHub repository, especially since the ome-types version. (I am considering updating it when I have time.) We are using this from the omero-cli-transfer forked in our Qureator account.
We often use pack/unpack to transfer files between different servers and created this repository because we didn't want to lose important information if possible. Does this explanation make sense?
I am glad to receive your message and have tagged it :) Thank you.
:+1:
We are using this from the omero-cli-transfer forked in our Qureator account.
Ah, I understand. Let me take a look at that then. Thanks for the pointer. It might be that the plugin interface in https://github.com/ome/omero-cli-transfer/pull/73 (or something similar) would allow us to put all of these pieces together.
Hi @eyshin05 et al.. I've just run across this project. When/if you are interested, you might add a GitHub topic like
#omero-import
so people can find it. (You can find an example under https://github.com/Laura190/OMEROimport/issues/1)While I'm here and if you have a moment, can you explain how you see the relationship between this project and omero-cli-transfer?