-
Notifications
You must be signed in to change notification settings - Fork 103
OMERO5DEV__3: fileset image linkage #951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Primarily concerned with fixing the graph specifications for delete, etc in spec.xml and handling the linkage from and to Image.
|
Tested with import, chgrp and delete on images and plates. Direct feedback to @joshmoore resulting in two most recent commits. May need more testing? |
|
@pwalczysko / @jburel : the remaining issue as I understood it was chgrp of plate. This was likely broken before this PR, no? |
|
@joshmoore Certainly does not seem to work with today's build (develop) on Gretzky. See below |
|
In that case I'm happy for the PR to be merged if chgrp of Plate it outwith this PR. |
|
@pwalczysko, sorry, I meant before this PR was opened. |
|
@joshmoore: change group for plate did not work prior to the PR. |
|
@jburel: thanks. @chris-allan said he would do without the upgrade script. Ok to merge? |
OMERO5DEV__3: fileset image linkage

As discussed recently, all images should link directly to
the Fileset that created them (or null if synthetic). Plate
no longer has a direct link to the Image, which simplies
several queries.
Import should continue to work and delete and chgrp for
images/filesets should all still work with the same
caveats for all multi-file images as previously.
Note: fstest/model.py still needs minor changes but
that conflicts with gh-941.