- Koha - lists.katipo.co.nz

local server to deploy the website
by Nisreen Qabbani 05 Apr '15

05 Apr '15

Hello We are currently working Koha system and I have some questions, please answer them: How to transfer Koha from the local server to deploy the website How possible change Logo How to make a backup copy of the data? I have a problem after what we have created more library on the system menu does not show the names of the libraries on the OPAC Gratefully

2 2

Regarding web-service
by rocky bang 05 Apr '15

05 Apr '15

Hi koha, I have a databases of Students(Patrons) residing on suppose server A, and i have my koha 3.16 installed on suppose server B. I want to sync. the Students(Patrons) data into my koha database. As when i enter the data of Student(Patrons) in server A it should get sync. with the koha application on Server B. So kindly suggest how is it possible to do... Thanks in advance......

2 1

Koha Community Newsletter: March 2015
by kohanews 03 Apr '15

03 Apr '15

Fellow Koha users: The Koha Community Newsletter for March 2015 is here: http://koha-community.org/koha-community-newsletter-march-2015/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! Chad Roseburg Editor, Koha Community Newsletter

1 0

2 ways to mark an item "withdrawn"???
by Steven Nickerson 03 Apr '15

03 Apr '15

Hello everyone, I'm running a variety of Koha package versions on Debian, ranging from 3.16.2 to 3.18.5.1 and am hearing reports of issues with how items are marked as withdrawn. If you search in the staff client for an item and click on its title to go into the details you can mark an individual item 'withdrawn' in one of two ways: 1. Click on the "Edit" button along the top and select "Edit Items" in the pull-down. In the resulting window, click on the "Edit" link on the left-hand side of the item you want to withdraw. The first option reads "0 - withdrawn status" and in the pull-down I set it to "Withdrawn", and then click "Save changes" at the bottom. 2. The other way is to click on the "Items" tab on the left-hand side instead of the "Edit" button along the top. Selecting the "Items" tab gives you a list of your items and each item has a "Withdrawn?" line with a button that can be clicked to "Withdraw" it. So, now my question/issue.following the #1 process above doesn't seem to do anything at all to actually withdraw the item. It is still searchable in both Staff and OPAC clients and shows as "available" everywhere. I also checked in the database itself and the items.withdrawn field is not changed for the given item either. So what does marking the item status in this way actually do? Is this a "bug", and should it be updating the items.withdrawn field, perhaps? Following the #2 process above seems to have the expected results. Thanks in advance for anyone's thoughts! Steve

1 0

Publication date fields in Koha
by Steven Nickerson 02 Apr '15

02 Apr '15

Hello everyone, I'm trying to clean up some data from the RDA-related changes when we updated our framework a while back and have a few topics/questions regarding the publication fields (particularly the dates): - Can someone explain to me where the publisher, location, and date come from in the OPAC's search results? The reason I ask is that Koha seems to be pulling it from EITHER field 260 OR 264, is that correct? I've run a SQL query that shows I have the publisher information in only one of those fields for every record, but Koha still displays it. - Should I be "worried" that for some records I have the publication data in marcxml field 260 and for others I see it in 264, even for recently-added records within the same framework? Shouldn't the data show up in the same place if using the same framework? - How do the biblio.copyrightdate and biblioitems.publicationyear dates get populated? It doesn't seem like I have anything in 'biblioitems.publicationyear' at all.should I? And I see the biblio.copyrightdate for those records where the 264$c marcxml field is populated, but not the ones that have the publication information in the 260$c marcxml field. In case anyone else cares to look at publication date information in their own environment, here's a SQL query that shows you all of the various copyright date/publication year fields I mention above for ALL your biblios: SELECT items.biblionumber,items.itype,biblio.title,items.barcode,biblio.copyrightda te,biblioitems.publicationyear,biblio.frameworkcode,ExtractValue(marcxml,'// datafield[@tag="260"]/subfield[@code="c"]') AS marc260c, ExtractValue(marcxml,'//datafield[@tag="264"]/subfield[@code="c"]') AS marc264c FROM items LEFT JOIN biblioitems on (items.biblioitemnumber=biblioitems.biblioitemnumber) LEFT JOIN biblio on (biblioitems.biblionumber=biblio.biblionumber) ORDER BY items.biblionumber ASC Hope this makes sense.just trying to figure out where the publication data SHOULD be and why it doesn't seem consistent in my environment. Thanks in advance! Steve

2 1

Anyone using Firefox ESR (Extended Support Release) sucessfully for staff client access?
by Kearns, Sheila 02 Apr '15

02 Apr '15

I would like to hear from anyone who is using Firefox ESR (Extended Support Release https://www.mozilla.org/en-US/firefox/organizations/) for staff client access with Koha or who knows anything about Firefox ESR which is supposed to be in sync with the current Firefox release for general users. Our IT group only installs Firefox ESR (Extended Support Release) on computers it manages (https://www.mozilla.org/en-US/firefox/organizations/) It is supposed to be in sync with the current Firefox release for general users, but clearly it is not. Even the most simple elements of the staff client (Koha version 3.16.04) do not work in Firefox ESR. Just one example is that most dropdowns do not function . When using the general release of Firefox (version 36.04) I believe that my problems are specifically with using the staff client. I have tried using the OPAC with this version of Firefox and have not found any problems. I wish Chrome could be an answer to this problem, but our IT security group sees it as a security risk and will not allow it to be installed. This is how life in state government in the US goes.... Sheila M. Kearns Information Technology Librarian Vermont Dept. of Libraries 109 State St. Montpelier, VT 05609 802-828-6952 sheila.kearns(a)state.vt.us

3 2

Re: [Koha] Anyone using Firefox ESR (Extended Support Release) sucessfully for staff client access?
by Paul A 02 Apr '15

02 Apr '15

We use ESR (currently 31.4, although I'm aware that 31.6 has been released -- just not had time to see what they've changed) and have not experienced the problem (dropdowns) you appear to have. Note that we use Koha 3.8.24 in production, but never found browser problems during testing of 3.16/3.18. I would also tend to agree that Chrome poses problems, not sure if they're purely security, but here in Canada our privacy laws (PIPEDA in particular) are such that we also have not deployed Chrome. We do use Comodo's Dragon (a "secure" Chrome) for limited browser compatibility checks, but have noticed that most users appear to prefer Firefox ESR (which I don't think is fully coordinated with the latest "public" releases -- this whole question of stable, old stable, new stable, alpha, beta, whatever, is a jungle of differing opinions ;=}. ) Best -- Paul At 01:23 PM 4/2/2015 +0000, Kearns, Sheila wrote: >I would like to hear from anyone who is using Firefox ESR (Extended >Support Release https://www.mozilla.org/en-US/firefox/organizations/) for >staff client access with Koha or who knows anything about Firefox ESR >which is supposed to be in sync with the current Firefox release for >general users. > >Our IT group only installs Firefox ESR (Extended Support Release) on >computers it manages >(https://www.mozilla.org/en-US/firefox/organizations/) It is supposed to >be in sync with the current Firefox release for general users, but clearly >it is not. Even the most simple elements of the staff client (Koha version >3.16.04) do not work in Firefox ESR. Just one example is that most >dropdowns do not function . When using the general release of Firefox >(version 36.04) > >I believe that my problems are specifically with using the staff client. I >have tried using the OPAC with this version of Firefox and have not found >any problems. > >I wish Chrome could be an answer to this problem, but our IT security >group sees it as a security risk and will not allow it to be installed. >This is how life in state government in the US goes.... > > >Sheila M. Kearns >Information Technology Librarian >Vermont Dept. of Libraries >109 State St. >Montpelier, VT 05609 >802-828-6952 >sheila.kearns(a)state.vt.us > > >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

koha-common | mpm-itk on wheezy
by mourik jan heupink 02 Apr '15

02 Apr '15

Hi, Trying to create a new site on wheezy, koha-common 3.18.05.1: root@data:~# koha-create --create-db --marcflavor unimarc --zebralang en test I get: Koha requires mpm_itk to be enabled within Apache in order to run. Typically this can be enabled with: sudo a2enmod mpm_itk root@data:~# a2enmod mpm_itk ERROR: Module mpm_itk does not exist! root@data:~# apt-get install apache2-mpm-itk Reading package lists... Done Building dependency tree Reading state information... Done apache2-mpm-itk is already the newest version. So, it seems I have apache2-mpm-itk installed, however nothing *itk* is present under /etc/apache2/mods-available, and I cannot enable it. Any ideas?

4 6

lost barcode focus and jquery
by Marty Jongepier 02 Apr '15

02 Apr '15

I have an annoying issue with koha, not world shocking, but it would be nice to get a solution. What happens is that if we scan a barcode, either for checking in or checking out, the focus moves from the barcode box to the search box (iceweasel, firefox, chrome...). It is annoying, to say the least, to have to click in the check in box (or check out) after every item scanned. Cleaning the cache, as somebody suggested, does not help either. It used not to be like that. You could scan as many items as you wanted and the focus would stay on the check in box. Some people told me that it was easily solved with jquery, but I am not a programmer. I have tried a few things, but so far no code in jquery I have written has solved this. Could any of you maybe help us out, give us some sample code for this? Running Koha on Debian Wheezy. Thank you! Marty

3 3

MOREnet 2015 Annual Conference
by glaws 01 Apr '15

01 Apr '15

http://tinyurl.com/on6ygfy Call for presentations. Also a good opportunity for vendors. Although sadly I won't be attending a Koha or Evergreen (EG) presentation would be great. Many libraries in Missouri use EG and all have heard of Koha. / //"//MOREnet’s Annual Conference is a professional development opportunity that allows our attendees to pick the learning experience that’s right for you."/ -- Greg Lawson

1 0