GalaxyInterface problems identified by Cathy
QA suggestions for Galaxy2 UI -- July 27, 2005
1. The "About Galaxy" link points to a page that does not seem intended
for the end user. E.g. "your system must be able to run Python2.4" ?!
2. Perhaps "About Galaxy" should appear on the right side, where people
are used to seeing the Help > About menu? Also PSU is making noises about requiring the PSU logo (with link to main PSU page) in the upper *left* corner. There are exceptions allowed for consortium pages, but that's hard to argue if we do show a "Penn State" link without mentioning other institutions.
3. Why does "Center for Comparative Genomics" appear at the bottom as a
non-link, when it already appears at the top as a link?
4. Commas would be helpful in the result counts (e.g. "[ 124875502 bases ]"
is hard to read).
5. "Peek" and "display" are conceptually similar and should be adjacent.
Also one might think that "edit" means editing the data. I suggest "peek | display | edit attributes | delete".
6. When the last query is expanded, "refresh" tends to look like part of
it rather than a separate item. More vertical space before "refresh" and darkening the horizontal rules would help with this.
7. I suggest changing "Perform Actions" to just "Actions".
8. In a large window, the "[help]" links are too far away to align
visually. Maybe add horizontal rules like the Data section?
9. Help text contains many spelling and grammatical errors.
10. Both the action categories, and the items within them, seem to be
listed in no particular order, and exhibit inconsistent capitalization.
11. Titles are a mixture of nouns and verbs (e.g. "Subtract" vs.
"Vicinity"). (But fixing this might make it even more awkward.)
12. Why are "Filter" and "Add a column" listed under Statistics?
13. "Join Same queries"? Why "same"?
14. What is the first box in the Restrict tool for? And why can't I
restrict to a particular coordinate region on a chromosome?
15. I don't think "Union" is a verb.
16. Is "Regions per cluster" a minimum, or an exact requirement?
17. The term "extract" is a little confusing. How about "fetch"?
18. "Data sources" is not an "action". How about "Obtain data"?
19. "Upload data" should be moved to the end of the "Obtain data" category,
after "Featured datasets". It could also be renamed to "Upload custom data" for better clarity.
20. Once we get the format hierarchy ironed out, "Upload data" should
support more of them, especially AXT and MAF. Also, if we support generic text files, it may not be appropriate to assume they are column-based and try to parse them. Should the column parser be moved to the "Format conversions" section? This would require an extra step for the user to invoke the converter manually, but would make it more clear that conversion is optional.
21. It would be helpful to list genome assemblies with both the abbrev.
(e.g. hg17) and the date (Human, May 2004) wherever they appear. I can never remember which is which.
22. "BED File Converter creates a bed or xbed file containing from text query" ?
23. It's nice that the UI remembers what I had opened, but it becomes tedious
closing things manually for a fresh start. I suggest a "Collapse all" button or link, and similarly an "Expand all" one for non-script users.
24. "Join queries" and "Join Same queries" are very similar. Can we combine
them into one tool (at least for UI purposes), and just add a radio option to distinguish the two types of matching?
