okay so call me stupid, but I keep forgetting that “Queries” are
"Saved Searches". So I go to make a dashboard, find the queries
screen and realize I need to make a new query … and go searching
around the interface looking for Queries. So after smacking my head
again, I’m wondering… Any reason to stick with Queries? Why not
call them “Saved Searches” and get rid of the Query word?
At the very least, can we put a link on the Queries page for creating
a new Query that links to the Search Builder?
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness
okay so call me stupid, but I keep forgetting that “Queries” are
“Saved Searches”. So I go to make a dashboard, find the queries
screen and realize I need to make a new query … and go searching
around the interface looking for Queries. So after smacking my head
again, I’m wondering… Any reason to stick with Queries? Why not
call them “Saved Searches” and get rid of the Query word?
Well, it’s not just Saved Searches. It’s anything with “Portlets”
It’s modeled on: http://rt3.fsck.com/Prefs/MyRT.html
“Saved Searches” isn’t quite right. Other thoughts?
okay so call me stupid, but I keep forgetting that “Queries” are
“Saved Searches”. So I go to make a dashboard, find the queries
…
why not call them “Saved Searches” and get rid of the Query word?
Well, it’s not just Saved Searches. It’s anything with “Portlets”
It’s modeled on: http://rt3.fsck.com/Prefs/MyRT.html
“Saved Searches” isn’t quite right. Other thoughts?
I don’t much care what the words are, as long as it’s easy to figure
out what one is. Like I said, a link from the query page to a page
where you can create new ones is probably all I need.
But I’ll keep thinking about it.
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness