Written in Java
Designer application run locally on PC
Users log in and run templates, via active directory or accounts created in Jasper
Self service reports with no reporter training
No post processing in Excel (person creating the report template can establish groupings, totals, etc.), and will provide functions such as auto-sums and averages
Will send automated, recurring reports
Report contents can appear in body of email, if desired
Option to not send an email if there is nothing in report output
Can also be saved on Jasper Reports server for later viewing
Templates with recurring reports can be edited, if edits don't change any of the filters the recurring report is using
Parameters are dynamic for broad use - all parameters don't have to be filled in each time a report is run
TADL runs their pull lists via Jasper Reports. The pull lists can autoprint. Pull lists are run by department via grouped shelving locations in a custom reporting view.
Reports can have granular permissions so that library staff can only view data for their own library, and certain users can have access to only certain reports.
Reports can link to item, borrower, tcn, title, etc in Evergreen, and can also link to other reports for more details
Back end
Administration
Limit to number of reports that are running at once? Unknown
Limit to length of query? Unknown, but can be controlled in Postgres
Server resources - "medium weight," 16 gigs RAM, 2 cpu, OpenJDK
Sharing templates - Jeff and Garry (whose library also runs Jasper) don't share templates currently, but they could