Differences

This shows you the differences between two versions of the page.

--- evergreen-reports:meetings:2012-04-25 [2012/05/17 10:34] – created jturner
+++ evergreen-reports:meetings:2012-04-25 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 16: / Line 16: @@
 ==== Introductions ====
-+ attendees
+  * 30+ attendees
-        Variety of new/investigating and experienced
+  * Variety of new/investigating and experienced
 ====  About the Reports Taskforce  ====
+  * A brief overview of the Reports Taskforce was provided (basically [[evergreen-reports:taskforce_activities|this]]).
+  * People interested in following the work of the Reports Taskforce were encouraged to join the [[http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-reports|mailing list]] and/or email reports@evergreen-ils.org for more information.
 ==== How many sites are writing their own SQL reports? ====
-        Not too many people appeared to be using SQL currently, but there was an interest from many in learning more about this option
+Not too many people appeared to be using SQL currently, but there was an interest from many in learning more about this option.
 ====  Sharing/Q&A/Divide into topical discussion groups (see below) ====
-        Newbies/Investigators (Jenny, PALS; Shae, ESI)
+  * Newbies/Investigators (Jenny Turner, PALS; Shae Tetterton, ESI)
-        Staff Client Report Ideas/New in 2.2 (Jess, Biblio)
+  * Staff Client Report Ideas/New in 2.2 (Jess Venturo, Biblio)
-        SQL (Amy, Biblio)
+  * SQL (Amy Terlaga, Biblio)
-====  Wire frames for Reports development ====
+====  Wireframes for Reports development ====
-        Pines and Emerald Data Systems hope to begin work on a reports interface project this summer.
+  * [[evergreen-reports:reports_wireframes|See them here]]
-        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.
+  * Primarily for upper level management to be able to get/view reports more easily.
-        Hope to be done by March 2013.
+  * Link to wireframes.
+  * Hope to be done by March 2013.
 ====     Large Group Sharing: highlights of small group discussions ====
@@ Line 42: / Line 45: @@
 (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 "stopping up;" need to restart it periodically.
+  * 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 "stopping up;" need to restart it periodically.
-Learn SQL vs. learn the reports writer in the client
+  * 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.
+    * 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.
+    * Learning the reports writer allows you to empower staff to run/clone own reports.
-Shortcomings of the report writer
+  * Shortcomings of the report writer
-"Best" documentation: Sitka has great training videos; current users suggested looking for "text" fields when building reports and following instructions for building a specific report (from another library) to begin to learn and understand the structure of the writer.  Pivot tables training in Excel has been handy for some library staff.
+  * "Best" documentation: Sitka has great training videos; current users suggested looking for "text" fields when building reports and following instructions for building a specific report (from another library) to begin to learn and understand the structure of the writer.  Pivot tables training in Excel has been handy for some library staff.
 === Staff Client Report Ideas/New in 2.2 ===
 (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
+  * Orphan volume reports
-Ideas for requirements/improvements:
+  * Ideas for requirements/improvements:
-Modify existing reports without cloning (could be permissions driven to allow some people to make direct changes, others to clone)
+  * 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
+  * Save name of report with report
 === SQL ===
 (Led by Amy Terlaga, Bibliomation)
-libraries/people running SQL with others interested
+  * 3 libraries/people running SQL with others interested
-"Package" of shared reports for SQL
+  * "Package" of shared reports for SQL
-JasperReports as a possibility
+  * JasperReports as a possibility
-Documentation on database schema
+  * Documentation on database schema