Editing IRStats2 (section)

=Installation=

==Dependencies==
* Geo&#58;&#58;IP or Geo&#58;&#58;IP::PurePerl
* Date::Calc

Both can usually be installed via your Linux package managers (apt-get, yum, ...) or via CPAN.

=== Debian/Ubuntu ===
 apt-get install libgeo-ip-perl libdate-calc-perl

=== RedHat/CentOS/Fedora ===
 yum install perl-Geo-IP perl-Date-Calce

=== CPAN ===
 cpan Geo&#58;&#58;IP Date::Calc

==EPrints 3.3 and 3.4==
IRStats2 can be installed directly via the Bazaar on EPrints 3.3 and 3.4.

===EPrints 3.3.11 (inc. 3.4.x) onwards===
Installing IRStats2 from the Bazaar is all you need to do. It is recommend that you restart Apache after doing so.

===EPrints 3.3.1 to 3.3.10===
You need to install IRStats2 from the Bazaar as above, but you also need to apply a few patches to enable the Google map showing the "Origins of downloads".

The patches relate to an incompatibility between the Prototype JS library (used by EPrints) and Google Charts (used by IRStats2). The two patches you need to apply are:

*[https://github.com/eprints/eprints/commit/f7a9088aae29b8732cb5d8edd83d17e94f069e63 Upgrade Prototype]
*[https://github.com/eprints/eprints/issues/130 Fix auto-completers]

==EPrints 3.2.x==
See [[IRStats2/EPrints 3.2]]

==Processing==
IRStats2 uses its own tables to manage statistics, which it populates from the EPrints access table (a table containing a row for every access to EPrints objects). Once installed, IRStats needs to process the full contents of this table. Processing works in two steps: the initial processing and then a daily incremental processing. Because the initial processing will take care of all your legacy "download" data, this can take a (very) long time. It may take a few days if your repository is very large, although more likely it will take a few hours.

For the initial processing, run, as the "eprints" user, the below command (and remember this may take a long time to complete). If you are running it from an SSH session, you may want to use the "screen" Linux utility to make sure your SSH session will persist.

<pre>
/opt/eprints3/archives/REPO_ID/bin/stats/process_stats REPO_ID --setup --verbose
</pre>

For the daily incremental processing, add the below line in cron. It is a good idea to let this run over-night when there is less traffic to your repository (note the redirections of output to /dev/null will make the script run silently).

<pre>
perl /opt/eprints3/archives/REPO_ID/bin/stats/process_stats REPO_ID 1>/dev/null 2>/dev/null
The two redirections to /dev/null forces the process to not output anything.
</pre>