hippware / rn-chat

MIT License
5 stars 0 forks source link

Weekly Server Side Report Request #366

Closed zavreb closed 7 years ago

zavreb commented 7 years ago

Note to @aksonov, this is @bernardd request.

Goal: These reports will help our intern team (who will be in charge of growth hacking) as well as product on the direction tr will take.

1. Report summing up information created beforehand date range: 16 Dec 2016 to 31 Jan 2017

2. Automatic script: A weekly report with the following columns:

For Bots:

1. owner handle
2. title
3. address
4. lat
5. lon
6. visibility (what does 20, 40, 10, 100) translate to? vs. "Only Me"/"Select Friends"/"All Friends"/"All Friends & Followers"/"Everyone"
7. Subscriber Count
8. Image Count
9. Note (text)
10. last viewed timestamp (@scurry's request)

Nice-to-have:

3. In csv format. The weekly report should only have bots created during that week

4. Report can be emailed automatically to reporting@hippware.com

zavreb commented 7 years ago

@thescurry please let me know if you would like additional info, I think this covers the basis and what is available for bot profile.

cc: @bengtan

thescurry commented 7 years ago

Can we also track (and I may need to discuss this a bit more with RZ):

bengtan commented 7 years ago
  1. Note (text)

For this, do you want just the bot description / cover note / first note, or do you want a dump of all notes published to the bot (which is probably just 1 or 2 but could be a lot)

These three items:

  1. last viewed timestamp (@scurry's request)

Total number of times a bot has been viewed (so we understand how popular a particular bot is)

Number of times bot is shared (is sharing a thing... or not a thing?)

aren't stored in the database.

If you want it, we can track this in the database but it's additional functionality. Please confirm.


Also, tracking these two:

  1. last viewed timestamp (@scurry's request)

Total number of times a bot has been viewed (so we understand how popular a particular bot is)

on the server side might be problematic because the server can only count how many times the bot has been retrieved by the app.

For example, if the app retrieves a bot but not show it to the user, the server would count '+1' but it's not actually a view.

Need more discussion, probably

bengtan commented 7 years ago

@zavreb:

This probably should have been posted to the back-end board.

With your prior approval, I'd like to move it to the back-end board ... unless you want a ticket on the front-end in order to track things. If so, I'll just create a separate ticket on the back-end board.

Also, in the future, feel free to post tickets directly to the back-end board.

zavreb commented 7 years ago

@bengtan feel free to create a dup on the back-end, I'll keep this here for tracking purposes.

bengtan commented 7 years ago

Corresponding server side ticket:

Weekly database report #490 https://github.com/hippware/wocky/issues/490

However there are some ambiguities ...

9. Note (text) is ambiguous

'Date last modified' and 10. last viewed timestamp (@scurry's request) needs to be discussed.

... so the first report will be an approximation and we'll refine it as we go.

zavreb commented 7 years ago

The 9. Note (text) is description thanks guys!

bengtan commented 7 years ago

Can be closed?

zavreb commented 7 years ago

Closing.