Again the use case is not visible to the user. It is all about sorting and 
I want to use it in Synapse. For that I need to have "starred subjects" which 
are all subject that have been ACCESSED or MODIFIED more than 10 times within 
the last 24h. These are usually things that are stamped in the users mind.
Now querying for most used does not tell me how many times it was used. Thus if 
i opened something 2 times in a day making it the most used subject it actually 
Allowing me to query for the subjects and having a count would tell me how they 
relatively match to each other as well as how they rank in an absolute matter.
I know it sounds stupid but there is no use case for it. It makes development 
Another one I can think of is Unity Places. I have the most used. Now lets say 
the most used person was contacted 10 times in the last 24 hours and all others 
were contacted 9 times. This makes the count irrelevant since 10 to 9 is not 
big of a difference to make it stand out. Thus I shouldn't consider it as a 
star item.

Add new aggregate API
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Zeitgeist Framework: Confirmed

Bug description:
Zeitgeist API can give us vague information but not statistics over the API
Use case:
- Give me counts of every subject_text from actor = Unity
Currently to do that one will need to either:
Request all events with Unity as an Actor and count the subject_text
This can be done much better IMHO
I am thinking of an Aggregation Extension.
But before we hack on that we need to agree if its necessary and how the API 
will look like.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to