Closed joshmoore closed 8 months ago
Do you see this more of a problem with cli-transfer versioning or OMERO versioning?
I don't really have a good answer to this - there's no easy way to ensure full version compatibility on the cli-transfer side of things (in particular, I'm thinking about the transition from using CommentAnnotation
s to XMLAnnotation
s). I think future transitions become easier - we can version schemas for the XMLAnnotation
s and the OME data model, so it's less of a big deal. But yeah - any thoughts welcome.
I don't think of it as an OMERO versioning problem, at least as far as OMERO doesn't have a "versioned export format". transfer is basically becoming an "export" format, so the question will be: is it versioned? Options that we've touched on:
for the last point, sub-options I can think of include:
I think the third option is very feasible for everything after 1.0: either sub-option is pretty ok if we have ome-types for almost all of it and versioned schemas for the things that are not there. I think continuing support for pre-1.0 packs is a losing proposition, to be honest - a world where we have
MSTM
During the presentation yesterday of a POC to the iRODS imaging WG meeting, I realized in a slow-mo sort of way, that if this script is the beginning of using
omero transfer
for archiving data (e.g., to iRODS) that the versioning issue is back on the table, i.e.:A
has omero-transfer v1 installedB
to iRODS asC.tar
B
C.tar
either:D
with a different versionA
after some upgrades