User Tools

Site Tools


evergreen-reports:meetings:2012-04-25

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
evergreen-reports:meetings:2012-04-25 [2012/05/17 10:45] – [About the Reports Taskforce] jturnerevergreen-reports:meetings:2012-04-25 [2012/05/17 10:52] – [How many sites are writing their own SQL reports?] jturner
Line 26: Line 26:
 ==== How many sites are writing their own SQL reports? ==== ==== 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) ==== ====  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)
                  
 ====  Wireframes for Reports development ==== ====  Wireframes for Reports development ====
Line 47: Line 47:
   * 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.
evergreen-reports/meetings/2012-04-25.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.