Summary

So this is definitely something that needs to be expanded upon and detailed. The idea is to build upon our current analytics solution to be something much more usable and visually interesting:

1. collect more information
2. display it on a pretty page

As someone dives into it there'll be better information here but for now I want to get this on paper.

so an idea that hit me last night

[11:36]
we could totally expand analytics on go links

[11:36]
I'm talking graphs

[11:36]
I'm talking charts

[11:36]
I'm talking history

[11:36]
I'm talking user agents

[11:36]
now (edited)

[11:36]
privacy policy would be a must

Nander [11:37 AM] So, rather than link.count += 1 link.save(), a separate clicks model?

David Haynes [11:37 AM] yeah def

[11:37]
I think there's potential to collect more information over a period of time

Nander [11:38 AM] This might be where caching will be useful

[11:38]
If you calculating datapoints for a bunch of graphs on a page, it'd be handy to only have to recompute them daily or w/e

David Haynes [11:39 AM] agreed

[11:39]
mylinks would still show basic info but could have an option to expand into greater information

[11:40]
or could link to an go.gmu.edu/analytics/$linkname

Nander [11:41 AM] Maybe a quick line chart (sparkgraph style) for clicks this month

[11:41]
or week

[11:41]
or w/e

[11:41]
on the mylinks page

David Haynes [11:41 AM] ah yeah that'd probably be a good basic visual

Helpful Links

• D3?