Calculate "answered" rate for questions posted in a certain time period, by tag

[ebarry]

THIS ISSUE IS PARTIALLY COMPLETE THANKS TO @cesswairimu -- PLEASE READ ALL THE WAY THROUGH TO SEE WHAT IS REMAINING:

What problem could this idea solve?

How can we know how many questions posted on publiclab.org are answered? Related: over in #2037 we're working on sorting the display of unanswered questions by recency of posting. But what is our overall answer rate in a period?

this snippet https://gist.github.com/jywarren/fd31cb03abfac4012362109b4cc47573 shows this calculation for the entire year 2017.

Next Steps

• We should display this number on /questions, perhaps with a dropdown menu to choose year, like 2017, 2016, 2015. I think this would be very motivating to people, to answer more questions and get our rate closer to 100%!
• DONE! We should also work in % answered rate to the time bounded stats pages, for instance it should appear here https://publiclab.org/stats/range/1-1-2017/31-12-2017/, and be updated for whatever date range is chosen in the URL
• We should also consider showing this on question pages by tag, for instance https://publiclab.org/questions/tag/water-quality - so that we can see for a given topic area what the rate of answered questions is. This will help us target our outreach efforts.

What did you expect to see that you didn't?

I just couldn't find what our "answer rate" was for a given time period. That's what i was looking for.

Please show us where to look

https://publiclab.org/stats/range/1-1-2017/31-12-2017/
https://publiclab.org/questions
https://publiclab.org/questions/tag/water-quality

[jywarren]

This sounds great -- it seems it could be broken into a few separate issues, one for each of the pages Liz points to. Thanks!

For the /questions pages, it could be for "all time" while on the "stats/range" page, we could use the start and end time periods from that page to set the range:

plots2/app/views/stats/range.html.erb

Line 3 in c58808b

<p>From <%= @start.to_formatted_s(:long) %> to <%= @end.to_formatted_s(:long) %></p>

Thanks!

[ryzokuken]

This sounds like a nifty addition indeed, and I would love to add this feature to the codebase.

@jywarren @ebarry help me make a list of things to do/add?

[ryzokuken]

TODO

• Display the stats on /questions
• Use a starting and ending datepicker
• Display the percentage on /range pages.
• Also display a percentage for a particular tag on the tag's tag page.
• Add tests for the same
• Make it default to no time bounds

[jywarren]

Perhaps the gist could be made into a unit-tested feature of Node -- like, `Node.answered(start, end)` , which defaults to no time bounds?

…

On Thu, Jan 25, 2018 at 2:54 PM, Ujjwal Sharma ***@***.***> wrote: This sounds like a nifty addition indeed, and I would love to add this feature to the codebase. @jywarren <https://github.com/jywarren> @ebarry <https://github.com/ebarry> help me make a list of things to do/add? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2120 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ7VpSj_W5ayMyrp0EjvmRhWDhPPDks5tONwFgaJpZM4RtWwF> .

[ebarry]

Hi! Lost track of this for a minute, coming back to it now as it's one of the few very tangible ways to measure "exchanges"

It would also be a cool way to incentivize Answering!

IS there any more information i could provide on this to make it doable?
I would like to be able to say a sentence like "During 2017, X questions were posted, and Y% of them were answered within Z days"

[ebarry]

hi @publiclab/soc , could we bump up this issue for the Google Code In? It's nice and discreet.

[Souravirus]

Yeah sure @ebarry

[ebarry]

UPDATE: I just updated the initial issue as the second of three feature requests has been implemented!!! Now, the /stats page does have a date picker, and a bar graph that seems to show the ratio of asked questions to answered questions in that period. See https://publiclab.org/stats?start=01-08-2019&end=31-10-2019 and experiment with the dates either in the URL or from the date picker:

Based on this success, at the next time we rotate through this "metrics" functions on the website, let's look into the first and third idea above, which are:

• adding the same stats bar to https://publiclab.org/questions
• adding a stats bar per topic (this will be important for research area reviews) -Add questions asked vs asked status bar in tag/topic page #6790

[cesswairimu]

Hey @ebarry, I created the issue for adding the status bar on tag page #6790 ..I think it would be best if it goes to this the tag stats page https://publiclab.org/tag/community/stats. thoughts?. On the questions page I remember I implemented the logic some time back #4256 but it wasn't published(it wasn't well implemented though just had a text displaying questions asked vs answered).. I think we opted to just have the bar on the '/stats' page or maybe @jywarren might remember the reason more clearly...Just checking to make sure we also need it on the questions page too. Thanks

[ebarry]

Wonderful that you planned for this information to go on the tag stats page! Agree. Yes, let's confirm with the forthcoming UI design for the questions page and see if there may be a good spot for a progress bar. Thank you Cess :D

…

On Sun, Nov 17, 2019, 5:10 AM Cess ***@***.***> wrote: Hey @ebarry <https://github.com/ebarry>, I created the issue for adding the status bar on tag page #6790 <#6790> ..I think it would be best if it goes to this the tag stats page https://publiclab.org/tag/community/stats. thoughts?. On the questions page I remember I implemented the logic some time back #4256 <#4256> but it wasn't published.. I think we opted to just have the bar on the '/stats' page or maybe @jywarren <https://github.com/jywarren> might remember the reason more clearly...Just checking to make sure we also need it on the questions page too. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2120?email_source=notifications&email_token=AABHNHZSEU4LLNQOVM56QB3QUEKCRA5CNFSM4ENVNQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIIMJY#issuecomment-554731047>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABHNH7DTDJM2D4APUJQJG3QUEKCRANCNFSM4ENVNQCQ> .

[jywarren]

With #6790 are we done here? Great work everyone!

[cesswairimu]

I believe this feature has been live for a while now. Closing this