evergreen-reports:meetings:2012-04-25
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
evergreen-reports:meetings:2012-04-25 [2012/05/17 10:34] – created jturner | evergreen-reports:meetings:2012-04-25 [2012/05/17 10:39] – [Wire frames for Reports development] jturner | ||
---|---|---|---|
Line 16: | Line 16: | ||
==== Introductions ==== | ==== Introductions ==== | ||
- | | + | * 30+ attendees |
- | Variety of new/ | + | |
| | ||
==== About the Reports Taskforce | ==== About the Reports Taskforce | ||
Line 27: | Line 27: | ||
==== Sharing/ | ==== Sharing/ | ||
- | | + | * Newbies/ |
- | Staff Client Report Ideas/New in 2.2 (Jess, Biblio) | + | |
- | SQL (Amy, Biblio) | + | |
| | ||
- | ==== | + | ==== |
- | | + | * [[evergreen-reports: |
- | Primarily for upper level management to be able to get/view reports more easily. | + | * Pines and Emerald Data Systems hope to begin work on a reports interface project this summer. |
- | Link to wireframes. | + | |
- | Hope to be done by March 2013. | + | |
+ | | ||
| | ||
==== Large Group Sharing: highlights of small group discussions ==== | ==== Large Group Sharing: highlights of small group discussions ==== | ||
Line 42: | Line 43: | ||
(Led by Jenny Turner, PALS; Shae Tetterton, ESI) | (Led by Jenny Turner, PALS; Shae Tetterton, ESI) | ||
- | Q/A about reports: sources come from database tables; perhaps it is time to redesign to prevent recursive-ness within the client report writer; important to learn how to kill reports. A few sites have issues with the reporter " | + | * Q/A about reports: sources come from database tables; perhaps it is time to redesign to prevent recursive-ness within the client report writer; important to learn how to kill reports. A few sites have issues with the reporter " |
- | Learn SQL vs. learn the reports writer in the client | + | |
- | SQL is powerful, but puts the onus for reports on the person that knows SQL. Also requires DB access. | + | |
- | Learning the reports writer allows you to empower staff to run/clone own reports. | + | |
- | Shortcomings of the report writer | + | |
- | " | + | |
=== Staff Client Report Ideas/New in 2.2 === | === Staff Client Report Ideas/New in 2.2 === | ||
(Led by Jess Venturo, Bibliomation) | (Led by Jess Venturo, Bibliomation) | ||
- | Hold/copy ratio sources are new in recent past | + | * Hold/copy ratio sources are new in recent past |
- | Orphan volume reports | + | |
- | Ideas for requirements/ | + | |
- | Modify existing reports without cloning (could be permissions driven to allow some people to make direct changes, others to clone) | + | |
- | Save name of report with report | + | |
=== SQL === | === SQL === | ||
(Led by Amy Terlaga, Bibliomation) | (Led by Amy Terlaga, Bibliomation) | ||
- | 3 libraries/ | + | * 3 libraries/ |
- | " | + | |
- | JasperReports as a possibility | + | |
- | Documentation on database schema | + | |
evergreen-reports/meetings/2012-04-25.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1