[Cosmo-dev] Dashboard Server Requirements Meeting

Bobby Rullo br at osafoundation.org
Tue May 15 13:37:10 PDT 2007


Hi all,

This morning Matthew, Brian, Randy and I had a meeting to bring the  
client and server team to some sort of agreement on how client/server  
interaction will work for dashboard. Here are the main points that  
came out of that meeting (or at least my interpretation of them ;-) )  
Some of this stuff affects design so I will post another message to  
the design list.

3 Queries
--------------
* There client will be required to make three queries to get the  
dashboard data - one for NOW, one for LATER and one for DONE. Each  
will have different parameters that can be set

NOW Query
-----------------
* The NOW query will return all items triaged as "NOW" as well as  
expanded recurrence occurrences which are occurring at the moment the  
query is made.
* Open Issue: is it necessary to send over a TZID so the server can  
do the time range query (applies to all three queries...)

LATER Query
-------------------
* The LATER Query will return all the items triaged as "LATER" as  
well as the next expanded recurrence occurrence for every recurring  
item, possibly parameterized so that only occurrences within say a  
month are returned.

DONE Query
-----------------
* The DONE query will return all the items triaged as "DONE" as well  
as recurrence occurrences which have past, within a certain date range

Sorting/Paging
---------------------
* Happens on the client side

Auto-Triaging
--------------------
* There will be no timer on the client  which automatically triages  
items which have moved into the NOW timeframe
* A sort of auto-triaging does happen in that when a query is made  
and the client gets back events that are happening NOW it will ping  
back the server to update the triage.

Other Open Questions
------------------------------
* What is the secondary sort, if triage is the primary sort? Title  
perhaps? Date?
* Is there a special "Dashboard" collection? Or do we write a query  
which ignores collections for which it was told to "keep out of  
Dashboard"? Or do we just show dashboard functionality for whatever  
collection we have selected?

Bobby


More information about the cosmo-dev mailing list