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).
| Table of Contents |
|---|
Setting up External Reporting
...
Creating the connection string
TODO
Creating reports
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
This is based on on
| Jira | ||||
|---|---|---|---|---|
|