- Koha - lists.katipo.co.nz

Backup of Koha 3
by john smith 23 Feb '09

23 Feb '09

Hi to all I have installed koha 3 on ubuntu 8.04 and all of that ok but i need to know way to talk Backup from data on mysql please if any body know way to that send me steps because i need that. thnks John Smith _________________________________________________________________ More than messages–check out the rest of the Windows Live™. http://www.microsoft.com/windows/windowslive/

2 1

Circulation rules
by Judith Nannozi 23 Feb '09

23 Feb '09

Dear All, My library is also one of those that are in the initial stages of familiarization with koha. We are using Koha 3.0 version. I am having problems with: 1. Realizing the changes/ revision I have made regarding circulation rules. I tried to revise the loan period of a certain category type i.e. Reserve Books being loaned out for 3 days other than the loan period i.e. 30 days for other books and the system is failing to recognize the changes. 2. I also tried initializing the "item due notices" and barring of patrons with over dues. I followed the manual step by step, but again after saving, nothing was realized. 3. We shifted from CDS/ISIS library management system to koha hence had our database records uploaded to koha. We were initially having various datacases, however these were merged into one database for koha. We have noticed a problem with records from the range 27528-27962 which belonged to a particular database. These do not show/ indicate any physical items as being available. We have also noticed that when you delete any of these records, for purposes of editing and try to re-enter the item details, it doesn't allow you to save but takes you to a page with a Koha error message Error: Can't call method "as_usmarc" on an undefined value at /opt/koha/src/C4/Search.pm line 2126. 4. While editing a record one of us must have stopped half way the editing process because if you go to details of the item, the original is not deleted. When we try to delete, it takes us to a page with a message error as follows "Koha error The following fatal error has occurred: Nested quantifiers in regex; marked by <-- HERE in m/1343,c++ <-- HERE fromthe\-(\d) at /opt/koha/src/C4/Biblio.pm line 2277." Could someone please help. Thanks in advance. Judith

3 2

Re: [Koha] How to add journals to koha
by thandu venkat narayana 23 Feb '09

23 Feb '09

Dear All, I am using Koha 2.2.9 on windows platform, I need help to add journals koha.. please give your valuable guidance to me. Thanks & Regards Venkat Check out the all-new Messenger 9.0! Go to http://in.messenger.yahoo.com/

2 1

problem in migrate data from Access(LIMS) to Koha
by saleemlib＠yahoo.com 23 Feb '09

23 Feb '09

Doug, Thanx for ur answer, its same error which we are facing in uploading. Now I have download Mark:Charset-0.92., but how I install it in Koha?. I can't search out about its installation process, I try it but I can't do this. With Regards Saleem Ahmad Librarian Federal Judicial Academy H - 8/4 Islamabad Tel (o) 051-9250388

2 1

Hi, I am new to KOHA. Please help. Just setup on Debain in a vitual environment. Ou web pages are cut in two on the bottom? It happens on multiple pages. Is this normal? Any explaination as to why?
by Goatley, Todd 23 Feb '09

23 Feb '09

Todd L. Goatley DCAS Washoe County Library - Spanish Springs 7100A Pyramid Lake Highway Sparks, NV 89436 Email: tgoatley(a)washoecounty.us W: 775-424-1843 C: 775-771-3489

4 4

Problems intalling Koha 3.0.1 stable on Ubuntu server 8.04
by "Thommy M. Malmström" 22 Feb '09

22 Feb '09

