Versions Compared

Old Version 3

changes.mady.by.user Kristi Searle

Saved on

compared with

New Version 4

changes.mady.by.user Dennis Tobar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Better syntaxis... so, the page isn't update!

Files:

...

  1. DSpace comes with a very basic web statistics package which you can use to gather information on page views (not the same as file downloads) and general activities performed within DSpace (e.g. searches performed, logins, errors and warnings). This statistics package will analyze and parse all of your old DSpace logs (in dspace/log) to generate HTML statistical reports. It consists of a set of Perl scripts all beginning with "stat-" in your dspace/bin/ directory. (Note: In order to utilize these scripts you must have Perl installed!)
  2. There are two basic options in dspace.cfg which allow you to specify whether or not your final statistics reports should be publicly accessible ( Code Blockreport.public), and where the final statistical reports should be stored ( Code Blockreport.dir). It's very possible you may not want to change either of these. However, if you change either option, don't forget to restart Tomcat (See Quick Restart in Rebuild DSpace )
    • report.public = false
    • report.dir = ${dspace.dir}/reports/
  3. The DSpace Statistics package comes with its own configuration file, dstat.cfg. This file has some settings which you must change (marked with an asterisk below), and a few that you may wish to review:
  4. * Code Blockdspace.log*- the full path of your dspace/log directory
    • Code Blockgeneral.summary- actions listed in the DSpace log file which you want to list in the "Overview" section. You don't need to change these unless needed.code
    • exclude.word- stopwords to filter out of search terms in statisticscode
    • exclude.type- Lucene search index terms to filter out of statistics (corresponds to the search indicies, see (Modify search fields)code
    • exclude.character- Lucene special characters to filter out of statisticscode
    • item.type- Item types to find statistics for. Corresponds to the form values (see Change a form value ) defined for your Code Blockdc.type field, or any metadata field with an element named Code Blocktype.
    • Code Blockitem.floor and Code Blocksearch.floor- specify the number of minimum accesses necessary before an item or search term is listed in statisticscode
    • item.lookup- specifies the maximum number of items to list Author/Title information for in statistics (all other viewed items are listed by URL)code
    • user.email- specifies whether to display user email information in login statistics. For privacy, this defaults to Code Blockfalse (i.e. do not display email)
  5. * Code Blockhost.name and Code Blockhost.url* - The name and URL of your DSpace install, which will be displayed at the top of the statistics page.
  6. In addition, the DSpace Statistics package comes with a mapping file (dstat.map), which maps DSpace "actions" which appear in the log files (in dspace/log) into human readable text. So, if you wish to update the text which appears in the statistics reports, or change the language, you can edit this file to do so.
  7. First, you must modify each of these scripts slightly based on your own DSpace installation. Look for the following section in each of the stat-* files:
    • Code Block{{# Details used Code Block################################################ ################################################ }}
  8. In that section, you will likely need to modify any variable which specifies the full path of a directory or file location (these paths will all start with Code Block/dspace/ by default). In particular keep an eye out for these variables:
    • Code Block$dsrun- the full path of the dspace/bin/dsrun script
  9. * Code Block$in_directory - the full path of the input directory (for stat-report-* scripts)
    • Code Block$out_directory - the full path of the statistical reports output directory. This must correspond to the directory listed in the Code Blockreport.dir option in your dspace.cfg (see above)!
    • To keep things simple, you may wish to specify that both the Code Block$in_directory and Code Block$out_directory be the same location (e.g. dspace/reports/).
    • You may also wish to modify the Code Block$start_year and Code Block$start_month variables in Code Blockstat-initial and Code Blockstat-report-initial. These should correspond to the year and month which you wish to start tracking statistics from.
  10. Make sure you updated every one of the stat-* scripts! There's six of them total: Code Blockstat-general, Code Blockstat-initial, Code Blockstat-monthly, Code Blockstat-report-general, Code Blockstat-report-initial, Code Block stat-report-monthly
  11. You will first need to run the initialization script to gather data about all of the past months (back to the month and year specified in Code Block$start_month and Code Block$start_year). This script only needs to be run once, though you can rerun it if you needed to (in which case it would overwrite its past results). Its output is a set of historic data files which can be used by stat-report-initial to generate historic HTML reports.
  12. dspace Code Block/bin/stat-initial (Note: For Windows, you may need to run Code Blockperl dspace Code Block/bin/stat-initial)
  13. Next, generate a series of monthly reports for all of this past data by running the corresponding stat-report-* script. Again, this script only needs to be run once, though you can rerun it as needed. Its output is historic monthly HTML reports.
  14. dspace Code Block/bin/stat-report-initial (Note: For Windows, perl dspace Code Block/bin/stat-report-initial)
  15. The other four scripts should be run at least on a monthly basis, though you may even want to schedule them to run on a nightly basis in order to keep your statistics up-to-date at all times. These scripts will generate a report based on the activities this current month (stat-monthly and stat-report-monthly) and a general report aggregating all activities in the history of the repository (stat-general and stat-report-general). As in the examples above, the stat-report-* scripts should always be scheduled to run after their corresponding stat-* script.
  16. For Linux or Mac OSX, you can schedule the scripts to run by adding a Code Blockcron entry similar to the following to the crontab for the user who installed DSpace:
    Code Block
    30 0 * * * [dspace]/bin/stat-monthly
    Code Block
    35 0 * * * [dspace]/bin/stat-general
    Code Block
    30 1 * * * [dspace]/bin/stat-report-monthly
    Code Block
    35 1 * * * [dspace]/bin/stat-report-general
  17. (The above cron entry would schedule these scripts to run nightly. stat-monthly and stat-general would be scheduled for 12:30am and 12:35am respectively. While their corresponding report scripts would run at 1:30am and 1:35am respectively. Note: You would need to change dspace to the full path of your DSpace installation directory.)
  18. For Windows, you should use Windows Scheduled Tasks to schedule those same commands at an appropriate time of day. Just remember to schedule stat-monthly and stat-general to run before their corresponding report scripts (similar to the Linux/Mac OSX example above). In addition, you may need to call Perl explicitly (e.g. perl stat-monthly)
  19. After running all statistics scripts, your DSpace site's statistical reports will be available immediately at Code Block http://web-address-to-my-dspace/statisticsImage Added