Re: [aerogear-dev] [UPS] What should the Top 3 Most Active Variants shows ?

On Fri, Aug 1, 2014 at 3:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > > > On Fri, Aug 1, 2014 at 3:08 PM, Matthias Wessendorf <matzew(a)apache.org&gt; > wrote: > >> >> >> >> On Fri, Aug 1, 2014 at 3:05 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >> wrote: >> >>> Hum, after thinking and looking a bit I think it's easier and more >>> clear to show the "real" 3 most recent active variants like you mentioned, >>> along with the numbers of receivers for the last push messages (but the >>> label should be made more obvious to explain this number, working on that s >>> well) >>> >> >> sounds good w/ me >> > Ok, here a last proposition, because our current model do really fit what > we want to do : What about showing the 3 last activity (regardless of the > variant) , basically a select on the PushMessageInformation sorted on > submitDate and we pick the 3 first one ? > ah, so it could be, for some reason list like this: * Variant A (50 message) * Variant C (5 message) * Variant A (15 message)

? I am totally fine with that as well. What ever makes sense and give some sort of "activity feeling" > > >> >> -M >> >> >>> >>> >>> >>> On Fri, Aug 1, 2014 at 2:39 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >>> wrote: >>> >>>> >>>> >>>> >>>> On Fri, Aug 1, 2014 at 2:34 PM, Matthias Wessendorf <matzew(a)apache.org >>>> > wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Fri, Aug 1, 2014 at 2:01 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Aug 1, 2014 at 1:52 PM, Matthias Wessendorf < >>>>>> matzew(a)apache.org&gt; wrote: >>>>>> >>>>>>> So the questions are, I think: >>>>>>> >>>>>>> 1) what does 'active' mean? >>>>>>> * total activity >>>>>>> * or recent activity >>>>>>> >>>>>>> Having [1] in mind, I *think* the three most recent active variants >>>>>>> makes sense >>>>>>> >>>>>>> 2) what number do we provide for that variant: >>>>>>> a) number of receivers/active tokens that received the last Push >>>>>>> message >>>>>>> b) total number of all receivers, in history >>>>>>> c) number of total push messages, per variant >>>>>>> >>>>>>> >>>>>>> Here, I *think* that b) does not make sense, having [1] in mind. I >>>>>>> think presenting a) or c) as the number on that "three recent active" >>>>>>> variants is a nice info. >>>>>>> >>>>>> >>>>>> Ok , but imagine this we have 4 variants, A,B,C,D. >>>>>> They all sent the same messages within the same hour , starting with >>>>>> : >>>>>> A sends 5000 messages >>>>>> B sends 100 messages >>>>>> C sends 15 messages >>>>>> D sends 50 messages >>>>>> >>>>> >>>>> >>>>> I think messages == receivers ? (I doubt that one variant will send >>>>> 5k of push messages - I'd try to sue the company for that amount of spam on >>>>> my phone) >>>>> >>>> yeah receivers :) >>>> >>>>> >>>>> >>>>>> >>>>>> The top 3 recent active are B,C and D , it's a bit a pita A do not >>>>>> show up, >>>>>> >>>>> >>>>> >>>>> that's life! :) >>>>> >>>>> >>>>>> since it was really the more active. >>>>>> Shall we define active within a period (24 hours ? ) ? >>>>>> >>>>> >>>>> doesn't make that even more complex ? >>>>> >>>> Well, not that much I think since we are already going to introduce a >>>> new query based on dates. I will take a look. >>>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> Sebi >>>>>> >>>>>> >>>>>>> -Matthias >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-673 >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 31, 2014 at 6:37 PM, Sebastien Blanc < >>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> I decided to start a new thread after some discussions we had on a >>>>>>>> previous thread[1] >>>>>>>> >>>>>>>> Basically, we are talking about this part of the dashboard : >>>>>>>> >>>>>>>> [image: screenshot-1.png - Latest 25/Jul/14 8:20 AM - Sebastien >>>>>>>> Blanc] >>>>>>>> >>>>>>>> It appeared that is not really clear what we want to show there, >>>>>>>> as a side note, the current query behind this is not correct and should >>>>>>>> change whatever we decide. >>>>>>>> >>>>>>>> So, what can we show here : >>>>>>>> >>>>>>>> 1. Show the most (three) recent active variants (and their # of >>>>>>>> receivers) >>>>>>>> Active means here, the 3 latest variants that sent a Push Message. >>>>>>>> The term "receivers" can also be confusing , do we want to show : >>>>>>>> >>>>>>>> 1.a : The number of receivers/active tokens that received the last >>>>>>>> Push message (i.e : Push Message A sent to 10 people and Push >>>>>>>> Message B to 5 people, we show 5) ? >>>>>>>> 1.b : The total number of receivers/actives tokens of this >>>>>>>> variant (i.e : Push Message A sent to 10 people and Push Message B to 5 >>>>>>>> people, we show 15) ? >>>>>>>> 1.c : The total number of Push Messages sent (i.e : Push Message >>>>>>>> A sent to 10 people and Push Message B to 5 people, we show 2). ? >>>>>>>> >>>>>>>> 2. Show the most active variants (and their # of receivers) >>>>>>>> Almost same than 1. but here we look at all the variants even >>>>>>>> those without an recent activity. >>>>>>>> Here again 1.a/1.b or 1.c applies. >>>>>>>> >>>>>>>> The core question, IMO, is what would be an useful information for >>>>>>>> the user ? >>>>>>>> >>>>>>>> Sebi >>>>>>>> >>>>>>>> >>>>>>>> [1] >>>>>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-July/008548.html >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev(a)lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev