Skip to content
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

Rework plate naming priorities so that reader-supplied names can be used #2

Open
wants to merge 2 commits into
base: dev_5_2
Choose a base branch
from

Conversation

melissalinkert
Copy link
Member

This is one attempt at resolving the long-standing issue of reader-supplied plate names being overwritten by the name of the imported file (which is set as the user specified name). The default names appear to come from ome.formats.importer.ImportFixture, but changes were not made there so as to not affect non-SPW imports.

Changes here were written and tested in the context of Harmony work, but all plate imports will be impacted. I would expect bin/omero import -n TestPlateName Images/Index.idx.xml to result in the same plate name (TestPlateName) with and without this change. bin/omero import Images/Index.idx.xml results in a plate named Index.idx.xml without this, and should result in a plate named according to the Name tag under Plate in the Index.idx.xml file.

The user specified name is typically non-null, even if the user did not
explicitly enter a plate name.  This attempts to distinguish between
"real" user specified names and default names based upon the imported
file name.

The default names appear to come from
ome.formats.importer.ImportFixture, but changes were not made there so
as to not affect non-SPW imports.
@melissalinkert
Copy link
Member Author

See also discussion here: ome/design#57

This removes the automatic setting of user-specified names in the
importer, so that later calls to retrieve the user-specified name are
guaranteed to return only what the user actually specified (or null by
default).  Plate and Image names supplied by the reader are trusted when
the user has not specified a name.  The name(s) will be set to the
relative path of the imported file only if both the user- and
reader-specified names are null.

The issue of 255 character limits on name fields has not been addressed
here, but a comment has been added so that it's easier to go back to
later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant