Hi,
The Cosmo Team and PPD met today to work through design requirements
and implementation options to figure out how items are triaged and
loaded into the web client without killing the server and frustrating
the user.
Sheila will be sending out notes shortly. There is one problem /
issue we came across that may require a minor change in the Chandler
Desktop UI.
If a Chandler Desktop user decides *not* to share Triage status, the
server potentially ends up with lots and lots of untriaged items
(depending on the size of the collection being published).
The server doesn't know how to triage those items. However, the
server needs to figure out what's NOW versus LATER versus DONE in
order to be smart about parcelling out items to the web client
without clogging up traffic.
The best proposal we were able to come up with in the meeting was:
Remove the sharing filter options from the Publish dialog (for
Preview) so that users always push triage status to the server when
they publish. However, after they publish, desktop users can go to
the Manage share... dialog to adjust the sharing filters. This
preserves the ability to manipulate sharing filters on the desktop
end, but ensures that the server never gets a big pile of untriaged
items.
Admittedly, it is unlikely people will happen upon the sharing filter
feature by the themselves. We will need to relnote this so that users
know where to look for filtering options.
Does this sound reasonable. Can anyone think of a better solution
that solves the problem described above?
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
