Apologies for the deluge of emails, but I think this should splinter
off into a separate thread.
So, my understanding is that a long time ago, we decided to defer
this feature to post-Preview for a number of reasons.
From the user scenarios we collected, we reconfirmed Mitch's
original insight that we really want saved queries to be:
+ Automatically refreshed
+ Support inclusions and exclusions (e.g.
+ Be reflected on its member items as a 'Label' (aka the 'Appears in'
field)
+ Be shareable
This means our search collections (unlike the ones in alpha4) would
essentially behave like all other support Drag and Drop of items both
IN and OUT of the collection. AND users would be able to name the
search collection.
I can believe that there are phasing proposals that would make it
possible for us to implement a portion of this design with minimal
usability fallout. However, at this late stage, I am hesitant to go
down that path, as I personally don't have the bandwidth to devote
much energy to new designs and I fear we are running out of time to
have many more rounds of experimentation with Search.
Ultimately, this is product/schedule call, so I defer to Sheila's
judgement on this issue.
That being said, we could put some energy into a menu feature that
stored saved searches into a separate palette. I think that would be
sufficiently out of the realm of the sidebar that users won't have
misguided expectations about how the saved searches should behave.
We can revisit this issue after Preview with some user feedback.
Mimi
On Feb 1, 2007, at 10:54 AM, D John Anderson wrote:
Finally, what did you think about letting the user save the search
results in a collection?
John
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
