- Koha - lists.katipo.co.nz

staff client, wrong default library
by Caitlin McGurk 04 Jan '11

04 Jan '11

G'mornin, Koha- While cataloging under the staff client, the default Library and Permanent Collection dragdown list are defaulting to the wrong library. In fact, I've never even heard of the libraries listed in my dropdown. Anyway to change that? While I catalog as the admin, it always defaults to the correct one. Suggestions? Caitlin McGurk -- Caitlin McGurk *Librarian The Schulz Library The Center for Cartoon Studies <http://www.cartoonstudies.org> McGurk(a)cartoonstudies.org*

2 1

remove catalog records...how?
by havergara 04 Jan '11

04 Jan '11

how do i remove catalog record in KOHA...my instructor says catalog records should not be removed because the accession number is continuous...thus every library catalogs should be documented or tagged as condemned or whatever it is called... -- View this message in context: http://koha.1045719.n5.nabble.com/remove-catalog-records-how-tp3325246p3325… Sent from the Koha - Discuss mailing list archive at Nabble.com.

3 2

Odd display in search results
by Elaine Bradtke 04 Jan '11

04 Jan '11

Koha 3.2.2 in the staff interface I was running a search using two terms and the 'or' operator. The search performed as expected. However, as we have highlight search results turned on, it highlighted 'or'. Not just 'or' on its own, but any instance of those two letters in that sequence (for instance the 'or' in Cranford). It does the same in the OPAC It's not a real serious problem. It doesn't actually search on 'or', it just highlights it. But it certainly looks strange and may be confusing to some users. I wonder how hard it would be to limit the highlighting to the actual text entered into the search box, so the Boolean operators would not be highlighted. -- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 ext 36 -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)

1 0

Re: [Koha] unable to run apache after upgrade from 3.0 to 3.2
by Randall Rowe 04 Jan '11

04 Jan '11

-----Original Message----- From: "Yatheesh Y" <yatheeshb(a)gmail.com> Sent 1/3/2011 10:54:54 PM To: "Randall Rowe" <r.rowe(a)lincolnlibraries.org> Cc: Koha(a)lists.katipo.co.nz Subject: Re: [Koha] unable to run apache after upgrade from 3.0 to 3.2 this is file apache error Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. On Mon, Jan 3, 2011 at 6:51 PM, Randall Rowe <r.rowe(a)lincolnlibraries.org> wrote: It means that the file /etc/apache2/sites-enabled/koha has an error. There is a closing </VirtualHost> without an opening <VirtualHost>. Check the file and see if you can figure out the problem or post it and we'll see what went wrong. Randy Rowe Lincoln City Libraries I.T. -----Original Message----- From: "Yatheesh Y" <yatheeshb(a)gmail.com> Sent 1/3/2011 5:19:10 AM To: Koha(a)lists.katipo.co.nz Subject: [Koha] unable to run apache after upgrade from 3.0 to 3.2 after upgrading unable to run apache it gives following error what is this? Restarting web server apache2 apache2: Syntax error on line 265 of /etc/apache2/apache2.conf: Syntax error on line 95 of /etc/apache2/sites-enabled/koha: </VirtualHost> without matching <VirtualHost> section -- ---------------------------- Y.Yatheesh babu Librarian Shri Shakti College of Hotel Management Venus Plaza Begumpet Hyderabad-500 016 09966178388 _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- ---------------------------- Y.Yatheesh babu Librarian Shri Shakti College of Hotel Management Venus Plaza Begumpet Hyderabad-500 016 09966178388 That file is most likely /etc/apache2/apache2.conf. The error is being caused by a problem in /etc/apache2/sites-enabled/koha. Compare the following with what you have in /etc/apache2/sites-enabled/koha # Koha Apache Configuration Directives #NameVirtualHost * ## OPAC <VirtualHost 172.25.1.252:80> ServerAdmin webmaster@lcltest DocumentRoot /usr/share/koha/opac/htdocs ServerName lcltest # ServerAlias opac.mydomain.com ScriptAlias /cgi-bin/koha/ "/usr/share/koha/opac/cgi-bin/opac/" ScriptAlias /index.html "/usr/share/koha/opac/cgi-bin/opac/opac-main.pl" ScriptAlias /opac-search.pl "/usr/share/koha/opac/cgi-bin/opac/opac-search.pl " ScriptAlias /search "/usr/share/koha/opac/cgi-bin/opac/opac-search.pl" ErrorLog /var/log/koha/koha-opac-error_log # TransferLog /var/log/koha/koha-opac-access_log SetEnv KOHA_CONF "/etc/koha/koha-conf.xml" SetEnv PERL5LIB "/usr/share/koha/lib" <IfModule mod_gzip.c> mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ </IfModule> <IfModule mod_deflate.c> # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml applicat ion/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate <IfModule mod_headers.c> #properly handle requests coming from behind proxies Header append Vary User-Agent </IfModule> </IfModule> # Repeat this virtualhost stanza changing the following environment vars to # create multiple OPAC interfaces with custom css and/or search limits: # SetEnv OPAC_CSS_OVERRIDE mystyle.css # SetEnv OPAC_SEARCH_LIMIT branch:CODE # SetEnv OPAC_LIMIT_OVERRIDE 1 Options +FollowSymLinks ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl # Rewrite Rules RewriteEngine On # Uncomment to turn on rewrite logging # RewriteLog /var/log/koha/koha-opac-rewrite.log # RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/opac-detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] </VirtualHost> ## Intranet <VirtualHost 172.25.1.252:8080> ServerAdmin webmaster@lcltest DocumentRoot /usr/share/koha/intranet/htdocs ServerName lcltest:8080 # ServerAlias intranet.mydomain.com ScriptAlias /cgi-bin/koha/ "/usr/share/koha/intranet/cgi-bin/" ScriptAlias /index.html "/usr/share/koha/intranet/cgi-bin/mainpage.pl" ScriptAlias /search "/usr/share/koha/intranet/cgi-bin/search.pl" ErrorLog /var/log/koha/koha-error_log # TransferLog /var/log/koha/koha-access_log SetEnv KOHA_CONF "/etc/koha/koha-conf.xml" SetEnv PERL5LIB "/usr/share/koha/lib" Options +FollowSymLinks ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl <IfModule mod_gzip.c> mod_gzip_on yes mod_gzip_dechunk yes mod_gzip_keep_workfiles No mod_gzip_can_negotiate yes mod_gzip_update_static No mod_gzip_temp_dir /tmp mod_gzip_minimum_file_size 512 mod_gzip_maximum_file_size 1000000 mod_gzip_maximum_inmem_size 1000000 mod_gzip_handle_methods GET POST mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\[" mod_gzip_item_exclude mime ^image/.* mod_gzip_item_exclude rspheader Content-Type:image/* mod_gzip_item_include file \.js$ mod_gzip_item_include mime ^application/x-javascript$ mod_gzip_item_include file \.php$ mod_gzip_item_include mime ^text/html$ mod_gzip_item_include file \.css$ mod_gzip_item_include mime ^text/css$ </IfModule> <IfModule mod_deflate.c> # Compress content with type html, text, and css, ... AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css AddOutputFilterByType DEFLATE application/xml application/xhtml+xml applica tion/rss+xml application/javascript application/x-javascript DeflateCompressionLevel 9 # Properly handle old browsers that do not support compression BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSIE !no-gzip !gzip-only-text/html DeflateFilterNote Input instream DeflateFilterNote Output outstream DeflateFilterNote Ratio ratio LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate <IfModule mod_headers.c> #properly handle requests coming from behind proxies Header append Vary User-Agent </IfModule> </IfModule> RewriteEngine On # Uncomment to turn on rewrite logging # RewriteLog /var/log/koha/koha-intranet-rewrite.log # RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] RewriteRule ^/issn/([^\/]*)/?$ /search?q=issn:$1 [PT] </VirtualHost> Randy

1 0

How to catalogue related items?
by Mirko 04 Jan '11

04 Jan '11

