Changes Suggested By Whole-team Pressure Test

by ADMIN 46 views

Introduction

In preparation for an upcoming workshop, a pressure test was organized involving ~15 users, with a focus on Blast Search and in the Genotype Table, searching for samples via a defined haplotype. The purpose was to pressure-test the Pretzel server, to identify where the documentation and workshop plan can be clarified, and to identify gaps in the GUI experience which cause users to miss their objective. This issue documents the main findings, and these will be split out as sub-issues and implemented.

Summary of Issues / Findings

Deleting Selected Samples

  • Clarification in Documentation: When deleting selected samples from the text area, if you drag the cursor outside the window, it will close. Instead, drag it vertically, or use Ctrl-A to select all for delete. This can be clarified in the documentation to avoid confusion.
  • Adding a Clear Selected Samples Button: Adding a Clear Selected Samples button seems worthwhile. A number of users found it difficult to clear them by selecting all and delete/backspace. Ctrl-A is easy, but not all users are familiar with that. This button will provide an alternative solution for users who struggle with the current method.

Handling Large Data Sets

  • Threshold Limit on Number of Rows and Samples: Several users selected thousands of samples, which probably didn't get a result. The server log showed the result was too large. We currently have an (adjustable) threshold limit on the number of rows, but it should be on area - i.e., (number of rows) x (number of samples). This can display a message to reduce the rows and/or samples to enable the request. This threshold would be adjustable by the user; default could be 30000 (e.g., 300 x 100).

Improving User Experience

  • Reducing Lag When Selecting SNPs Alt/Ref: One user reported a noticeable lag when selecting SNPs Alt/Ref in the Genotype Table, for sorting / filtering / searching samples. This is probably explained by the most recent selection being highlighted with a blue border, and not changing to a green border until another action such as clicking another SNP. We are planning (in #511) to use a clearer color background to show this selection because the green dashed border is not visible immediately - it is overridden by the blue highlight.

Enhancing User Guidance

  • Clearing the Blast Result Tab: It was not obvious to several users that they should click on the Blast Result tab to see the result, and to view the axes. Part of this solution is just making it clear in the workshop & documentation, e.g., recent documentation has included an animation of mouse-clicks in the video clips. There may be some GUI change which can clarify this, e.g., a button in the search tab to go to the result tab now or a checkbox to enable switching to that tab automatically when the result is received.

Browser Compatibility

  • Exception in Firefox and MS Edge: After the meeting, we worked through the issues seen with Firefox and MS Edge; we were able to see an exception which probably affected the Dataset Explorer Trait/Ontology display, but didn't impact the exercise. That exception has been copy/pasted from the Web Inspector console and is being investigated In this 2nd work-through, the user was able to complete the blast search and the Genotype lookup OK in Firefox, so at this stage, we don't have any known issues with Firefox.

Sign-up Issues

  • Sign-ups Mostly Went OK: Sign-ups mostly went OK, but there were several sign-ups which didn't complete so I verified them manually in the database; there aren't any clear issues observed / reported.

Login Page Issues

  • 'Reset Password' Link Not Displayed: The 'Reset Password' link is not displayed on the Login page; this is being worked on.

Conclusion

Introduction

In our previous article, we discussed the main findings from the whole-team pressure test conducted on the Pretzel server. The pressure test aimed to identify areas that needed improvement in the server, documentation, and GUI experience. In this article, we will address some of the frequently asked questions (FAQs) related to the pressure test and its findings.

Q&A

Q: What was the purpose of the pressure test?

A: The pressure test was conducted to identify areas that needed improvement in the Pretzel server, documentation, and GUI experience. The test aimed to simulate real-world scenarios and gather feedback from users to enhance the overall user experience.

Q: What were some of the key findings from the pressure test?

A: Some of the key findings from the pressure test included:

  • Deleting selected samples from the text area can be confusing, and a clear solution is needed.
  • Handling large data sets can be challenging, and a threshold limit on the number of rows and samples is necessary.
  • Improving user experience by reducing lag when selecting SNPs Alt/Ref in the Genotype Table is essential.
  • Enhancing user guidance by making it clear that users should click on the Blast Result tab to see the result and view the axes is necessary.
  • Browser compatibility issues with Firefox and MS Edge need to be addressed.

Q: What are some of the proposed solutions to address the issues identified during the pressure test?

A: Some of the proposed solutions to address the issues identified during the pressure test include:

  • Adding a Clear Selected Samples button to make it easier for users to clear selected samples.
  • Implementing a threshold limit on the number of rows and samples to handle large data sets.
  • Improving the GUI by using a clearer color background to show the selection of SNPs Alt/Ref in the Genotype Table.
  • Enhancing user guidance by adding a button in the search tab to go to the result tab now or a checkbox to enable switching to that tab automatically when the result is received.
  • Addressing browser compatibility issues with Firefox and MS Edge.

Q: How will the proposed solutions be implemented?

A: The proposed solutions will be implemented as sub-issues and will be prioritized based on their importance and feasibility. The implementation will involve a collaborative effort from the development team, and the progress will be tracked and reported.

Q: What is the expected outcome of the proposed solutions?

A: The expected outcome of the proposed solutions is to enhance the user experience, improve the GUI, and provide better guidance to users. The proposed solutions aim to address the issues identified during the pressure test and make the Pretzel server more user-friendly and efficient.

Conclusion

The pressure test has provided valuable insights into the areas that need improvement in the Pretzel server. By addressing these issues, we can enhance the user experience, improve the GUI, and provide better guidance to users. The proposed solutions will be implemented as sub-issues, and the progress will be tracked and reported.