Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #3481 (closed)

Opened 13 years ago

Closed 12 years ago

User feedback session Johan 22/11/10

Reported by: saloynton Owned by: saloynton
Priority: minor Milestone: Unscheduled
Component: Usability Keywords: n.a.
Cc: jburel Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by saloynton)

A summary of the discussion with Johan (see Scientists Anonymisation list for name conversion)

1) Importer part of Insight
There was an initial question on when the importer will be part of insight.

J-M: for initial work see #3415. Will Johan be a good candidate to test it?

Scott: Confirmed with Johan and he is happy to help give feedback with the importer opened ticket #3584 for the next phase of feedback.

2) Click efficiency
There are 6 mouse click's required for the exporting of an image. The example scenario given was exporting 5 images in a panorama for a power point. In this scenario every image requires 6 clicks from the image selection to the confirmation In an ideal situation he would like to be able to make 3 clicks select the images > export > save.

This problem is exacerbated in two ways firstly as the information that is typed in about the save location is not saved between each action. So OMERO does not remember what was last done, this would be helpful across a range of different tasks for working in OMERO. And secondly with the addition of the confirmation boxes, could the confirmation be displayed within the data manger in the bottom left corner. Then there would only be a need to display the box when there is a problem.

J-M: Selection in thumbnail view will require some significant work. The Save dialog should offer the ability
to mark the folder as default. If not, require a ticket.

Requirement and user story opened for this: #4640

3) Viewing multiple Image metadata

The scenario was discussed with Johan when he was wanting to view the same element of metadata about multiple images i.e. exposure time. The workflow of moving between images creates extra steps as the view of the metadata returns to the default view on each occasion. The scientist work is quite specific to this problem as he does a lot of cross comparison of images and image metadata.

To demonstrate the use of the feature further the scientist showed how this worked with Adobe Bridge. This allowed the image metadata to be selected and then when selecting on other images the same metadata was remembered and displayed. Adobe bridge has some very interesting filters on the image metadata and the way it is presented. This might be worth some further investigation for possible ideas of how existing systems work for filtering data.

J-M: see comment above

4) - Some level of Automation in assigning ROI

The scientist was doing a lot of repetitive work and was very keen to have some level of automation with ROI. His work was in cell selection so being able to select cells and grow a ROI circle relative to the background was the ideal way he would like to be working. He also mentioned this would help reduce the issue of introducing a bias in the image analysis.

A help file within the ROI would be valuable as spent some time trying to pick up and use the tool. The one that was not completely obvious was the double click feature on Windows with the point-to-point tool. (I have sent Johan the link to the OMERO video's and documents to help with this in the future)

J-M: ROI and Measurement tool will be reviewed when we do the Analysis package. We can start making tickets.

4.1 Presentation of data in the ROI tool

In selecting a collection of ROI (this was done using the point to point tool) the problem faced by the scientist is that the data/information within the ROI is available but the way and where the information is within the ROI can make the workflow more difficult. The example discussed was how the scientist may want information on the centre and area of the ROI but this is separate from intensities.

The ideal scenario discussed with the scientist was to have the ROI and then the stain with all the information associated with that (i.e. including area and centre) then the second stain with all the information grouped together etc. The key point discussed was that he found the ROI tool very useful but required the information grouping to reflect how he was working with the ROI data more closely.

The information coming from the ROI tool is important for the scientist work in the way it must be suitably prepared in order to be viewed within excel. (Johan was having problems with insight crashing when exporting data to excel)

J-M: See comment above.

5) Use of shift in workspace – selecting multiple images

When using the workspace the clicking of shift to select a group of image does not behave in the same way as the file hierarchies. The shift key behaves in the same way as ctrl. The scientist found this frustrating, as he wanted to be able to select his images in the workspace.

J-M: See comment above.

6) Batch Image Export

Johan would like the ability to export a batch of images in the same way you are able to export the image in the image viewer. He was exporting many images and so having the ability batch export would help save him a lot of time. Johan would wish to have the same options as provided in the image viewer of selecting image type and the same selection on file format.

J-M: a very limited number of actions can be done so far.

Change History (5)

comment:1 Changed 13 years ago by jburel

  • Summary changed from User feedback session to User feedback session Johan 22/11/10

comment:2 Changed 13 years ago by jburel

  • Description modified (diff)

comment:3 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:4 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:5 Changed 12 years ago by jburel

  • Resolution set to fixed
  • Status changed from new to closed

information about roi moved to #6263 and #6264.
The rest is already covered.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67958 sec.)

We're Hiring!