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

Disable companion attachments (Fix #12519) #3384

Merged
merged 1 commit into from Mar 4, 2015

Conversation

joshmoore
Copy link
Member

Annotations with namespace NSCOMPANIONFILE are no
longer needed since all the files in a single fileset
are grouped in the database and are parseable via
Bio-Formats. Clients can continue looking for old
companion annotations but no assumption should be
made that all images will have them.

--no-rebase

Annotations with namespace NSCOMPANIONFILE are no
longer needed since all the files in a single fileset
are grouped in the database and are parseable via
Bio-Formats. Clients can continue looking for old
companion annotations but no assumption should be
made that all images will have them.
@jburel jburel added the develop label Jan 23, 2015
@mtbc
Copy link
Member

mtbc commented Jan 26, 2015

Well, this certainly seems to work fine. It does seem to mean that in the client I don't see a list of companion files any more; that's okay / expected?

@joshmoore
Copy link
Member Author

@mtbc : in which location? We might need to update a query to support that. /cc @jburel @dominikl @will-moore

@mtbc
Copy link
Member

mtbc commented Jan 28, 2015

It's over in the metadata panel on the right, maybe under the acquisition tab?

@jburel
Copy link
Member

jburel commented Jan 28, 2015

Acquisition tab that's where they are displayed if any. I will have to review the annotation count (on-going issue)

@joshmoore
Copy link
Member Author

@jburel : let me know if you want me to track down what queries are currently being made.

@jburel
Copy link
Member

jburel commented Feb 13, 2015

I will have a look at that next.

@joshmoore
Copy link
Member Author

@jburel : do you want me or someone else to look into something here?

@joshmoore
Copy link
Member Author

@jburel : ping. Still planning on this for 5.1.0?

@jburel
Copy link
Member

jburel commented Mar 3, 2015

will work on it now that i have the imagej out of the way

@jburel
Copy link
Member

jburel commented Mar 4, 2015

There is no assumptions that the image will have it since it was not the case prior to FS, i.e. only certain file format will have a companion file e.g. DV.
Checked web and insight, no error noticed.

An example: trout user-1 project: 5.0 data dataset leica-original, the image in dataset will have a companion file
The images in alexandra won't

@joshmoore
Copy link
Member Author

i.e. we should have these into the testing plan for 5.1.0?

@jburel
Copy link
Member

jburel commented Mar 4, 2015

It won't hurt to have it check.
The thing to test is:

  • Import file like lei or a dv with a companion file and check the display
  • compare with previously imported file of similar type

cc @pwalczysko

@jburel
Copy link
Member

jburel commented Mar 4, 2015

Just imported a file so it is no longer possible to view the log of a DV. This could be a surprise for user so we will have to handle that case cc @will-moore @gusferguson @pwalczysko

@pwalczysko
Copy link
Member

Works fine with dv. New display really does not have companion file, but no problems with the file detected.

@joshmoore
Copy link
Member Author

So an RFE re: displaying logs based on the fileset? Anything else?

@jburel
Copy link
Member

jburel commented Mar 4, 2015

that should be it. not a blocker for that PR since we can have access to the log file when the user downloads the image.

@joshmoore
Copy link
Member Author

Jotted down the namespace for 5.2 cleanup. Merging.

joshmoore added a commit that referenced this pull request Mar 4, 2015
Disable companion attachments (Fix #12519)
@joshmoore joshmoore merged commit e944f88 into ome:develop Mar 4, 2015
@joshmoore joshmoore deleted the no-companion-anns branch March 4, 2015 16:05
@sbesson sbesson added this to the 5.1.0-m5 milestone Mar 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants