Details

    • Type: Improvement
    • Status: To-Do (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 9.1.8 Major Release
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Winter 6 Mar 8 - Mar 19, Spring 1 2021 Mar 22 - Apr 2, Spring 2 2021 Apr 5 - Apr 16

      Description

      Situation: The Open Genome from File user interface can be improved.

      Task: Improve the Open Genome from File user interface.

      For example:
      1) Genome Version should be below Species to make it more in line with the Species menu.
      2) The placeholder for Species should be changed to something to more accurately reflect the expected input, such as "Genus species"
      3) Change the Genome Version from a text box to a series of dropdowns. The Genome Version in IGB must conform to the following pattern:
      H_sapiens_Dec_2013
      We can obtain the first half by using the Genus species from the Species input. So if the user enters Homo sapiens, we would take the first letter of Homo (H) and then the second word (sapiens), separating them by underscores. We could then have a dropdown for the month (Jan/Feb/Mar/etc...) and then an input for year. We would then use these values to construct the IGB compliant Genome Version.

      1. Completed.jpg
        36 kB
      2. expandDefaultArea.png
        42 kB
      3. openGenomeFromFile.png
        28 kB

        Issue Links

          Activity

          Hide
          rweidenh Rachel Weidenhammer added a comment -

          I spoke with Karthik and it looks like all of the behaviors I observed per my previous comment are normal and intended.

          I have one question I wanted to run by Nowlan Freese,
          So we want to make sure the user doesn't have to deal with a bunch of error messages for optional fields, but on the flip side -
          Isn't it confusing if we forgo giving the user any error feedback when they do something that will result in the software not behaving as expected, like dropping all of their input data without warning?

          Show
          rweidenh Rachel Weidenhammer added a comment - I spoke with Karthik and it looks like all of the behaviors I observed per my previous comment are normal and intended. I have one question I wanted to run by Nowlan Freese , So we want to make sure the user doesn't have to deal with a bunch of error messages for optional fields, but on the flip side - Isn't it confusing if we forgo giving the user any error feedback when they do something that will result in the software not behaving as expected, like dropping all of their input data without warning?
          Hide
          rweidenh Rachel Weidenhammer added a comment -

          Change request Karthik Raveendran:

          1) If all fields are left blank the text should be generated: "Custom Species 1" and "Custom Genome 1" (incrementing the numbers where appropriate) for the Species and Genome Version menus within the Current Genome tab in IGB.

          2) Limit the Year field to number characters, and/or take only the first 4 characters entered.

          Show
          rweidenh Rachel Weidenhammer added a comment - Change request Karthik Raveendran : 1) If all fields are left blank the text should be generated: "Custom Species 1" and "Custom Genome 1" (incrementing the numbers where appropriate) for the Species and Genome Version menus within the Current Genome tab in IGB. 2) Limit the Year field to number characters, and/or take only the first 4 characters entered.
          Hide
          aloraine Ann Loraine added a comment -

          Question for Karthik Raveendran & Rachel Weidenhammer:

          • What do you think of this idea?

          When the user first sees the form, the year and month are already filled in using the current year and month.

          Show
          aloraine Ann Loraine added a comment - Question for Karthik Raveendran & Rachel Weidenhammer : What do you think of this idea? When the user first sees the form, the year and month are already filled in using the current year and month.
          Hide
          karthik Karthik Raveendran added a comment - - edited

          Ann Loraine, If the Month and Year fields are already entered and the user does not enter any other values, then the "Custom Genome 1" format would never appear. It will always be in the format "Genus_Species_Apr_2021". With the current logic, if the user enters two reference seqs with the same name (and without any other optional entries), there would not be a clash in names because the "Current Genome" format increments the numbers. If there is a clash, both sequences will be merged together as one in IGB.

          Show
          karthik Karthik Raveendran added a comment - - edited Ann Loraine , If the Month and Year fields are already entered and the user does not enter any other values, then the "Custom Genome 1" format would never appear. It will always be in the format "Genus_Species_Apr_2021". With the current logic, if the user enters two reference seqs with the same name (and without any other optional entries), there would not be a clash in names because the "Current Genome" format increments the numbers. If there is a clash, both sequences will be merged together as one in IGB.
          Hide
          karthik Karthik Raveendran added a comment -

          Rachel Weidenhammer & Nowlan Freese, ill make both the changes.

          Show
          karthik Karthik Raveendran added a comment - Rachel Weidenhammer & Nowlan Freese , ill make both the changes.

            People

            • Assignee:
              karthik Karthik Raveendran
              Reporter:
              nfreese Nowlan Freese
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development

                  Agile