...
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 DSpace 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).
Note that all steps here assume that you have configured DSpace, the database and the reporting tool to use UTF-8.
| Table of Contents |
|---|
Setting up External Reporting
...
Enabling remote database connections
Postgres
The trick is to edit pd_hda.conf to access from the smallest possible range of IP addresses:
| Code Block | ||
|---|---|---|
| ||
host dspace reporting 10.123.0.0/64 md5 |
...
ODBC-based reporting tools work by running one or more SQL query against the underlying DSpace database. You can find some examples in
| Jira | ||||
|---|---|---|---|---|
|
Reusing reports
TODO
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.
Reusing reports
Do you have some reports that you might be willing to
This is based on on
| Jira | ||||
|---|---|---|---|---|
|