• To produce web sites that show statistics and leaderboards for one or more BOINC projects. Examples are listed at here.
• To produce dynamically-generated images (typically used as message-board signatures) that show user and/or team credit, possible across projects. Examples are listed at here.
• To produce downloadable XML files that summarize cross-project statistics. We're trying to standardize the XML format.
• To produce web RPC interfaces to XML summaries of individual user or team statistics. We're trying to standardize the XML format. Examples are here: http://www.boinc.dk/index.php?page=download_stats_xml and http://www.boincstats.com/xml/xml_user_example.php.

Statistics data is exported in XML-format files. XML schemas for these files are here, and a graphical representation is here. NOTE: these are both somewhat out of date. Just look at the actual files - they're pretty self-explanatory.

Most projects regenerate the files every 24 hours.

These files are contained in a download directory, linked to from the project's web site (generally X/stats/, where X is the project URL).

The download directory contains the following files: "; list_start(); list_item("tables.xml", "This gives the total number of records for each entity type (team, user, and host). It also includes the UNIX time when the files were last generated, and a list of the project's applications, with counts of various things.
For example:

".
htmlspecialchars("
    1046220857
    127
    14
    681
    1234.234
    
        
            setiathome
            100
            1000
            10000
        
        ...
    

").
"

The format of the various XML elements in the output files is as follows.
Notes:

• <cpid> ('cross-project identifier') is a unique identifier across multiple projects. Accounts with the same email address on different projects will have the same cross-project identifier (as long as at least one computer is attached to both accounts).
• All 'expavg_credit' values were computed at some point in the past (given by 'expavg_time'). To compute their current values, they must be scaled according to the formula given here.

Team summary

",
htmlspecialchars("

 5
 Broadband Reports Team Starfire
 153402.872429
 503030.483254
 1087542007.701900
 14

"),
"

User summary

",
htmlspecialchars("

 12
 John Keck
 42698.813543
 117348.653646
 1087542007.701900
 283472938743489759837498347
 [ 5 ]
 [  ]

"), "

Host summary

",
htmlspecialchars("

  102
  3
  0.000000
  0.000000
  1087542007.701900
  GenuineIntel
  Pentium
  Windows XP
  5.1
  1040170006
  28800
  2
  45724737.082762
  43233895.373973
  4032258.064516
  670478336.000000
  1000000.000000
  1638260736.000000
  9088008192.000000
  3788505088.000000
  24109.794088
  57037.049858
  465609.562145
  e129b5fa44ed8ba58e41c472822f2807

"),"

A project can decide what data to export, and how it is divided into files. This is described by a file db_dump.xml of the following form: "; echo html_text(" x x x

n x

... ... "); echo " An 'enumeration' is a listing of particular table. The fields are: "; list_start(); list_item("table", "'user', 'host' or 'team'"); list_item("filename", "The base filename."); list_item("sort", "The sorting criterion: 'total_credit', 'expavg_credit', or 'id'. 'id' is the default." ); list_end(); echo "An 'output' is a file or set of files containing an enumeration. The fields are:"; list_start(); list_item("recs_per_file", "If present, the listing is divided into multiple files with the given number of records per file. The file names have the form xxx_N, where xxx is the base filename. For views that are ordered by ID, each file contains a fixed-size segment of the ID range, not a fixed number of records. If the database ID allocation has gaps, files will have fewer than this number of records.

If zero or absent, the listing is written to a single file." ); list_item("detail", "If present, records are 'detailed': user records include a list of hosts, and team records include a list of users." ); list_end(); page_tail(); ?>