I have a "sorry-i'm-not-a-librarian"-question: How do I catalogue several items that belong together? For example: I have a series for language learning: one workbook, one grammar and two audio cds. They are not a single kit containing all items but have seperate call numbers and can be used/checked out independently of each other. Nonetheless they are related and this information needs to be available to the patron. I thought I would set up a biblio containing the general information (title, author etc.) and have items for workbook, grammar, cds with their respective call number/barcode. Somehow this seems to be the wrong way to do it: - I can only have one item type (for the biblio, not for the item) -- but i want patrons to be able to find for example the cds if they search for audio materials -- so this seems wrong - I used "Materials specified (bound volume or other part)" to put "CD 1", "CD 2", "Workbook"… but that information only shows up in the staff client. When searching the OPAC I don't get this info, neither can I do anything with the items of the biblio (like, place a hold), I can only look up "Item type", "Call number" and "Status". There is also a field "Location", but it is empty (it is filled in the staff client). What is the correct way to catalogue several different items that somehow belong together? If I have to make a seperate biblio for each item, how do I connect them? Patrons should be able to see that (for example) there are also audio cds when they see the record for the books (etc.). I hope it is clear what I'm trying to do, any help is appreciated.

2 3

Re: [Koha] unable to run apache after upgrade from 3.0 to 3.2
by Yatheesh Y 04 Jan '11

04 Jan '11

this is file apache error Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log" # with ServerRoot set to "" will be interpreted by the # server as "//var/log/apache2/foo.log". # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation (available # at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/etc/apache2" # # The accept serialization lock file MUST BE STORED ON A LOCAL DISK. # #<IfModule !mpm_winnt.c> #<IfModule !mpm_netware.c> LockFile /var/lock/apache2/accept.lock #</IfModule> #</IfModule> # # PidFile: The file in which the server should record its process # identification number when it starts. # This needs to be set in /etc/apache2/envvars # PidFile ${APACHE_PID_FILE} # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 # # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15 ## ## Server-Pool Size Regulation (MPM specific) ## # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_prefork_module> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # worker MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_worker_module> StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0 </IfModule> # event MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_event_module> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxRequestsPerChild 0 </IfModule> # These need to be set in /etc/apache2/envvars User ${APACHE_RUN_USER} Group ${APACHE_RUN_GROUP} # # AccessFileName: The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. # AccessFileName .htaccess # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ~ "^\.ht"> Order allow,deny Deny from all </Files> # # DefaultType is the default MIME type the server will use for a document # if it cannot otherwise determine one, such as from filename extensions. # If your server contains mostly text or HTML documents, "text/plain" is # a good value. If most of your content is binary, such as applications # or images, you may want to use "application/octet-stream" instead to # keep browsers from trying to display binary files as though they are # text. # DefaultType text/plain # # HostnameLookups: Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it'd be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # HostnameLookups Off # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog /var/log/apache2/error.log # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn On Mon, Jan 3, 2011 at 6:51 PM, Randall Rowe <r.rowe(a)lincolnlibraries.org>wrote: > It means that the file /etc/apache2/sites-enabled/koha has an error. > There is a closing </VirtualHost> without an opening <VirtualHost>. > Check the file and see if you can figure out the problem or post it and > we'll see what went wrong. > > Randy Rowe > Lincoln City Libraries I.T. > > -----Original Message----- > From: "Yatheesh Y" <yatheeshb(a)gmail.com> > Sent 1/3/2011 5:19:10 AM > To: Koha(a)lists.katipo.co.nz > Subject: [Koha] unable to run apache after upgrade from 3.0 to 3.2 > > after upgrading unable to run apache it gives following error > > what is this? > > > Restarting web server > apache2 apache2: Syntax error > on line 265 of /etc/apache2/apache2.conf: Syntax error on line 95 of > /etc/apache2/sites-enabled/koha: </VirtualHost> without matching > <VirtualHost> section > > > -- > ---------------------------- > Y.Yatheesh babu > Librarian > Shri Shakti College of Hotel Management > Venus Plaza Begumpet > Hyderabad-500 016 > 09966178388 > > _______________________________________________ > Koha mailing list http://koha-community.orgKoha@lists.katipo.co.nzhttp://lists.katipo.co.nz/m… > > -- ---------------------------- Y.Yatheesh babu Librarian Shri Shakti College of Hotel Management Venus Plaza Begumpet Hyderabad-500 016 09966178388

2 1

Re: [Koha] Editing library code
by Paul 03 Jan '11

03 Jan '11

At 09:23 AM 1/4/2011 +1300, you wrote: >On 4 January 2011 09:16, Paul <paul.a(a)aandc.org> wrote: > > Happy new year to all. > > > > Q: How do I edit our "Library Code" (koha-admin / branches / modify > > library), please? It does not appear in an editable text-box. > > > > [we originally - and erroneously - entered our code with the "Canadian > > prefix" Ca, as CaOPIACS, and now need only OPIACS.] > > >Hi Paul > >Happy new year, the short answer is, you can't. Not in the web >interface. Because to do so means updating a whole pile of things, the >borrowers table, items table, accountlines, reserves, the marc in >biblioitems etc. > >Does it actually matter, the description is displayed in most places ... ? Chris (and Jane), Thanks for replying, but not what we are looking for. The main reason to change is that a search at Library and Archives Canada <http://www.collectionscanada.gc.ca/illcandir-bin/illsear/l=0/c=1> relies on "OPIACS" and anyone searching for "CaOPIACS" cannot find us in the ILL system; also OPIACS is our "authority." What we have done is to set up a second library called OPIACS (totally identical to the first CaOPIACS), but now, despite being prompted to delete the first one, it just will not delete. So the question is - should I just grep CaOPIACS and replace wherever found, or is there a more elegant and reliable (non-gui) method? We do not care at this point about "borrowers table, items table, accountlines, reserves, etc" because we have reentered all our holdings (with OPIACS as required in the data) in the second (valid) library after purging all biblio and item records in the first, and so far have not entered any patron, budget, etc data -- so there is nothing to lose. I am sure we'll be purging again; we're in "pre-production mode" and refining our MarcEdit templates and mappings, and even 20,000 books only take a couple of minutes to delete and reload (plus zebra cron job.) Many thanks - Paul

2 1

Problem uploading MARC records
by Darla Grediagin 03 Jan '11

03 Jan '11

Good afternoon all, I have been getting the following message when I upload records to stage for import "SyntaxError: missing ; before statement" I have clean MARC records that I have used MARC edit to swap fields in. I have used the MARC edit feature to check for mistakes. If you have seen this statement, please let me know how you solved your problem. I am uploading records to a new install of Koha 3.00.06.010. Thanks in advance, -- Darla Grediagin District Librarian Bering Strait School District Unalakleet, Alaska Web Address : http://bssdonline.org/course/view.php?id=51 Blog: http://aklibrarian1.edublogs.org/ OPAC: http://opac.bssd.org:8181/cgi-bin/koha/opac-search.pl

1 0

Editing library code
by Paul 03 Jan '11

03 Jan '11

Happy new year to all. Q: How do I edit our "Library Code" (koha-admin / branches / modify library), please? It does not appear in an editable text-box. [we originally - and erroneously - entered our code with the "Canadian prefix" Ca, as CaOPIACS, and now need only OPIACS.] Thanks - Paul tired old sys-admin

3 2

Re: [Koha] Cannot save edited patron info in koha (but I can in mysql)
by Chris Cormack 03 Jan '11

03 Jan '11

Hi Marty As usual we also need to the version of Koha you are running, I can confirm editing patrons works fine in 3.2.2 for me. Also check your error logs if it isn't saving there is a good chance a database error is being thrown this will be in the error log. Chris On 27 Dec 2010 08:08, "Marty" <ontariowolf64(a)yahoo.com> wrote: This might be a permissions thing, but I am not sure. When I edit a patron's information I can change all fields I need to, but after the information has been 'saved' nothing has changed (When I am logged in as a superlibrarian) I can play in mysql and do a 'UPDATE borrowers SET city = 'Keswick' WHERE borrowernumber = 1234; This results in the changes info showing up in Koha, but I need this working in Koha, so the librarians can change patron info. As usual, any ideas are appreciated. Marty _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

3 8