Page History
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).
...
Postgres
The trick is to edit pdpg_hdahba.conf to access from the smallest possible range of IP addresses:
...
| Code Block | ||
|---|---|---|
| ||
jdbc:oracle:thin:@//HOSTNAME:5432/dspace |
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 | ||||||
|---|---|---|---|---|---|---|
|
...
Do you have some reports that you might be willing to share? if so please log into upload them.
This is based on on
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Overview
Content Tools