More often than not, I use the ugly old core/search tool for quick searches because the dashboard interface is heavy enough that it adds 30 seconds of fiddling to get into. The problem is a combination of a few factors:
I use firefox as my main browser, and dashboard does not work in firefox;
when I start chrome to use dashboard, it requires me to login every time because I have just restarted chrome (evidently logins to last through browser restarts?);
the interface is relatively heavy and does not make it easy to just throw a search into a box, google style -- I generally have to double click to select the text in one keyword box, set the dates to be longer, and delete the second query;
the results take much longer to return because they are doing so much more (and I think doing much of it in serial rather than parallel).
I recognize that there are good reasons for all of the design decisions that go into the current interface (many pushed by me!). But I'm worried that the end product is actively discouraging a major use case (quick check searches in the flow of working on some larger problem).
More often than not, I use the ugly old core/search tool for quick searches because the dashboard interface is heavy enough that it adds 30 seconds of fiddling to get into. The problem is a combination of a few factors:
I recognize that there are good reasons for all of the design decisions that go into the current interface (many pushed by me!). But I'm worried that the end product is actively discouraging a major use case (quick check searches in the flow of working on some larger problem).