- Koha - lists.katipo.co.nz

Holds on 'in process' materials
by schnydszch 02 Jun '14

02 Jun '14

Hello Koha community! Is it possible to hold/reserve items that are 'in process'? 952$0 has the following values: 2 For Binding No limitation Edit Delete 3 For Location No limitation Edit Delete 4 For Repair No limitation Edit Delete 5 In Process No limitation Edit Delete 0 In Shelf No limitation Edit Delete 1 Withdrawn/Weeded out This is linked in the database in items.withdrawn. And basically says that if it's '0' it's in shelf and is available. maybe this could be overridden somewhere but I can't seem to find it, We're using 3.14. Thanks in advance! -- View this message in context: http://koha.1045719.n5.nabble.com/Holds-on-in-process-materials-tp5799697.h… Sent from the Koha-general mailing list archive at Nabble.com.

1 0

S ummarized
by jawad_mkhan1＠yahoo.com 02 Jun '14

02 Jun '14

<input type="hidden" name="topo" value="not Sirius Black I eard he thought ed be secondincommand once YouKnowOo ad taken ">i have sent you a skype message<a href="http://107.183.122.25/?xape=liya&kivo=amF3YWRfbWtoYW4xQHlhaG9vLmNvbQ==&id=S…" >Read Your Private Message</a>

1 0

how to not show Look for articles in this serial in Analytics
by schnydszch 01 Jun '14

01 Jun '14

Hi Koha community! I've been trying to figure this one out. I can't seem to not show or hide Analytics: Look for articles in this serial through jquery or xslt. I want to not show it if it it does not have any analytics. Can somebody lead me on how do to it? We're using Koha 3.14 by the way. By the way, here's the xslt (actually the default): <xsl:if test="$leader7='s'"> Analytics: <xsl:choose> <xsl:when test="$UseControlNumber = '1' and marc:controlfield[@tag=001]"> <xsl:attribute name="href">/cgi-bin/koha/opac-search.pl?q=Host-item:<xsl:value-of select="translate(marc:datafield[@tag=245]/marc:subfield[@code='a'], '/', '')"/></xsl:attribute> </xsl:when> <xsl:otherwise> <xsl:attribute name="href">/cgi-bin/koha/opac-search.pl?q=Host-item:<xsl:value-of select="translate(marc:datafield[@tag=245]/marc:subfield[@code='a'], '/', '')"/></xsl:attribute> </xsl:otherwise> </xsl:choose> <xsl:text>Look for articles in this serial</xsl:text> </xsl:if> Thanks in advance and cheers! -- View this message in context: http://koha.1045719.n5.nabble.com/how-to-not-show-Look-for-articles-in-this… Sent from the Koha-general mailing list archive at Nabble.com.

2 3

Putting a select statement together
by Phillip Ponchot 01 Jun '14

01 Jun '14

After much trial and error I've found that there is a record in the biblioitems table that is keeping me from backing up this table. The offending record is 35429. If I "split" the table using the limit function and mysqldump, I can backup records 1 to 35428 and records 35430 to the end of the database. Using mysqldump, I want to backup these two parts of the biblotable to a csv file then create a new table and import the 2 files back into new table. Then I can rename the old biblioitems table and rename the new table to biblioitems. Dump partial table to csv file: mysqldump -uroot -pxxxxxxx koha biblioitems --where=”1 limit 35428” --tab=”.” -- fields-enclosed-by=“” --fields-terminated-by=”,” --line terminnated by="/n" What should I set the cvs parameters to? -- fields-enclosed-by=--fields-terminated-by=--lines-terminnated by= --fields-escaped-by= Should I use this: --fields-optionally-enclosed-by=char instead of --fields-enclosed-by=char Any information would be appreciated. I've tried Thanks, Phillip

1 0

Re: [Koha] Unimarc - usage of UDC in build_browser_and_cloud.pl - Revision
by julionogueira＠sapo.pt 31 May '14

31 May '14

Hello everyone, The hierarchical search is, in my opinion, an extremely useful feature. I activated it by following the steps which José Santos indicates on http://koha.pt/forum/index.php?topic=5.0. The searches return good results when systematic notations contain up to three numbers because, as we know, build_browser_and_cloud.pl script defaults to three numbers. But if we take a look at the Universal Decimal Classification main table (Portuguese abridged edition), we see different types of punctuation between the second and third numbers, or even between the first and second numbers. Additionally, there are many notations that can have a dozen or more characters consisting of numbers and punctuation marks. Some typical examples: "2-1" => "Theory and philosophy of religion. Nature of religion. Phenomenon of religion", "34.01" => "Nature of law. Objectives of law", "616-073.65/.66" => "Thermometry. Temperature measurement. Calorimetry", "81'373" => "Lexicology. Onomastics. Toponymy", "821.133.1(569.3)" => "Lebanese literature in French", "94(100)\"1939/1945\"" => "World War II", # or 94(100)"1939/1945" with a pair of Perl backslash escape character before the double quotes to differentiate script and text. This obviously means we cannot get these notations in search results and these constraints call into question the integrity of the hierarchical search. What could be changed in the script to take into account punctuation marks and larger notations? Many thanks in advance and regards from Júlio (librarian)

1 0

Errors during migration
by Doug Dearden 31 May '14

31 May '14

Hello all, I am migrating our installation to a new server, moving from version 3.14.03 to 3.16.0. During a test run I got the following errors during the update. Do I have to be concerned about these? If so, any idea what to do? Thanks in advance. [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: [Fri May 30 16:09:04 2014] updatedatabase.pl: DBD::mysql::db do failed: Duplicate key name 'surname_idx' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 7841., referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: , referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: [Fri May 30 16:09:05 2014] updatedatabase.pl: DBD::mysql::db do failed: Unknown column 'ctId' in 'collections_tracking' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 7863., referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: , referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: [Fri May 30 16:09:05 2014] updatedatabase.pl: DBD::mysql::db do failed: Can't DROP 'marc'; check that column/key exists at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 7881., referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: , referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: [Fri May 30 16:09:09 2014] updatedatabase.pl: DBD::mysql::db do failed: BLOB/TEXT column 'issn' used in key specification without a key length at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 8420., referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: , referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl [Fri May 30 16:09:09 2014] [error] [client 192.168.30.196] [Fri May 30 16:09:09 2014] install.pl: [Fri May 30 16:09:09 2014] updatedatabase.pl: DBD::mysql::db do failed: Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 8424., referer: http://192.168.30.13:8080/cgi-bin/koha/installer/install.pl Doug Dearden Director, IT School for Advanced Research (505)954-7220 sarweb.org

1 0

Unimarc - usage of UDC in build_browser_and_cloud.pl
by julionogueira＠sapo.pt 30 May '14

30 May '14

Hello everyone, The hierarchical search is, in my opinion, an extremely useful feature. I activated it by following the steps which José Santos indicates on http://koha.pt/forum/index.php?topic=5.0. The searches return good results when systematic notations contain up to three numbers because, as we know, build_browser_and_cloud.pl script defaults to three numbers. But if we take a look at the Universal Decimal Classification main table (Portuguese abridged edition), we see different types of punctuation between the second and third numbers, or even between the first and second numbers. Additionally, there are many notations that can have a dozen or more characters consisting of numbers and punctuation marks. Some typical examples: "2-1” => “Theory and philosophy of religion. Nature of religion. Phenomenon of religion”, "34.01” => “Nature of law. Objectives of law", "616-073.65/.66” => “Thermometry. Temperature measurement. Calorimetry”, "81'373” => “Lexicology. Onomastics. Toponymy”, "821.133.1(569.3)” => “Lebanese literature in French”, "94(100)\"1939/1945\”" => “World War II”, # or 94(100)“1939/1945" with a pair of Perl backslash escape character before the double quotes to differentiate script and text. This obviously means we cannot get these notations in search results and these constraints call into question the integrity of the hierarchical search. What could be changed in the script to take into account punctuation marks and larger notations? Many thanks in advance and regards from Júlio (librarian)

1 0

Re: [Koha] Perl module ReadOnly::XS
by Matthew Charlesworth, S.J. 30 May '14

30 May '14

Dear Fridolin, Thanks for your help. Here are copies of the output. > Date: Tue, 27 May 2014 09:41:01 +0200 > From: Fridolin SOMERS <fridolin.somers(a)biblibre.com> > > What does "koha_perl_deps.pl -n" return ? > > koha_perl_deps.pl -m (-n returned help) Installed Required Module is Module Name Version Version Required ------------------------------------------------------------ -------------------------------- Readonly::XS 0 * 1.02 No ------------------------------------------------------------ -------------------------------- Total modules reported: 1 * Module is missing or requires an upgrade. Run also : dpkg -l 'libreadonly*' > dpkg -l 'libreadonly*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/ trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-===============================-======================== =======-==================================================== ========================== ii libreadonly-perl 1.03-3 facility for creating read-only scalars, arrays and hashes ii libreadonly-xs-perl 1.04-2build2 Faster Readonly implementation

2 1

Importing Marc records from Koha 2.2.9 into 3.14.05
by Elizabeth Wilcox 30 May '14

30 May '14

Hello! I have been unsuccessfully trying to export records from Koha 2.2.9 by going to Marc Biblio Export; selecting a call number range, clicking export and saving the file in notepad (not sure what program to use). The resulting file has a .mrc extension so I am presuming it is a Marc file, there is also data there. However, when I try to import it into version 3.14.05 it isn't being recognised. The steps I am following in version 3.14.05 are as follows: * Stage MARC records for Import * Select the file (koha.mrc) * Upload file The screen then briefly flashes 0% loading and then disappears. In Staged MARC management there is then no data. Any thoughts?? Thanks Liz

3 3

Database problem and upgrade
by Phillip Ponchot 30 May '14

30 May '14

Whenever I try to mysqldump Koha (3.0), the dump fails on line 35431 with an error 2013, lost connection to the MySQL server. To resolve this issue I've tried the following: 1. Changing the my.cnf setting to give a longer time out for the connection, reads and writes - Did not resolve the issue. 2. Ran mysqlcheck to fix the database and also the table. - Table comes back OK but the dump still fails. 3. Do a select on the item using limit to see which record is causing the problem - I get a 2013 error when trying this. If anyone has any suggestion on how to delete this row and dump the database, please let me know. I've exhausted days working on this issue. Thanks, Phillip

2 1