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"

Task #3926 (closed)

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

2nd round of User feedback On Importer in Insight - Keria

Reported by: saloynton Owned by: saloynton
Priority: minor Milestone: OMERO-Beta4.3
Component: Usability Version: n.a.
Keywords: n.a. Cc: jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2011-01-27 (4)

Description (last modified by jburel)

A follow up meeting has been arranged with Keria for friday 21 jan. To demo the changes made in the importer workflow raised in first review documented in ticket 3584.

Feedback 21 January Keria

The purpose of the session was to demo the changes made from the last preview of the importer within insight.

There was generally a lot of positive feedback particularly on the following areas of change:

  • The improvements in providing the import panel was liked.
  • The change in the use of tags between imports.
  • The option to turn off thumbnails to reduce the slow down in importing.


Problems experienced

  • Import Error (see #3958)

There was an error on selecting a file from the LMF file structure this was reported in the feedback. It was seen after that the password for LMF had been changed.

The first import completed in the session led to the loss of the imported dataset. There action taken was the import of a project on completion of the import had no link to the images imported. The refresh icon in this instance was indicated on Keria’s name in the tree.

  • Import selection process (see #3960)

There is still some confusion with the clarity of selection and importing. This was discussed to come down to the selection of project/dataset before import.

The scenario discussed to help clarify the workflow was to provide the drop down boxes of project and dataset within the import panel. This is to provide the information/confirmation of where the imported information will go. If the information is not in the expected place for the import it can be corrected. If the information for the import is correct it would not add an additional step to the import use.
'
The new import workflow may come down to a user learning curve – as once the workflow of selecting the images into the dataset this could become the standard practice for them. However there will need to be the allowance for a dual workflow to cater for both.

  • Selection of DV file types

The selection of the specific DV file format option is a big miss for Keria. Her argument for continuing to support this was that the option of selecting out the specific files amongst in the folder is a big time saver when importing a large collection of files.

Last point needs to be discussed, to specific: only suitable for some local users.

Change History (5)

comment:1 Changed 13 years ago by saloynton

  • Summary changed from 2nd round of User feedback On Importer in Insight to 2nd round of User feedback On Importer in Insight - Keria

comment:2 Changed 13 years ago by saloynton

  • Status changed from new to accepted

comment:3 Changed 13 years ago by saloynton

  • Description modified (diff)

comment:4 Changed 13 years ago by saloynton

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

comment:5 Changed 13 years ago by jburel

  • Description modified (diff)
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.67566 sec.)

We're Hiring!