new queries

[Seif Lotfy]

Here are some new queries we need to look at.
1) Most popular actors
2) Most popular actors for subject template
It is not a must but I think covering that gives us a application-centric approach too, for some of our use cases

[Mikkel Kamstrup Erlandsen (kamstrup)]

In more technical engine-terms I think you are talking about defining some more zeitgeist.datamodel.ResultTypes? I don't understand 2, but something like 1 might be a good idea. Maybe we need to go full monty on this:

MostPopularActor
MostRecentActor
MP Origin
MR Origin

For consistency we'd also need the Least* version of these ResultTypes

[Seif Lotfy (seif)]

OK show we do this in the find_events method or should we give it a separate method.
I would vote for hitting it in find_events

[Mikkel Kamstrup Erlandsen (kamstrup)]

I think adding a separate method (or methods) for these use cases alone is a very slim basis for an API. Thus I'd like if we could shovel this under the FindEvents and FindEventIds or if we could come up with a more general purpose method that could do this...

That said I am not sure how 1. or 2. would make sense in our current Find* methods - they are specifically for finding events, and this does not seem to be the prupose of the functionality of your requests...

[Seif Lotfy (seif)]

The thing is this doable we just need to know where to implement it since
the data is in the DB...
Something like docky is interested in the 15 most used apps. To get that we
need to fetch the events within a timeperiod then count the actors. And if
not 15 piece we need to fetch from a wider timeperiod and count again. Thus
the suggestion of 15 most used or recents apps (for a mimetype or subject
etc...)

2010/1/17 Mikkel Kamstrup Erlandsen <email address hidden>

> I think adding a separate method (or methods) for these use cases alone
> is a very slim dbasis for an API. Thus I'd like if we could shovel this
> under the FindEvents and FindEventIds or if we could come up with a more
> general purpose method that could do this...
>
> That said I am not sure how 1. or 2. would make sense in our current
> Find* methods - they are specifically for finding events, and this does
> not seem to be the prupose of the functionality of your requests...
>
> --
> new queries
> https://bugs.launchpad.net/bugs/493903
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Zeitgeist Framework: New
>
> Bug description:
> Here are some new queries we need to look at.
> 1) Most popular actors
> 2) Most popular actors for subject template
> It is not a must but I think covering that gives us a application-centric
> approach too, for some of our use cases
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/zeitgeist/+bug/493903/+subscribe
>
>

[Siegfried Gevatter (rainct)]

2010/1/17 Seif Lotfy <email address hidden>:
> I would vote for hitting it in find_events

Yeah.

I'll have a go at this in a couple days, if nobody beats me to it.

--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer 363DEAE3

[Siegfried Gevatter (rainct)]

revision <email address hidden> (1303)
Author: Siegfried-Angel Gevatter Pujals <email address hidden>
Date: Wed 2010-01-20 19:39:38 +0100
Branch: zeitgeist-trunk
Bugs: https://launchpad.net/bugs/493903 fixed

    Add MostPopularActor, LeastPopularActor and MostRecentActor.
    There should also be a LeastRecentActor but I could get it to work :/.

[Siegfried Gevatter (rainct)]

revision <email address hidden> (1345)
Author: Siegfried-Angel Gevatter Pujals <email address hidden>
Date: Tue 2010-02-16 20:36:42 +0100
Branch: zeitgeist-trunk
Bugs: https://launchpad.net/bugs/493903 fixed

    Implement LeastRecentActor.

[Mikkel Kamstrup Erlandsen (kamstrup)]

I think Siegfried added these new ResultTypes just after 0.3.2 was released. The will be available in the next release. As far as I can see this covers the requested functionality. Can we close his bug?

[Siegfried Gevatter (rainct)]

Mikkel: It is closed :).