Quote:
Originally Posted by chaley
Perhaps it should be a comments-like column so that it is searchable. Yes, it could be searchable anyway, but having the column would make that fact discoverable.
|
I'm working on the assumption that most people will be using naked search the majority of the time. The advanced search builder dialog would be used to create complex queries. At least until the user understands the syntax and how it works.
Quote:
Originally Posted by chaley
Searching the description raises the 'naked search' issue that we had to deal with in the library view: when I search for "foo", what columns are examined? I am not sure what the right answer is. It might be wise to limit naked terms to name, location, and formats, but that would force a user who wants to find stores with "mysteries" in the description to use something like description:"mysteries".
|
The way I've always looked at it is, naked searches everything. If you want to search a specific thing then you use a field search.
Quote:
|
Originally Posted by chaley
A harder-to-use alternative, but one that might pay some dividends in the future, would be to have a way to easily get to the plugin's configuration dialog from the chooser.
|
I like this idea better because it gives access to more than just the browser choice. I don't feel we need to relate any settings information in the chooser because that's not going to help the user decide if they want to disable or enable a store.