Notes have been made on Wiki pages where content was taken with links to the files in the github repository and links to the html document (some links will need updating). Moreover, links have been added to the documentation outline (http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline) indicating the corresponding wiki content for various sections.
It was determined that using the DIG list is a good place for communication from the web committee for questions, suggestions, etc... Other communication means will be used as needed.
Bibliomation on the basics of SQL reports writing. We now have a variety of SQL reports that run on daily & monthly basis.
Originally, we manually ran these SQL reports as necessary. But we soon decided that we would need to setup an automated process for the most commonly used (and repeated) reports. This would be especially important once we migrated our entire consortium to Evergreen. We decided to experiment by setting up the daily circulation SQL report for our libraries.
I began by writing a few shell scripts that would work together to produce the content we desired. The scripts worked to query the Evergreen database directly, output the results into a CSV (comma-separated value) file, do a little massaging to make things look pretty, and then run through a Perl conversion script to place the results into XLS Excel format. The final XLS files would then be e-mailed to the libraries. The scripts are "automated" using cronjobs set to run daily. Our first daily circ reports went live two weeks ago without too much trouble, we are now working to adapt the monthly SQL reports to be automated in this fashion.
Our next objective is to continue generalizing the scripts and consolidating them so that they can be shared and used effectively by the community if so desired.</code>
DIG has made a good deal of progress collecting, writing, and editing documentation, and converting it to DocBook format. The new host for the documentation site is: http://docs.evergreen-ils.org/ Eventually, this URL will lead to a jump page with links to all the various versions and formats of the documentation. The current and only version is the draft version of the 1.6 documentation: http://docs.evergreen-ils.org/1.6/draft/html/ The documentation outline shows which areas are complete and which areas still need work. http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline Jeremy Buhler from Sitka contributed a docbook style guide: http://docs.evergreen-ils.org/style_guide/html/ As of the last meeting, the documentation was being refreshed manually. It is now generated automatically. On a nightly basis, the documents are pulled from the github repository and the HTML and PDF files are generated on the server.
Our last few meetings have been sparsely attended - any interested bodies are welcome to join us! View information about the group here: http://groups.google.com/group/open-ils-reports. We're curious about reports in 2.0; at the time of our last meeting in September, no one in attendance was testing 2.0. We're reviewing the PINES report requirements document. Our next meeting is scheduled for tomorrow at 1:00 Central/2:00 Eastern. We could definitely use a few more people; if you're interested, let one of the current Reports people know.
The director of the Software Freedom Conservancy (Bradley Kuhn) said in IRC that invitations to new member projects will go out today - including to Evergreen. Also, from today's governance meeting, expect more membership proposals to get kicked around on the lists.