Apologies for being some what last minute. These are some reports related ideas/questions/wishlist which were compiled from the mailing list.
Please look through and mail back if you would like to add more points to the discussion during the reports round-table. If you can't make it this year to the conference send us your ideas, requests, solutions, etc. we plan to do a write up and post it on the website. Here is the example list of base reports that George Tuttle came up with as a starting point [ http://list.georgialibraries.org/pipermail/open-ils-general/2010-March/002589.html ]. We will discuss this so if you think other canned reports (academic library needs?) need to be included (or his reports need to be modified) mail back or make a note to bring it up at the discussion. Discussion Points: - Sharing reports/repository for community. Rating good reports, comments about reports, etc. similar to Firefox extensions. - Create canned reports - what reports should be canned? Generic list? - Community process to decide which templates to add into base install. - Pre-scheduled reports that run automatically and where the end-user merely accesses the data, like the circulation reports for individual months. In this type of report, the results are canned and can't be altered(?) - Documentation on Data Sources for creating reports. - View SQL generated by report builder and an option to paste & use SQL into the reporter. - Show report title, date and description on top of output so it can be just printed. - Editing reports without creating a clone. - Show the settings entered when scheduling a report (the exact date ranges, circ modifiers, etc.) that were entered when creating a report - yes, we can put that in the description field, but people forget. - Long numeric barcodes are currently displayed in scientific notation which needs to be fixed. - Bookmark regularly used templates. - Right click option to reduce number of clicks (applies across the client) - UI for exporting/importing report templates across Evergreen installations (and have it catch whether a report depends on a reporter extension which may not exist in the importing installation). Later, it may even be desirable to have the UI tap directly into a community repository of such reports. - See reports be able to directly populate copy and/or record buckets (going in the other direction is possible now, but could probably be made easier). - Configure a run-time limit for reports (for example, if a report runs for over an hour, automatically kill it). - Sponsoring/Co-sponsoring development - Plan a roadmap? -------------------------- Cheers -- - - - - - - - - - - - - - - - - - - - - - - - - - Anoop Atre IS Developer & Integrator, MnPALS PH: 507.389.5060 OF: 3022 Memorial Library (Office-ML 3022) -- "Mit der Dummheit kämpfen Götter selbst vergebens" ~ Johann Christoph Friedrich von Schiller