I'm following the install instructions on http://wiki.koha.org/doku.php?id=koha_3_install_guide_ubuntu_hardy Everything goes smoothly untill the build phase where the make test can't access the database. I can manually access the database with the user=kohaadmin and password=kohaadmin but it seems as if they don't match when it comes to using it from perl DBI. Anyway, I went along and did the install but it hangs at the zebrasrv init. Accessing localhost:8080 or koha3:8080 just gives access error messages as below... So, is it just me that have set the wrong password somewhere, or? I don't find any instructions to uninstall my installation, to be able to start over. Must I reinstall the whole Ubuntu server? [...] perl Makefile.PL make make test # Here I see errors in database access sudo make install sudo ln -s /etc/koha/koha-httpd.conf /etc/apache2/sites-available/koha sudo a2enmod rewrite sudo a2ensite koha && sudo /etc/init.d/apache2 reload sudo mkdir -p /var/lock/koha/zebradb/biblios sudo mkdir -p /var/lock/koha/zebradb/authorities sudo zebrasrv -f /etc/koha/koha-conf.xml # Here it hangs (I bail out with ^C) Accessing http://localhost:8080 in the browser give this... Koha error The following fatal error has occurred: Can't connect to MySQL server on 'koha3' (111) at /usr/share/perl/5.8/CGI/Carp.pm line 314. Compilation failed in require at /usr/share/koha/lib/C4/Circulation.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Circulation.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Overdues.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Overdues.pm line 24. Compilation failed in require at /usr/share/koha/lib/C4/Members.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Members.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 31. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 31. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. Log of the install +++++++++++++++090222+++++++++++++++++ $ perl Makefile.PL By default, Koha can be installed in one of three ways: standard: Install files in conformance with the Filesystem Hierarchy Standard (FHS). This is the default mode and should be used when installing a production Koha system. On Unix systems, root access is needed to complete a standard installation. single: Install files under a single directory. This option is useful for installing Koha without root access, e.g., on a web host that allows CGI scripts and MySQL databases but requires the user to keep all files under the user's HOME directory. dev: Create a set of symbolic links and configuration files to allow Koha to run directly from the source distribution. This mode is useful for developers who want to run Koha from a git clone. Installation mode (dev, single, standard) [standard] Please specify the directory under which most Koha files will be installed. Note that if you are planning in installing more than one instance of Koha, you may want to modify the last component of the directory path, which will be used as the package name in the FHS layout. Base installation directory [/usr/share/koha] Since you are using the 'standard' install mode, you should run 'make install' as root. However, it is recommended that a non-root user (on Unix and Linux platforms) have ownership of Koha's files, including the Zebra indexes if applicable. Please specify a user account. This user account does not need to exist right now, but it needs to exist before you run 'make install'. Please note that for security reasons, this user should not be the same as the user account Apache runs under. User account [koha] Please specify the group that should own Koha's files. As above, this group need not exist right now, but should be created before you run 'make install'. Group [koha] Please specify which database engine you will use to store data in Koha. The choices are MySQL and PostgreSQL; please note that at the moment PostgreSQL support is highly experimental. DBMS to use (Pg, mysql) [mysql] Please specify the name or address of your database server. Note that the database does not have to exist at this point, it can be created after running 'make install' and before you try using Koha for the first time. Database server [localhost] koha3 Please specify the port used to connect to the DMBS [3306] Please specify the name of the database to be used by Koha [koha] Please specify the user that owns the database to be used by Koha [kohaadmin] Please specify the password of the user that owns the database to be used by Koha [katikoan] kohaadmin Koha can use the Zebra search engine for high-performance searching of bibliographic and authority records. If you have installed the Zebra software and would like to use it, please answer 'yes' to the following question. Otherwise, Koha will default to using its internal search engine. Please note that if you choose *NOT* to install Zebra, koha-conf.xml will still contain some references to Zebra settings. Those references will be ignored by Koha. Install the Zebra configuration files? (no, yes) [yes] Found 'zebrasrv' and 'zebraidx' in /usr/bin. Since you've chosen to use Zebra with Koha, you must specify the primary MARC format of the records to be indexed by Zebra. Koha provides Zebra configuration files for MARC 21 and UNIMARC. MARC format for Zebra indexing (marc21, unimarc) [marc21] Koha supplies Zebra configuration files tuned for searching either English (en) or French (fr) MARC records. Primary language for Zebra indexing (en, fr) [en] Koha can use one of two different indexing modes for the MARC authorities records: grs1 - uses the Zebra GRS-1 filter, available for legacy support dom - uses the DOM XML filter; offers improved functionality. Authorities indexing mode (dom, grs1) [grs1] dom Please specify Zebra database user [kohauser] Please specify the Zebra database password [zebrastripes] Since you've chosen to use Zebra, you can enable the SRU/ Z39.50 Server if you so choose, but you must specify a few configuration options for it. Please note that if you choose *NOT* to configure SRU, koha-conf.xml will still contain some references to SRU settings. Those references will be ignored by Koha. Install the SRU configuration files? (no, yes) [yes] SRU Database host? [localhost] koha3 SRU port for bibliographic data? [9998] SRU port for authority data? [9999] Since you've chosen to use Zebra, you can also choose to install PazPar2, which is a metasearch tool. With PazPar2, Koha can perform on-the-fly merging of bibliographic records during searching, allowing for FRBRization of the results list. Install the PazPar2 configuration files? [no] yes Zebra bibliographic server host? [localhost] koha3 Zebra bibliographic port for PazPar2 to use? [11001] PazPar2 host? [localhost] koha3 PazPar2 port? [11002] Would you like to run the database-dependent test suite? (no, yes) [no] Koha will be installed with the following configuration parameters: AUTH_INDEX_MODE dom DB_HOST koha3 DB_NAME koha DB_PASS kohaadmin DB_PORT 3306 DB_TYPE mysql DB_USER kohaadmin INSTALL_BASE /usr/share/koha INSTALL_MODE standard INSTALL_PAZPAR2 yes INSTALL_SRU yes INSTALL_ZEBRA yes KOHA_GROUP koha KOHA_INSTALLED_VERSION 3.00.01.005 KOHA_USER koha MERGE_SERVER_HOST koha3 MERGE_SERVER_PORT 11001 PATH_TO_ZEBRA /usr/bin PAZPAR2_HOST koha3 PAZPAR2_PORT 11002 RUN_DATABASE_TESTS no ZEBRA_LANGUAGE en ZEBRA_MARC_FORMAT marc21 ZEBRA_PASS zebrastripes ZEBRA_SRU_AUTHORITIES_POR9999 ZEBRA_SRU_BIBLIOS_PORT 9998 ZEBRA_SRU_HOST koha3 ZEBRA_USER kohauser and in the following directories: DOC_DIR $(DESTDIR)/usr/share/koha/doc INTRANET_CGI_DIR $(DESTDIR)/usr/share/koha/intranet/cgi-bin INTRANET_TMPL_DIR $(DESTDIR)/usr/share/koha/intranet/htdocs/intranet-tmpl INTRANET_WWW_DIR $(DESTDIR)/usr/share/koha/intranet/htdocs KOHA_CONF_DIR $(DESTDIR)/etc/koha LOG_DIR $(DESTDIR)/var/log/koha MAN_DIR $(DESTDIR)/usr/share/koha/man MISC_DIR $(DESTDIR)/usr/share/koha/misc OPAC_CGI_DIR $(DESTDIR)/usr/share/koha/opac/cgi-bin OPAC_TMPL_DIR $(DESTDIR)/usr/share/koha/opac/htdocs/opac-tmpl OPAC_WWW_DIR $(DESTDIR)/usr/share/koha/opac/htdocs PAZPAR2_CONF_DIR $(DESTDIR)/etc/koha/pazpar2 PERL_MODULE_DIR $(DESTDIR)/usr/share/koha/lib SCRIPT_DIR $(DESTDIR)/usr/share/koha/bin SCRIPT_NONDEV_DIR $(DESTDIR)/usr/share/koha/bin ZEBRA_CONF_DIR $(DESTDIR)/etc/koha/zebradb ZEBRA_DATA_DIR $(DESTDIR)/var/lib/koha/zebradb ZEBRA_LOCK_DIR $(DESTDIR)/var/lock/koha/zebradb ZEBRA_RUN_DIR $(DESTDIR)/var/run/koha/zebradb To change any configuration setting, please run perl Makefile.PL again. To override one of the target directories, you can do so on the command line like this: perl Makefile.PL PERL_MODULE_DIR=/usr/share/perl/5.8 You can also set different default values for parameters or override directory locations by using environment variables. For example: export DB_USER=my_koha perl Makefile.PL or DB_USER=my_koha DOC_DIR=/usr/local/info perl Makefile.PL If installing on a Win32 platform, be sure to use: 'dmake -x MAXLINELENGTH=300000' Checking if your kit is complete... Looks good Writing Makefile for koha thommym@koha3:~/build/koha-3.00.01-stable$ $ make test PERL_DL_NONLAZY=1 KOHA_CONF=blib/KOHA_CONF_DIR/koha-conf.xml /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/PERL_MODULE_DIR', 'blib/arch')" t/*.t t/Amazon.......................ok t/Barcodes_PrinterConfig.......ok t/Bookfund.....................ok t/Bookseller...................ok t/Boolean......................ok t/Branch.......................ok t/Calendar.....................ok t/Charset......................ok t/Circulation_barcodedecode....DBI connect('dbname=koha;host=koha3;port=3306','kohaadmin',...) failed: Can't connect to MySQL server on 'koha3' (111) at /home/thommym/build/koha-3.00.01-stable/blib/PERL_MODULE_DIR/C4/Context.pm line 666 t/Circulation_barcodedecode....NOK 1 # Failed test 'use C4::Circulation;' # in t/Circulation_barcodedecode.t at line 10. # Tried to use 'C4::Circulation'. # Error: Can't connect to MySQL server on 'koha3' (111) at /home/thommym/build/koha-3.00.01-stable/blib/PERL_MODULE_DIR/C4/Context.pm line 666. # Compilation failed in require at /home/thommym/build/koha-3.00.01-stable/blib/PERL_MODULE_DIR/C4/Circulation.pm line 25. # BEGIN failed--compilation aborted at t/Circulation_barcodedecode.t line 10. # Compilation failed in require at (eval 3) line 2. # BEGIN failed--compilation aborted at (eval 3) line 2. Undefined subroutine &C4::Circulation::barcodedecode called at t/Circulation_barcodedecode.t line 31. # Looks like you planned 16 tests but only ran 1. # Looks like you failed 1 test of 1 run. # Looks like your test died just after 1. t/Circulation_barcodedecode....dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-16 Failed 16/16 tests, 0.00% okay t/Dates........................ok 1/126# # In order to run without DB access, this test will substitute 'us' # as your default date format. Export environmental variable KOHA_TEST_DATE_FORMAT # to override this default, or pass the value as an argument to this test script. # # NOTE: we test for the system handling dd=00 and 00 for TIME values, # therefore you *should* see some warnings 'Illegal date specified' related to those. # # Testing Legacy Functions: format_date and format_date_in_iso # Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 58 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 61 # # Testing 4 formats. # Testing no input (defaults): # # Testing with valid inputs: Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 # # Testing object independence from class # done. # Looks like you planned 126 tests but ran 9 extra. t/Dates........................dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 127-135 Failed 9/126 tests, 92.86% okay t/Debug........................# BEFORE use: $debug is not defined # BEFORE use: $cgi_debug is not defined t/Debug........................ok 1/3# AFTER use: $debug is 0 # AFTER use: $cgi_debug is 0 # Done. t/Debug........................ok t/dummy........................ok t/Input........................ok t/Koha.........................ok t/Languages....................ok t/Maintainance.................ok t/Output.......................ok t/Record.......................ok t/Review.......................ok t/Scrubber.....................ok 1/10# Note: scrubber test output will have whitespace collapsed for readability # done. t/Scrubber.....................ok t/Stats........................ok Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------------- t/Circulation_barcodedecode.t 255 65280 16 31 193.75% 1-16 t/Dates.t 255 65280 126 9 7.14% 127-135 Failed 2/21 test scripts, 90.48% okay. 7/189 subtests failed, 96.30% okay. make: *** [test_dynamic] Error 255 thommym@koha3:~/build/koha-3.00.01-stable$ thommym@koha3:~/build/koha-3.00.01-stable$ Installing /usr/share/koha/man/man3/acqui::lateorders.3pm Koha's files have now been installed. In order to use Koha's command-line batch jobs, you should set the following environment variables: export KOHA_CONF=/etc/koha/koha-conf.xml export PERL5LIB=/usr/share/koha/lib For other post-installation tasks, please consult the README. thommym@koha3:~/build/koha-3.00.01-stable$ export KOHA_CONF=/etc/koha/koha-conf.xml thommym@koha3:~/build/koha-3.00.01-stable$ export PERL5LIB=/usr/share/koha/lib thommym@koha3:~/build/koha-3.00.01-stable$ ls -l /etc/apache2/sites-available/koha ls: cannot access /etc/apache2/sites-available/koha: No such file or directory thommym@koha3:~/build/koha-3.00.01-stable$ ls -l /etc/apache2/sites-available total 4 -rw-r--r-- 1 root root 985 2008-06-25 15:49 default thommym@koha3:~/build/koha-3.00.01-stable$ sudo ln -s /etc/koha/koha-httpd.conf /etc/apache2/sites-available/koha thommym@koha3:~/build/koha-3.00.01-stable$ sudo a2enmod rewrite Module rewrite installed; run /etc/init.d/apache2 force-reload to enable. thommym@koha3:~/build/koha-3.00.01-stable$ sudo a2ensite koha && sudo /etc/init.d/apache2 reload Site koha installed; run /etc/init.d/apache2 reload to enable. * Reloading web server config apache2 [ OK ] thommym@koha3:~/build/koha-3.00.01-stable$ sudo mkdir -p /var/lock/koha/zebradb/biblios thommym@koha3:~/build/koha-3.00.01-stable$ sudo mkdir -p /var/lock/koha/zebradb/authorities thommym@koha3:~/build/koha-3.00.01-stable$ sudo zebrasrv -f /etc/koha/koha-conf.xml 11:27:59-22/02 [log] zebra_start /etc/koha/zebradb/zebra-biblios.cfg 1.3.50 11:27:59-22/02 [log] zebra_start /etc/koha/zebradb/zebra-biblios.cfg 1.3.50 11:27:59-22/02 [log] zebra_start /etc/koha/zebradb/zebra-authorities-dom.cfg 1.3.50 11:27:59-22/02 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/bibliosocket id=1 11:27:59-22/02 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/authoritysocket id=2 11:27:59-22/02 [server] Adding dynamic listener on tcp:@:11001 id=3 11:27:59-22/02 [server] Starting server zebrasrv pid=15181

2 2

Re: [Koha] FW: data migration from excel to koha
by Koustubha Kale 22 Feb '09

22 Feb '09

1 0

Re: [Koha] I'm confused about where normal view customization occurs
by Doug Dearden 20 Feb '09

20 Feb '09

Thanks Joe, I'll look at the HTML::Template perldoc. By your reply I surmise that this takes a code modification and there is no way to do it from the admin pages. Regarding the copy prog stuff, I was doing that in an effort to use the "opactheme" option. Copy the default theme, rename it, then make minor modifications to the copy and point a second database at that theme rather than the default. It didn't work, I put in a bug report (#2774) to which Owen commented "There are a LOT of instances in templates and code where the "prog" theme is hardcoded." So I abandoned that avenue. With xsl on for one DB and off for the other, I was able to customize the detail page the xsl version uses and leave the other alone. With the exception of those changes, the rest of my customizations are simple ones that can be pointed to from the System Preferences - different color.css files, simple changes in the header via html in the right place in system preferences. Because of that I haven't been using git. My notes about the install make me think that I thought it was going to remove aptitude in favor of it. As I was using aptitude to look for perl packages as well as others, I said no to installing git. Perhaps I misunderstood something there. This is my first time using Linux and Perl on a production system, so I am learning those as I go. It is not my intention to do any major modifications in the Perl code, but I can tweak where necessary to get things looking the way our librarian would like them to. Is there a reference on git you can point me to? Or can you tell me how it is used in Koha development? I am completely in the dark regarding it. Thanks, Doug >>> Joe Atzberger <ohiocore(a)gmail.com> 2/20/2009 11:24:53 AM >>> Like any page, you can add TMPL_VAR's to the template, and add to the script that populates it. It sounds like you should refer to the HTML::Template perldoc to see how it operates. The XSL solution is a lot slicker if you can manage it, but that only applies for the OPAC (when enabled). I'm not sure what approach you are taking by copying prog, but then using a "second database" on it. Copying prog is pretty drastic and is sure to cut off your developments from mainline updates. If you use git to control your code, then you wouldn't need to copy everything (since you could always revert to the mainline version if it got messed up), and you could still pull down updates. --Joe On Fri, Feb 20, 2009 at 12:46 PM, Doug Dearden <dearden(a)sarsf.org> wrote: > Ah, OK. I have multiple databases and have turned on the xsl option on one > of them and used it to customize how the clickable links appear, as that > database is cataloging on-line resources. I ran into trouble turning on xsl > for the other databases, as the "prog" directory is hard coded in many > places in the code, and copying the file structure over to a new directory > and pointing a second database at that structure didn't work, too many > things still fetched from "prog". Because of that I left the xsl option off > on the main catalog DB. > > So is the answer to my question that the customization for this occurs at > the Perl template level? Or is there some other place in the Admin that I > can add other fields to the Title line in the Normal View? > > Thanks, > > Doug > > >>> Nicole Engard <nicole.engard(a)liblime.com> 2/20/2009 9:14 AM >>> > The screenshots in the manual are probably different because some were > taken with XSL on and others with it off. There are two system > preferences that control this and can be found here: > > https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/a… > > --- > > Nicole C. Engard > Open Source Evangelist, LibLime > (888) Koha ILS (564-2457) ext. 714 > nce(a)liblime.com > AIM/Y!/Skype: nengard > > http://liblime.com > http://blogs.liblime.com/open-sesame/ > > > > On Fri, Feb 20, 2009 at 11:06 AM, Doug Dearden <dearden(a)sarsf.org> wrote: > > Hello all, > > > > I am trying to figure out if there is an easy way to add to the fields > that appear in the Normal view of the OPAC and the Staff Client. > Specifically, we currently see the 245$a field as the Title in the search > results and detail view page. Is there a way in the Admin screens to change > the display so the 245$b subfield is appended to the 245$a subfield, and > display both as the Title? I thought this would be customizable from within > the frameworks, but I don't seem to be having any luck. Looking at the doc > on this page: > https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/o… samples show titles with two different formats, one of which appears to > be displaying info that is normally in the 245$b field. > > > > Is this customization that takes place at the Perl template level? Or is > there something I am missing in the Admin? > > > > Thanks, > > > > Doug > > > > _______________________________________________ > > Koha mailing list > > Koha(a)lists.katipo.co.nz > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

2 1

I'm confused about where normal view customization occurs
by Doug Dearden 20 Feb '09

20 Feb '09

Hello all, I am trying to figure out if there is an easy way to add to the fields that appear in the Normal view of the OPAC and the Staff Client. Specifically, we currently see the 245$a field as the Title in the search results and detail view page. Is there a way in the Admin screens to change the display so the 245$b subfield is appended to the 245$a subfield, and display both as the Title? I thought this would be customizable from within the frameworks, but I don't seem to be having any luck. Looking at the doc on this page: https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/o… the samples show titles with two different formats, one of which appears to be displaying info that is normally in the 245$b field. Is this customization that takes place at the Perl template level? Or is there something I am missing in the Admin? Thanks, Doug

4 4

User History
by Melanie Hedgespeth 20 Feb '09

20 Feb '09

Does anyone utilize the patrons reading history option for users? If so why, and if not, why not? Thanks! Melanie Hedgespeth Tech Center Manager Salina Public Library 785.825.4624 Ext. 233 melanie(a)salpublib.org <mailto:melanie@salpublib.org> P Please consider the environment before printing this e-mail.

6 5