Reports Task Force/Interest Group Information

[Turner, Jennifer M]

Thanks to everyone who attended our Reports meeting this morning at the Evergreen Conference.  A special thanks to Jennifer Bielweski from Lyrasis for volunteering to co-convene the Reports group with me!  It was awesome to have such a strong and enthusiastic turnout. 

 

Notes will be posted soon.  In the meantime, here are links to the Google Group and Evergreen wiki page referenced at today’s gathering.

Google Group: http://groups.google.com/group/open-ils-reports

Wiki: http://open-ils.org/dokuwiki/doku.php?id=evergreen-reports:taskforce

 

Happy Reporting!

 

Jenny

 

 

Jennifer Turner | PALS, A Program of the Minnesota State Colleges and Universities | 507-389-2000

 

[Jenny Turner [PALS]]

Jennifer Bielweski's notes from the conference session are below.
Hopefully we will get these cleaned up and added to our page on the
Evergreen wiki soon. If anyone would like to volunteer to do this,
please go right ahead (http://open-ils.org/dokuwiki/doku.php?
id=evergreen-reports:taskforce_meetings; page formatting standards are
here:http://www.evergreen-ils.org/dokuwiki/doku.php?
id=webteam:draft_guidelines, see the section on namespaces). Thanks!

Jenny Turner

Notes from the session—

Reports needed, essential or wish list
1) how much money a library owes another library
2) patrons by stat categories
3) how money was taken in each day by categories
4) title list that could be brought into a bucket or ran without
having access to the report interface
5) Missing data report- which records are missing x field
6) Missing or inaccurate fields in patron data
7) Simple reports that any staff can run without having to use the
report interface
8) Tweaking without cloning or redo-ing the whole report
9) Export templates to share with others
10) Report on what itemspatrons are borrowing from others—
11) Collection development, collection analysis reports, gaps in
collection, not checked out in x months or years
12) Auto-kill hanging reports
13) Patrons who are inactive
14) Average use of collection, patrons average use
15) Owed bill report like a credit card statement with itemized
transaction
16) More user friendly user face
17) Change the email address of the report without having to clone or
recreate
18) SQL and statements to do multiple comparisons on a column
19) Run reports for 30 minutes then kill
20) Export, export, export templates
21) How to teach people reports, set them up, definitions of the
tables
22) SC Lends have a good collection of reports and share amongst each
other
23) Easier to use interface
24) Simple interface that just runs existing reports—simple canned
reports with few clicks
25) Weed report
26) Records created by report, records, copies etc.
27) Turnover report, shelflist turnover report
28) A list of wanted reports that anyone can work on and share
29) List with titles and authors in its “natural case”
30) Reports that ignore deleting space with call numbers
31) Drop obvious mistakes
32) Fiscal or 3rd party reporting tools and can they work in EG
33) Sharing reports easier with all EG users
34) GIST weeding report will it work with EG? Gift and deselection
tool. You can look at other catalogs and conduct collection analysis
(Lets ask Cyril at SUNY!)
35) Nullability report ?


What is the development likelihood of sharing reports? There are
version issues but someone would need to go in the back and load it
using SQL script, we think!

On the Wiki is a reports page (Amy T.) (How to write SQL reports)
-How to get started
-How to run SQL reports on EG outside the system. Email Amy the
queries
-Is anyone using 3rd party tools to run reports?

Why is sharing so hard?
-Time?
-Different version?
-Accurracy?
-??

Once you share a report, you can’t delete the template (is this true?
Yes!)

Web Reporter product/MicroStrategy should be able to talk to any SQL
database.

Where to find help? Equinox, Listerv, others

Should there be a separate report server?



On Apr 27, 11:32 am, "Turner, Jennifer M" <jennifer.tur...@mnsu.edu>
wrote: