- Koha - lists.katipo.co.nz

Internal server error when trying to open Budget or Funds
by Michael Kuhn 15 Sep '17

15 Sep '17

Hi When trying to click "Budgets" or "Funds" in Koha menu "Administration > Acquisition parameters" just a blank page appears, saying "Internal server error". Like this, of course, no new budget or fund can be added. I am experiencing this on Koha 16.11.1 as well as on Koha 17.05.1 (but not on Koha 16.11.4). I tried this as a user with the rights of a "superlibrarian" as well as with a user with fewer permissions. Has anyone experienced the same and can help, or should I maybe open a bug case? Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

2 5

Data not found
by Luis Moises Rojas 15 Sep '17

15 Sep '17

Hello everybody, Everyday in the morning, i have to run this script: Koha-rebuild-zebra -f -v -b -r {Koha instance} if i do not do this: we can not see any data, not search is found, etc. Why? -- *Luis Moisés Rojas P.*

2 1

Koha Data Migration and cover Image
by Chinmoy 15 Sep '17

15 Sep '17

1. How to migrate data from koha to excel format marc tagwise like 020a, 020c, 041a, 082a,082b, 100, 245a, 245b, 245c, 250, 260a,260b, 260c, 300a,440a, 500a, 650a, 700a,700b,700c,700d,700-4,942c etc. 2. If a book not available in www.amazon.com but available in Amazon India(www.amazon.in) then how can I get cover image of that book. In koha there is no option to select Amazon India services from Amazon Locale because here only American, British, Japanese, French, German and Canadian are available. In India various languages are there so various language books are available in www.amazon.in site but we cannot obtain the book cover in koha for local language books. 3. Another point is when we search a book in catalogue first shows the normal view and in normal view sequence is Title(245a), Subtitle(245b), Statement of Responsibility (245c) then By: Main Entry Personal name(100a), Contributor(s): (700a), (700b), (700c), Relator code(700-4). In normal view mode there is no punctuation mark i.e (: colon) between Title (245a) and Subtitle (245b). Also Statement of Responsibility (245c) and By: Main Entry Personal name(100), Contributor(s): (700a), (700b), (700c), Relator code(700-4) both i.e 245c and 700abc are meaningless because same thing appears two times. I think (245c) is not required to display in Normal view. When we setup ISBD Template we put there punctuation mark and at the time of data entry we do not add punctuation mark as a result in Normal view mode Title , Subtitle, SOR are coming without punctuation mark and it is very confusing to a new user. Maximum Library authority do the data entry job by non Librarian worker and they do not know the punctuation mark so it is better to setup with punctuation mark at the time of display page designing. Also after (260a) :colon; (260b) ,comma ; (260c).dot and after pagination (300a) p. may be inserted. It is my earnest request to the concern persons to look into the matter for betterment of koha services. Thanking you, Chinmoy Ghosh. -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html

4 5

Call for News: September 2017 Newsletter
by kohanews 15 Sep '17

15 Sep '17

I'm collecting news for the September newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Koha Accession Register format as Per Indian GFR2017 rule
by vinod mishra 15 Sep '17

15 Sep '17

Dear All Please find here a link for very useful Koha report format. Report Name: Accession Register Report/Format as per Indian GFR2017 Rule ( http://mishravk.com/wp-content/uploads/2017/09/acquisition7.txt) Purpose: This report will help all Libraries to print the accession record of a book and maintain the register as per Indian GFR2017 prescribed accession register format ( http://mof.gov.in/the_ministry/dept_expenditure/GFRS/GFR2017.pdf) You may find more report as per Indian Libraries requirements at: http://mishravk.com/koha/koha-reports/ <https://l.facebook.com/l.php?u=http%3A%2F%2Fmishravk.com%2Fkoha%2Fkoha-repo…> With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 Website: http://mishravk.com/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

1 0

Verticial menu
by Luis Moises Rojas 14 Sep '17

14 Sep '17

Hello everybody. I few days ago, i wrote about problem with the MAIN MENU. This menu, is displayed normally horizontal, but i have vertical, like this Circulation Patrons Search . . . where should be: Circulation Patrons Search ... I deleted the browser cached and still nothing happens. Any idea pls, because we do not want to reinstall Koha again. Thanks. -- *Luis Moisés Rojas P.*

4 4

Firefox Screenshots
by George 14 Sep '17

14 Sep '17

Hello everyone, Firefox updated on my computer last night and, without asking me if I wanted it or not, the new Firefox has "Firefox Screenshots" was enabled by default. If you haven't seen this new built-in feature yet, one of its functions is to allow you to very easily save screenshots to an unsecured location in the cloud. Naturally anything that allows staff to, potentially, save confidential data to an unsecured location in the cloud causes me great concern and the only advice I can find from Mozilla is just an explanation of how to disable this new feature by turning it off using "about:config." Since I have to worry about staff at 51 different library locations with 2-20 staff computer per location, tuning this off using about:config is not feasible for me. My concern here isn't that staff will purposefully start taking screenshots like crazy and sharing them with their friends but that they will take a screenshot to share a problem or a concern with me or other staff and click on the button that saves the screenshot to the cloud without realizing that anyone with the URL will be able to access the screenshot. So, I looked at what is happening in Koha when you click on the screenshot icon or by right clicking on "Take a screenshot" and figured out that some jQuery would stop staff at all of our libraries from using this new feature. This should prevent anyone from accidentally saving confidential information somewhere where they shouldn't. The only thing that I don't like about this method of disabling this feature is that, if someone does try to use Firefox Screenshots while in the Koha staff client, they will probably end up with a pop-up message on their screen saying "Woah! Firefox Screenshots went haywire." If anyone else wants this jQuery for this, it's on the community wiki at https://wiki.koha-community.org/wiki/JQuery_Library#Disable_.28more-or-less… See you all later, George -- George Williams NExpress Coordinator Send NExpress support e-mails to nexpresshelp(a)nekls.org

3 2

Returning borrowed book error
by Luis Moises Rojas 14 Sep '17

14 Sep '17

Hello everybody, We are having a new problem (New because yersterday was working), when a user want to return a borrowed bool it says: book can not be return. Any idea, pls? Thanks to all -- *Luis Moisés Rojas P.*

3 3

Re: [Koha] Fwd: Unable to reindex after massive upgrade
by Tim Young 14 Sep '17

14 Sep '17

Previously, I noted that I was not able to reindex. I tracked it down to the following. My biblio_metadata file wasempty, and therefore my reindex could not retrieve any biblio information. Now that I know what to look for, there was this error during the upgrade: [Thu Jun 22 22:29:11 2017] updatedatabase.pl: DBD::mysql::db do failed: *Cannot add or update a child row: a foreign key constraint fails* (`kohadb2015`.`biblio_metadata`, CONSTRAINT `biblio_metadata_fk_1` FOREIGN KEY (`biblionumber`) REFERENCES `biblio` (`biblionumber`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement " [Thu Jun 22 22:29:11 2017] updatedatabase.pl: INSERT INTO biblio_metadata ( biblionumber, format, marcflavour, metadata ) SELECT biblionumber, 'marcxml', 'CHANGEME', marcxml FROM biblioitems; I think this is where the upgrade failed; the newly created biblio_metadata has a foreign key: *CONSTRAINT `biblio_metadata_fk_1` FOREIGN KEY (biblionumber) REFERENCES biblio (biblionumber) ON DELETE CASCADE ON UPDATE CASCADE* When doing the bulk migration, we probably need to turn off foreign key checks before doing the update: SET FOREIGN_KEY_CHECKS=0; And then put them back once it has been done: SET FOREIGN_KEY_CHECKS=1; [update having solved the problem] This glitch was caused primarily by a few different things: 1) a previous update to the mysql did not upgrade all the users. The debian-sys-maint user was somewhat broken. Various things that depended on this user failed during the upgrade. 2) We have some broken data in our install. At one time we had a number of records get corrupted, which resulted in records that do not have the records corresponding to their foreign keys. 3) I did not immediately notice the importance of the error logs (above) telling me that my data had not been copied over. To fix my mysql issues with debian-sys-maint, I ended up running # mysql_upgrade --force -uroot -p This repaired the mysql users table. Being a wise sysadmin, I had a backup database [kohadb2015] which had our original data. To populate that table with the marc data, I ran the following sql: SET FOREIGN_KEY_CHECKS=0; INSERT INTO koha_opac.biblio_metadata ( biblionumber, format, marcflavour, metadata ) SELECT biblionumber, 'marcxml', 'CHANGEME', marcxml FROM kohadb2015.biblioitems; UPDATE biblio_metadata SET marcflavour = (SELECT value FROM systempreferences WHERE variable="marcflavour"); SET FOREIGN_KEY_CHECKS=1; After that, I was able to reindex fine. When the reindex was complete, the pages would still not load. I was getting an error rendering the page. Can't call method "branchname" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 1627 I am not entirely sure if this is yet another problem with my data, or if I have some odd setting somewhere. What I did, however, was to modify the koha code to avoid it blowing up: vi /usr/share/koha/lib/C4/Biblio.pm +1627 if ( $tagslib->{$tag}->{$subfield}->{'authorised_value'} eq "branches" ) { *if(defined(Koha::Libraries->find($value)))* { return Koha::Libraries->find($value)->branchname; } - Tim Young

2 5

Re: [Koha] Koha Digest, Vol 143, Issue 18
by Suresh Kumar Tejomurtula 14 Sep '17

14 Sep '17

Hi, As suggested already you can use, but I noticed that sort1 and sort2 are there in acquisition also. Hence if you rename anything here, it will reflect in acquisition module too.... I used unused fields in borrower table and renamed them as per my need in opac and intranet using jquery statements. Regards T Suresh Kumar > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Sep 2017 08:12:15 +0530 > From: Ashok Francis <ashokfrancis.tgs(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Patron: Sort 1 as Grade and Sort 2 as Section > Message-ID: > <CAHKLWPL3ByR+r01pJ_jMunyYDwP3NPsa-6mtdFoNXPn0O2r9aQ(a)mail.gmail. > com> > Content-Type: text/plain; charset="UTF-8" > > Dear All, > > I am working in a school with koha library software. Is it possible to > change SORT 1 as Grade and SORT 2 as Section in the patron? If yes, can you > please guide me to change SORT 1 as Grade and SORT 2 as Section. I will be > thankful to you. > > Ashok. > > > ------------------------------ >

1 0