Statistics - Revision history

Stuartyeates at 10:03, 19 April 2011

2011-04-19T10:03:38Z

Emcaulay: /* Kinds of statistics */ typo corrections

2011-04-05T16:09:37Z

‎Kinds of statistics: typo corrections

Emcaulay: typo corrections

2011-04-05T16:09:11Z

typo corrections

Emcaulay: typo correction

2011-04-05T16:08:17Z

typo correction

Stuartyeates at 02:59, 5 April 2011

2011-04-05T02:59:15Z

Stuartyeates at 02:56, 5 April 2011

2011-04-05T02:56:12Z

Stuartyeates at 02:53, 5 April 2011

2011-04-05T02:53:43Z

Stuartyeates at 00:30, 5 April 2011

2011-04-05T00:30:26Z

Stuartyeates at 10:09, 4 April 2011

2011-04-04T10:09:37Z

Stuartyeates at 08:04, 4 April 2011

2011-04-04T08:04:28Z

← Older revision		Revision as of 10:03, 19 April 2011
Line 15:		Line 15:

	A number of TEI projects use google analytics as a tool for measuring user statistics. It uses a piece of javascipt on the bottom of every page to track users as they browse to the website and continue on their way across the web. Hosted, so once you install a fragment of javascript someone else takes care of everything else. Very good for tracking which search terms are bringing users to a site. Very good filtering-out of bots, scripts and malware. Nice PDF reports. Only sees javascript-using web browsers. Lots of features assume that the website is selling something in a monetary transaction which are thus irrelevant to most TEI projects. Sites can grant read access to third parties to look at their stats, enabling sharing and comparison of stats.		A number of TEI projects use google analytics as a tool for measuring user statistics. It uses a piece of javascipt on the bottom of every page to track users as they browse to the website and continue on their way across the web. Hosted, so once you install a fragment of javascript someone else takes care of everything else. Very good for tracking which search terms are bringing users to a site. Very good filtering-out of bots, scripts and malware. Nice PDF reports. Only sees javascript-using web browsers. Lots of features assume that the website is selling something in a monetary transaction which are thus irrelevant to most TEI projects. Sites can grant read access to third parties to look at their stats, enabling sharing and comparison of stats.
		+
		+	Also used on parts of the http://www.tei-c.org/ website (P5 guidelines, most navigation: yes; P4 guidelines, some archival content: no).

	https://www.google.com/analytics/		https://www.google.com/analytics/

@@ Line 3: / Line 3: @@
 === Kinds of statistics ===
-There are in general three reasons to produce statistics, it is important to know what you want to do with your statistics before you start or you may end up being unable to measure what you need.
+There are in general three reasons to produce statistics. It is important to know what you want to do with your statistics before you start or you may end up being unable to measure what you need.
 # to monitor workflow and progress towards set targets. These are most often reported internally often include documents ingested in a unit time, measured error rates of OCR, server uptime, server response time, collection size, etc. They are typically tied to a workflow or service contract (real or implied) of some description.
 # to find how users are using a collection. These focus on how users interact with the collection and often include most popular pages, popular search terms, referring websites, etc. They are typically used in aggregate to measure what people are interested in and how easy a site is to use.

@@ Line 3: / Line 3: @@
 === Kinds of statistics ===
-There are in general three reasons to produce statistics, it is important to know you want to do with your statistics before you start or you may end up begin usable to measure what you need.
+There are in general three reasons to produce statistics, it is important to know what you want to do with your statistics before you start or you may end up being unable to measure what you need.
 # to monitor workflow and progress towards set targets. These are most often reported internally often include documents ingested in a unit time, measured error rates of OCR, server uptime, server response time, collection size, etc. They are typically tied to a workflow or service contract (real or implied) of some description.
 # to find how users are using a collection. These focus on how users interact with the collection and often include most popular pages, popular search terms, referring websites, etc. They are typically used in aggregate to measure what people are interested in and how easy a site is to use.

@@ Line 3: / Line 3: @@
 === Kinds of statistics ===
-Three are in general three reasons to produce statistics, it is important to know you want to do with your statistics before you start or you may end up begin usable to measure what you need.
+There are in general three reasons to produce statistics, it is important to know you want to do with your statistics before you start or you may end up begin usable to measure what you need.
 # to monitor workflow and progress towards set targets. These are most often reported internally often include documents ingested in a unit time, measured error rates of OCR, server uptime, server response time, collection size, etc. They are typically tied to a workflow or service contract (real or implied) of some description.
 # to find how users are using a collection. These focus on how users interact with the collection and often include most popular pages, popular search terms, referring websites, etc. They are typically used in aggregate to measure what people are interested in and how easy a site is to use.

@@ Line 111: / Line 111: @@
 | 25
+|
+| ~34000
 |}

@@ Line 104: / Line 104: @@
 |  [http://freedict.org http://freedict.org]
 | 2
+|
+|

@@ Line 38: / Line 38: @@
 === AWStats ===
-Log based statistics, similar to Webalizer.
+Log based statistics, similar to Webalizer. See for example: http://vgstats.huygensinstituut.knaw.nl/awstats/awstats.pl?config=vg
 http://awstats.sourceforge.net/
@@ Line 114: / Line 114: @@
 # http://en.wikipedia.org/wiki/Web_analytics
 # http://www.jiscmu.ac.uk/ (I know they do monitoring / statistics of websites but they don't seem to have documentation of how/what they measure and why)
-# http://news.netcraft.com/ Good for ''what web-server are/were they running?'' type checking
+# http://news.netcraft.com/ Good for ''what web-server are/were they running?'' type checking. Confused by proxies and complex hosting arrangements
-# http://waybackmachine.org/ Good for find dates of site-wide updates
+# http://waybackmachine.org/ Good for find dates of site-wide updates. Rarely complete.

@@ Line 92: / Line 92: @@
 |    [http://www.nzetc.org/ http://www.nzetc.org/]
 |  2091
-|  13000
+|  ~13000
-|  >50000
+|  ~150000
 |-
 |  http://en.wikipedia.org/wiki/The_SWORD_Project

@@ Line 108: / Line 108: @@
 |}
-The reason that 'Raw hits per day' is so much higher than the 'Google pageview per day' is that the raw hits include requests by real users for images, javascipt, etc as well as requests from bots and scripts (including, of course, Google's own web crawlers). The raw hits is perhaps a useful measure of server load, but pageviews a much better measure of how many real people are really using a website.
+Examples stolen from the wikipedia page for the  [http://en.wikipedia.org/wiki/Text_Encoding_Initiative TEI]. The reason that 'Raw hits per day' is so much higher than the 'Google pageview per day' is that the raw hits include requests by real users for images, javascipt, etc as well as requests from bots and scripts (including, of course, Google's own web crawlers). The raw hits is perhaps a useful measure of server load, but pageviews a much better measure of how many real people are really using a website.
 === See also ===