[OPEN-ILS-GENERAL] Report View error
Dear Evergreen community, We employ Evergreen 2.09 on our Linux running servers. While trying to export our patron lists or bibliographic records through AdminLocal Administration Reports, we encountered some difficulties. The problem is that after creating a report on stuff client we are not able to View it, although Stuff client says that the document was created successfully. The server responses with this error. * The requested URL /reporter/1/5/5/report-data.html was not found on this server. ** In fact, there is no such directory in **/openils/var/web/reporter/1/1/1/report-data.html**. We have even created a *reporter* folder in /openils/var/web/ directory and made it writable by everyone. However, the problem was not fixed. In addition, we know that there is another way to export the necessary data through postgre SQL commands. Can someone hint a useful link or advice on this issue? We need to export our patrons. Any advices? Arayik.
Re: [OPEN-ILS-GENERAL] Report View error
Hi Aarayik When I've seen this, it's because the report itself didn't run, so it did not create the result file.Do you see any other error messages? Alternatively, you might look at using the PostgreSQL ODBC driver.We've done some reports that way. Hope that helps June From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Araik Manukyan Sent: Friday, January 13, 2012 3:43 AM To: open-ils-general@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] Report View error Dear Evergreen community, We employ Evergreen 2.09 on our Linux running servers. While trying to export our patron lists or bibliographic records through AdminLocal Administration Reports, we encountered some difficulties. The problem is that after creating a report on stuff client we are not able to View it, although Stuff client says that the document was created successfully. The server responses with this error. * The requested URL /reporter/1/5/5/report-data.html was not found on this server. ** In fact, there is no such directory in **/openils/var/web/reporter/1/1/1/report-data.html**. We have even created a *reporter* folder in /openils/var/web/ directory and made it writable by everyone. However, the problem was not fixed. In addition, we know that there is another way to export the necessary data through postgre SQL commands. Can someone hint a useful link or advice on this issue? We need to export our patrons. Any advices? Arayik.
[OPEN-ILS-GENERAL] Global Flags for Historical Circulation Retention Age and Historical Circulations per Copy?
Hi Folks I'm working on the Server Administration section of the 2.1 documentation for DIG, and I haven't been able to find an explanation of what the global flags for Historical Circulation Retention Age and Historical Circulations per Copy do.It looks like they are both enabled by default. Can anyone please point me to some information about it, or explain? Thank you! June Rayner ILS Application Team (412) 622-1941 rayn...@einetwork.net
[OPEN-ILS-GENERAL] 2012 EG International Conference Program
*Please excuse cross-posting* Hello everyone! Hope everyone's 2012 is off to a great start! Just a quick email to notify everyone that there is a program outline available for the 2012 Evergreen International Conference on the website to help prospective attendees make their travel arrangements: http://evergreen2012.org/schedule/ Final recommendations for programs have been made by the Program Committee and we plan to add a detailed list of programs to the schedule outline next week. Everyone who submitted a potential program will be notified at that time. Also, there is important information about reserving hotel rooms on the Venue page of the blog: http://evergreen2012.org/venue/ Let me know if you have any questions! ___ Shauna Borger Evergreen Indiana Coordinator Indiana State Library 140 North Senate Avenue Indianapolis, IN 46204 Direct: 317-234-6536 Toll free: 1-800-451-6028 Fax: 317-232-0002 sbor...@library.in.gov
Re: [OPEN-ILS-GENERAL] Global Flags for Historical Circulation Retention Age and Historical Circulations per Copy?
Hi June, These settings are global settings which are related to circulation anonymization for privacy purposes. The standard behavior is that when a circulation is deleted in the database, a Postgres trigger calls a function called action.age_circ_on_delete which anonymizes the circulation's patron down to a postal code, home library, user profile and birth year. These are stored in a view which combines anonymized and non-anonymized circulations called action.all_circulations. Normally, circulations don't get deleted, so this needs to be done manually to anonymize circulations. To facilitate this, there is a database function called action.purge_circulations() which will purge circulations based on the following settings: === Global Settings === Historical Circulations per Copy - how many circs to hold onto per copy, if this is not set, then it will keep them all forever Historical Circulation Retention Age - how long to hold onto circs before 'aging' and anonymizing them, if not set, will default to 2000 years === User Settings === Historical Circulation Retention Age - how long to keep circs - this value overrides the global value for the user this setting is set for the user Historical Circulation Retention Start Date - the date to start retaining circs Typically, the patron would set these settings in the OPAC, so the idea would be that the default is don't keep my circs and they would have access to a checkbox that says keep my circs which sets the start date, and a setting for how long to keep my circs which sets the retention age. However, these settings are not implemented in the classic AJAX OPAC, although I believe they are implemented in the Template Toolkit PAC in 2.2 and in some of the KCLS OPAC skins for the AJAX OPAC. The action.purge_circulations() function is not run by default, so all circs are kept by default. I believe the idea is that a sysadmin should set that database function to run as a cron job at a regular interval if they wish to anonymize circs. ~James Fournie BC Libraries Cooperative Sitka Project On 2012-01-13, at 6:10 AM, Rayner, June wrote: Hi Folks I’m working on the Server Administration section of the 2.1 documentation for DIG, and I haven’t been able to find an explanation of what the global flags for Historical Circulation Retention Age and Historical Circulations per Copy do.It looks like they are both enabled by default. Can anyone please point me to some information about it, or explain? Thank you! June Rayner ILS Application Team (412) 622-1941 rayn...@einetwork.net
Re: [OPEN-ILS-GENERAL] How do other systems handle print notices?
Hi, On 01/12/2012 12:12 PM, Jonathan Field wrote: I've spent some time looking at this. I used the ESI scripts as a excellent starting point. We used generate_circ_notices.pl and then adapted the xsl so that it split the files up by org unit and also added some conditionals to allow different notice text for adults and juniors. Also managed to make it send different notices at different periods for different consortia members. It's a lot of xsl but is almost doing the job and produces PDF output. Next step is printed hold notifications. Anyone done anything with them as I can't see a way of doing it right now? Here's one way of doing it, briefly: create an action/trigger event definition using the hold.available hook, the HoldIsAvailable validator, and the ProcessTemplate reactor, and set up the template to emit XML akin to what generate_circ_notices.pl does for overdue notices. A daily cronjob could then gather up generated event output, stitch it into an XML file, then use adapted versions of the ESI overdue notice XSL and fop to produce PDFs. One of the nice things about this approach is that you can mix it up to suit your inclinations: - Don't like to process XML? Set up the A/T template to produce JSON, or YAML, or plain old CSV. - Don't like FOP? Use your preferred language to generate PDFs. - Are you so old-school that you'd rather use LaTex? Go for it! - Don't want to print your print notices yourself? Ship the data off to a third-party print-and-mail service. Regards, Galen -- Galen Charlton Director of Support and Implementation Equinox Software, Inc. / The Open Source Experts email: g...@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web:http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org http://evergreen-ils.org
