Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Many organisational DSpace users run reports on DSpace not from within DSpace itself, but from within an external reporting system (Business Intelligence, JasperReports, etc) which connect to the DSpace database via ODBC. Reports may be run on an external reporting system rather than DSpace to allow integrated reporting across a number of systems, to allow integration with other organisational systems, to exploit existing reporting skills, or for other reasons. Typically the connection is read-only, this allows both better security (since it limits the damage that an incompetent or malicious user can do) and better performance (since read-only accesses to tables typically require less locking or resource-use in most databases).

...

ODBC-based reporting tools work by running one or more SQL query against the underlying DSpace database. You can find some examples in

Jira
serverDuraSpace JIRA
keyDS-1645
which illustrate the kinds of SQL joins that you'll be looking at using. Note the use of item.in_archive = 't' and item.withdrawn = 'f' to check whether the item has been deleted or withdrawn respectively.

Note that some data (such as access stats) aren't held in the SQL database but in solr. Access details for these can be found at Solr#AccessingSolr.

Reusing reports

Do you have some reports that you might be willing to share? if so please log into upload them.

...