[OPEN-ILS-DOCUMENTATION] Regarding Reports

Wed Nov 24 10:36:01 EST 2010

Robert and all,

Good questions!  I will bring these to the reports taskforce to see if I can drum up some volunteers for editing/beefing up content and see what types of additional information are needed wanted.  I think I can safely say that there was a desire for a how-to section for SQL queries, so perhaps we can add a place holder for this type of reporting in the DIG documentation?  

The next Reports Taskforce meeting is scheduled for Dec. 8th, but I'll query the group for ideas on specifics now and hopefully have more ideas - and perhaps some content - for the DIG group early next month.

Thanks - and Happy Thanksgiving!

Jenny

==============================
Jennifer Turner
PALS, A Program of the Minnesota State Colleges and Universities
Minnesota State University, Mankato
ML 3022
Mankato, MN 56001
507-389-2000

* Through Our Work, Knowledge Grows *

-----Original Message-----
From: open-ils-documentation-bounces at list.georgialibraries.org [mailto:open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Soulliere, Robert
Sent: Tuesday, November 23, 2010 7:15 PM
To: Documentation discussion for Evergreen software
Subject: [OPEN-ILS-DOCUMENTATION] Regarding Reports

Hi All,

Yes, I must say that the reports section is rather simple with basic information on the procedures but not too many details or examples.

There are also a couple of  "raw" SQL examples in the introduction to SQL chapter in the developer section.
See http://docs.evergreen-ils.org/1.6/draft/html/query_requests.html.

Now the greatest number of reports specialists are currently on the Reports Task Force so I wonder if someone form that group could...:

1) Edit the reports part directly to include more meaty information?

2) Share any documentation they might have in any format with the DIG so we can convert to DocBook and include in the Reports section. Or point us to any known existing documentation?

3) Specify what they would like to see added to the documentation such as more real life examples or techniques?

I am a bit fuzzy on whether we need more detailed step-by-step procedures for using the staff client reports module, more precise examples on various types of reports using the staff client report module or more techniques for creating reports using raw SQL outside of the staff client.

My fuzziness in this area is why I am not on the Reports Task Force.;-)

Thanks,
Robert

Robert Soulliere, BA (Hons), MLIS
Systems Librarian
Mohawk College Library
robert.soulliere at mohawkcollege.ca
Telephone: 905 575 1212 x3936
Fax: 905 575 2011
________________________________________
From: open-ils-documentation-bounces at list.georgialibraries.org [open-ils-documentation-bounces at list.georgialibraries.org] On Behalf Of Karen Collier [kcollier at kent.lib.md.us]
Sent: November 23, 2010 3:43 PM
To: open-ils-documentation at list.georgialibraries.org
Subject: [OPEN-ILS-DOCUMENTATION] DIG Update, Volunteer Requests, & More

Hi Everybody,

I just got done giving an update on what DIG has been doing at the Evergreen Community IRC Meeting (IRC Log and Minutes to be posted at http://evergreen-ils.org/dokuwiki/doku.php?id=community:meetings).  By the way, the next Community Meeting is scheduled for Tuesday, December 21 at 2 PM EST for anyone who wants to mark their calendars to attend.

This update inspired me to do a much overdue update on the DIG list, so here goes.  (And thank you to Robert Soulliere who reminded me of much of this.)

The version 1.6 documentation is nearing completion (Yay!)  A big thank you to everyone who has contributed!  Most of the chapters in version 1.6 have been completed or assigned as shown in the outline linked to from our main wiki page:
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig

BUT we need reviewers to read through the documentation at http://docs.evergreen-ils.org/ and provide feedback and corrections.  Please let me know if you're interested in helping out in this way.  You can submit bug reports on the documentation via Launchpad.  There are links throughout the documentation to do this.  Or submit feedback directly to this mailing list.

We're also looking for volunteers who have access to a 2.0 installation of Evergreen and would be interested in helping produce documentation covering features new and different to version 2.0.  Any format is okay.  Any takers?

During the discussion at today's Community Meeting, a member of the reports task force suggested that DIG may want to cover SQL reporting in our documentation.  Anyone interested in working on that topic?

Also from today's meeting, Dan Scott asked if there are any particular areas of mystery, where documentation writers might like to pick the brains of the people who are in the know.  He suggested that if we could come up with some topics we want to know more about, we could use some time at the next meeting to try to identify who could help us with those topics.  Sounds like a great idea to me!  Any suggestions on topics of this sort?

And last but not least (sorry for the lengthy email), who feels it's time to schedule another DIG meeting, and would be likely to attend?  It's been quite a while.  We could try to set up another GoToMeeting meeting like we've done before, or possibly consider an IRC chat format meeting.  Any thoughts?

Thanks,
Karen

--
Karen Collier
Public Services Librarian
Kent County Public Library
408 High Street
Chestertown, MD 21620
410-778-3636
www.kentcountylibrary.org
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation

This E-mail contains privileged and confidential information intended only for the individual or entity named in the message.  If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited.  If this communication was received in error, please notify the sender by reply E-mail immediately, and delete and destroy the original message.
_______________________________________________
OPEN-ILS-DOCUMENTATION mailing list
OPEN-ILS-DOCUMENTATION at list.georgialibraries.org
http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation