Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2061

Improve Advanced Search usability

    Details

    • Type: Task
    • Status: To-Do (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      The Advanced Search tab enables users to search for items based on Properties, Name, and so on. This is a super great feature!

      However, there are some confusing aspects of how this is currently implemented. For example, if you don't enter any search string and run one of the keyword-style searches, everything currently in memory is returned, but only for items that have the property being searched. (Previously a Java exception was thrown - the exception is fixed in IGBF-2011.) This "return everything" behavior does not happen with the residues search, however. In that case, a dialog appears informing the user that the nothing was entered.

      This is not a great behavior, either. To proceed, the user has to click the "close" button on the dialog, which interrupts flow.

      Idea for improvement:

      The table where search results appear contains nothing if a search has failed or has not yet been run. This area would be the perfect place to show some sort of feedback message to the user letting them know if there was a problem with their search. Instead showing a dialog in a separate window, we could show the message there instead.

      I think this would improve the user experience a lot because it would save a click and would not be quite so jarring. It's good design (in my view) to encourage users to explore and try out different things, particularly with a complex, feature-rich application such as IGB. Showing a new dialog that requires a click to close each time the user makes a "mistake" discourages exploration of the UI.

      Another issue:

      In any of the searches, if you enter a * (asterisk) character, which usually means "match anything and everything", a cryptic error message about regular expressions appears in a new dialog. To proceed, the user has to click the "close" button on the dialog.

      It is a great idea to give users feedback to let them know how their action has affected the system. But it is not a good idea to distract them from the task at hand by showing popups.

        Attachments

          Issue Links

            Activity

            ann.loraine Ann Loraine created issue -
            ann.loraine Ann Loraine made changes -
            Field Original Value New Value
            Epic Link IGBF-1765 [ 17855 ]
            ann.loraine Ann Loraine made changes -
            Link This issue relates to IGBF-2011 [ IGBF-2011 ]
            ann.loraine Ann Loraine made changes -
            Sprint Fall 5 : 14 Oct to 25 Oct [ 76 ] Fall 6 : 28 Oct to 8 Nov [ 77 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            ann.loraine Ann Loraine made changes -
            Workflow Fall 2019 Workflow Update [ 20818 ] Revised Fall 2019 Workflow Update [ 21135 ]
            Status Open [ 1 ] In Progress [ 3 ]
            ann.loraine Ann Loraine made changes -
            Description The Advanced Search tab enables users to search for items based on Properties, Name, and so on. This is a super great feature!

            However, there are some confusing aspects of how this is currently implemented. For example, if you don't enter any search string and run one of the keyword-style searches, everything currently in memory is returned, but only for items that have the property being searched. (Previously a Java exception was thrown - the exception is fixed in IGBF-2011.) This "return everything" behavior does not happen with the residues search, however. In that case, a dialog appears informing the user that the nothing was entered.

            This is not a great behavior, either. To proceed, the user has to click the "close" button on the dialog, which interrupts flow.

            Idea for improvement:

            The table where search results appear contains nothing if a search has failed or has not yet been run. This area would be the perfect place to show some sort of feedback message to the user letting them know if there was a problem with their search. Instead showing a dialog in a separate window, we could show the message there instead.

            I think this would improve the user experience a lot because it would save a click and would not be quite so jarring. It's good design (in my view) to encourage users to explore and try out different things, particularly with a complex, feature-rich application such as IGB. Showing a new dialog that requires a click to close each time the user makes a "mistake" discourages exploration of the UI.

            An analogous situation: you invite friends to stay with you at your home. When they arrive, you say "look around - pick a room to stay in." However, rooms that are already taken are locked. If your newly arrived friends try to open one the door to a room that is already claimed, a loud recording that repeats "This room is taken, try again!" starts to play. To turn it off, they have to walk down the hall and press an "off" button.

            Another issue:

            In any of the searches, if you enter a * (asterisk) character, which usually means "match anything and everything", a cryptic error message about regular expressions appears in a new dialog. To proceed, the user has to click the "close" button on the dialog.

            It is a great idea to give users feedback to let them know how their action has affected the system. But it is not a good idea to distract them from the task at hand by showing popups.
            The Advanced Search tab enables users to search for items based on Properties, Name, and so on. This is a super great feature!

            However, there are some confusing aspects of how this is currently implemented. For example, if you don't enter any search string and run one of the keyword-style searches, everything currently in memory is returned, but only for items that have the property being searched. (Previously a Java exception was thrown - the exception is fixed in IGBF-2011.) This "return everything" behavior does not happen with the residues search, however. In that case, a dialog appears informing the user that the nothing was entered.

            This is not a great behavior, either. To proceed, the user has to click the "close" button on the dialog, which interrupts flow.

            Idea for improvement:

            The table where search results appear contains nothing if a search has failed or has not yet been run. This area would be the perfect place to show some sort of feedback message to the user letting them know if there was a problem with their search. Instead showing a dialog in a separate window, we could show the message there instead.

            I think this would improve the user experience a lot because it would save a click and would not be quite so jarring. It's good design (in my view) to encourage users to explore and try out different things, particularly with a complex, feature-rich application such as IGB. Showing a new dialog that requires a click to close each time the user makes a "mistake" discourages exploration of the UI.

            Another issue:

            In any of the searches, if you enter a * (asterisk) character, which usually means "match anything and everything", a cryptic error message about regular expressions appears in a new dialog. To proceed, the user has to click the "close" button on the dialog.

            It is a great idea to give users feedback to let them know how their action has affected the system. But it is not a good idea to distract them from the task at hand by showing popups.
            ann.loraine Ann Loraine made changes -
            Status In Progress [ 3 ] To-Do [ 10305 ]
            ann.loraine Ann Loraine made changes -
            Sprint Fall 6 : 28 Oct to 8 Nov [ 77 ] Fall 9 : 9 Dec to 20 Dec [ 80 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to IGBF-21 [ IGBF-21 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to DB-131 [ DB-131 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to DB-100 [ DB-100 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to DB-182 [ DB-182 ]
            nfreese Nowlan Freese made changes -
            Link This issue relates to IGBF-1096 [ IGBF-1096 ]
            Hide
            nfreese Nowlan Freese added a comment -

            While investigating an issue with advanced search, I found several issues in the deep backlog that are still present in 9.1.0. I have linked the issues to this issue.

            Show
            nfreese Nowlan Freese added a comment - While investigating an issue with advanced search, I found several issues in the deep backlog that are still present in 9.1.0. I have linked the issues to this issue.
            ann.loraine Ann Loraine made changes -
            Sprint Fall 9 : 9 Dec to 20 Dec [ 80 ]
            ann.loraine Ann Loraine made changes -
            Rank Ranked higher
            ann.loraine Ann Loraine made changes -
            Assignee Ann Loraine [ aloraine ]
            ann.loraine Ann Loraine made changes -
            Labels Advanced

              People

              • Assignee:
                Unassigned
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: