- Koha - lists.katipo.co.nz

OPAC not working
by shankar reddy Kolle 17 Nov '15

17 Nov '15

Dear sir/Madam We have installed latest version of Koha using package method, meanwhile we also tried to install the Dspace on the same server, but not succeeded. Now the Koha OPAC is not working. Please help me to figure out the problem and give the solution for the problem. hope i may have the solution soon. Thanking you, yours sincerely Dr. Shankar Reddy

2 1

Is anyone using EAD for finding aids
by jtate 16 Nov '15

16 Nov '15

My agency is looking into using EAD for our finding aids. Is anyone already using it and how is it working for you? -- View this message in context: http://koha.1045719.n5.nabble.com/Is-anyone-using-EAD-for-finding-aids-tp58… Sent from the Koha-general mailing list archive at Nabble.com.

2 1

Re: [Koha] Merge.pl koha
by Tajoli Zeno 16 Nov '15

16 Nov '15

Hi Elif, Il 14/11/2015 08:05, Elif Demir ha scritto: > I want to merge one biblio to many biblios. in koha system , merge.pl > <http://merge.pl> , it can be done only "merge one biblio to another one > biblio". Can you help me? How can i do this multiple merge? you need to wait 3.22 release: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8064 Generaly speaking it is better do send questions to mailing list instead to a single person. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

1 0

Invitation for Libraries using Koha to participate in the 2015 Library Automation Perceptions survey
by Marshall Breeding 16 Nov '15

16 Nov '15

To all libraries using Koha: I'm collecting data for the 2015 International Library Automation Perceptions survey. This survey, now in its ninth annual iteration, provides an opportunity for libraries to register their perceptions of the strategic automation products they use, organizations that provide these products, and the quality of support delivered. The survey also probes at considerations for migrating to new systems and the level of interest in open source products. As open source software supported both by the general community and by a variety of different service firms, some special considerations apply to Koha. In the libraries.org directory, Koha is represented by a combination of the name Koha and the primary support organization involved. (For example Koha - Catalyst IT, Koha -- ByWater Solutions). Libraries relying entirely on community support or internal resources are represented as Koha - Independent. If there are any special support arrangements not covered by these conventions, just mention that in the comments area of the survey. In this way the survey will be able to reflect both the functionality of the Koha software and the quality of support provided. This model of representing libraries using Koha isn't ideal, but is a pragmatic approach that aggregates all users of Koha while also segregating the different support scenarios. While the numeric rating scales support the statistical results of the study, it's the comments offered that provide the most insight into the current state of library automation satisfaction. Comments will be published in the survey results, redacted to conceal text that might identify the individual or organization responding. The raw data for the survey will not be shared, but reports are available that provide a variety of ways to view results. Please help your fellow librarians who might be in the process of evaluating library automation options by responding to the survey. Any information regarding vendor performance and product quality can be helpful when making strategic decisions regarding automation alternatives. A large number of responses strengthen the impact of the survey and the subsequent report. If you have responded in previous years, please respond again this year to help identify any trends regarding improvement or worsening of the products or support services. For more information about the survey, for instructions on how to participate, and to see results of previous year's survey reports, see: http://librarytechnology.org/web/breeding/AutomationSurvey/ I hope that all libraries using Koha will respond. Feel free to forward this request to any other library-related list. Please let me know if there are any questions regarding the survey. Marshall Breeding Editor, Library Technology Guides www.librarytechnology.org Marshall.breeding(a)librarytechnology.org twitter.com/mbreeding

1 0

Koha parameters/implementation back-up
by Pedro Amorim 16 Nov '15

16 Nov '15

Hello all, I was wondering if there is an easy way to back-up all the parameters from global preferences made in Koha (what database table, for example). As anyone done this before that can provide with some guidance? Besides global system preferences, any light on how to repeat the same process for framework MARC structure, koha to MARC mapping and pretty much everything that has to do with implementation (data/records not included). Thank you.

2 1

Errors upgrading from 3.18.11 to 3.18.12
by Bob Elgie 15 Nov '15

15 Nov '15

I hoped/expected that someone else would post about these errors I received when upgrading from 3.18.11 to 3.18.12. Since no one has ... My system: 1 instance of koha-common running under Linux Mint Debian 2, mysql-server 5.5.46-0+deb8u1, apache2 5.5.46-0+deb8u1 This is a personal-use installation of koha that, despite the errors below, appears to function properly. Screen-grab from apt-get: Preparing to unpack .../koha-common_3.18.12_all.deb ... Stopping Zebra server for mint SIP server for mint not running. Unpacking koha-common (3.18.12) over (3.18.11) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up koha-common (3.18.12) ... Installing new version of config file /etc/koha/zebradb/ccl.properties ... Installing new version of config file /etc/koha/zebradb/marc_defs/unimarc/biblios/biblio-koha-indexdefs.xml ... Installing new version of config file /etc/koha/zebradb/marc_defs/unimarc/biblios/biblio-zebra-indexdefs.xsl ... Starting Zebra server for mint Upgrading database schema for mint DEV atomic update: hourlyloans.sql C4::Installer::load_sql returned the following errors while attempting to load /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/hourlyloans.sql: ERROR 1060 (42S21) at line 1: Duplicate column name 'lengthunit' DEV atomic update: oai_sets.sql C4::Installer::load_sql returned the following errors while attempting to load /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/oai_sets.sql: ERROR 1062 (23000) at line 35: Duplicate entry 'OAI-PMH:AutoUpdateSets' for key 'PRIMARY' Question: Do these errors need to be rectified? If so, I'm comfortable working at the command line in mysql. Thanks! Bob Elgie

2 1

(no subject)
by celikbas＠itu.edu.tr 14 Nov '15

14 Nov '15

The original message was received at Sat, 14 Nov 2015 17:47:14 +0530 from 157.186.0.15 ----- The following addresses had permanent fatal errors ----- koha(a)lists.katipo.co.nz ----- Transcript of the session follows ----- ... while talking to host lists.katipo.co.nz.: >>> DATA <<< 400-aturner; %MAIL-E-OPENOUT, error opening !AS as output <<< 400-aturner; -RMS-E-CRE, ACP file create failed <<< 400-aturner; -SYSTEM-F-EXDISKQUOTA, disk quota exceeded <<< 400

1 0

Call for News: November Newsletter
by kohanews 14 Nov '15

14 Nov '15

Fellow Koha users ~ I'm collecting news for the November 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. -- Chad Roseburg

1 0

Paris
by BWS Johnson 14 Nov '15

14 Nov '15

Salvete! What a tragedy in Paris tonight! "Il pleure sans raison." Sincerely, Brooke

1 0

Re: [Koha] Searching in Arabic
by David Cook 13 Nov '15

13 Nov '15

Just fixing the subject line to aid people in discovering my response... See my real reply below. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > From: David Cook [mailto:dcook@prosentient.com.au] > Sent: Friday, 13 November 2015 9:44 AM > To: 'koha(a)lists.katipo.co.nz' <koha(a)lists.katipo.co.nz> > Cc: 'Tajoli Zeno' <z.tajoli(a)cineca.it>; 'jlambertson(a)sqcc.org' > <jlambertson(a)sqcc.org> > Subject: RE: Koha Digest, Vol 121, Issue 18 > > Hi Jesse: > > I've read the response from yourself and others, and I agree with Zeno that it > would be wise to open a bug on http://bugs.koha-community.org/bugzilla3/. > > The reason the keyword searching works is because all text nodes in a MARC > record are indexed in the "Any" (ie Keyword) index. The 880 field itself gets > no special handling in the current version of biblio-zebra-indexdefs.xsl, which > is why searching indexes other than Keyword doesn't work when you're > searching for Arabic text stored in the 880. > > In my opinion, an elegant solution could theoretically be achieved by > something like the following: > > <xsl:template match="marc:datafield[@tag='880']"> > <xsl:variable name="linkage" > select="substring(marc:subfield[@code='6']",1,3)"/> > <xsl:call-template name="$linkage" /> > </xsl:template> > > However, we don't current use named templates in biblio-zebra- > indexdefs.xsl, so that's not possible at the moment. The above is just a > hypothetical suggestion that would be easier to maintain and extend. > > Glancing at http://bugs.koha- > community.org/bugzilla3/show_bug.cgi?id=14217, you might try something > like the following in biblio-koha-indexdefs.xml in Koha 3.22: > > <index_subfields tag="880" subfields="a" > condition="substring(marc:subfield[@code='6']",1,3) = 245"> > <target_index>Title-cover:w</target_index> > <target_index>Title-cover:p</target_index> > <target_index>Title-cover:s</target_index> > <target_index>Title:w</target_index> > <target_index>Title:p</target_index> > <target_index>Title:s</target_index> > </index_subfields> > > Unfortunately, this convention requires you to make a block for every index > linkage you need. That is, you'll need to do the same for 245, 260, 100, etc. > It'll also be more difficult to maintain in the long-run, so it would be wise to > locate the 880 near its linked field in the biblio-koha-indexdefs.xml file, so as > to prevent deviations between how the fields are indexed. > > Of course, since you're probably only trying to provide access to a handful of > commonly used fields, this shouldn't be too laborious of a process. > > It is possible to fix your situation one way or another, Jesse. XSLT is powerful > and DOM indexing is quite flexible as a result. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St, Ultimo, NSW 2007 > > > > -----Original Message----- > > Date: Thu, 12 Nov 2015 16:05:48 +0100 > > From: Tajoli Zeno <z.tajoli(a)cineca.it> > > To: Jesse Lambertson <jlambertson(a)sqcc.org> > > Cc: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> > > Subject: Re: [Koha] Searching in Arabic > > Message-ID: <5644AACC.5020607(a)cineca.it> > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Hi Jesse, > > > > > > Il 12/11/2015 15:16, Jesse Lambertson ha scritto: > > > I think this is because 880 is not in the default indexing list. > > > It seems to me that associated linked 880 fields for title (245), > > > author( > > > 100 and 700) as well as series (490 and 830) should return results > > > searched in Arabic as long as we add 880 to the list. > > > > > > Am I incorrect in that assumption? > > > > No, sorry. > > You assumption is correct. > > You need to change the default indexing setup to index your 880 that > > are probably like: > > 880 10$6245-01/(3/r$a[Arabic chars] > > > > I suggest you to open a bug here: > > http://bugs.koha-community.org/bugzilla3/ > > with description of the problem and 10-20 records from your catalogue > > to do test. > > > > Do you want to try to fix your self ? > > Well, you need to understand how indexing works with Zebra. > > > > Start on chapter 13 of the manual: > > http://translate.koha-community.org/manual/3.20/en/searching.html > > > > Read the basic on Zebra documentation: > > http://www.indexdata.com/zebra/doc/record-model-domxml.html > > (Tip: configuration language of the files is XSLT, so you need to > > learn a basic of it). > > > > The 3 basic files are: > > etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml > > etc/zebradb/xsl/koha-indexdefs-to-zebra.xsl > > etc/zebradb/marc_defs/marc21/biblios/biblio-zebra-indexdefs.xsl > > > > The real working file is biblio-zebra-indexdefs.xsl In its head you > > can read: > >  > > > > You probaly need to backport this fix from master to 3.20: > > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14217 > > > > and insert many condition in biblio-koha-indexdefs.xml about 880 with > > specific values in $6 > > > > Not an easy work. > > > > Bye > > Zeno Tajoli > > > > > > > > > > > > -- > > Zeno Tajoli > > /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche > > Email: z.tajoli(a)cineca.it Fax: 051/6132198 > > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) > > > >

3 4