- Koha - lists.katipo.co.nz

Etiquetas de lomo (Spine labels) en impresora Zebra !!!
by adalid＠tij.uia.mx 06 May '16

06 May '16

Iintento hacer pruebas de impresión de etiqutas de lomo para libros usando una impresora Zebra ZDesigner TLP 2824 Plus (ZPL) desde Koha usando las herramientas de impresión rapida y la de impresión por columnas sin ningún éxito. Según he visto en las listas de correo hay problemas de compatibilidad con esta marca y Koha. Para empezar no encuentro rollos de etiquetas para impresión termica de 1" de ancho por 1.5"de alto pero si las hay de 1.5"de ancho por 1: de alto. Según he visto en las preferencias de la impresora se le puede indicar que la impresión sea horizontal pero en Koha la etiqueta se despliega de manera vertical. Me interesa saber si alguien trabaja con esta marca y puede compartir experiencias o alguna recomendación que me ayude a tomar una decisión sobre si nos quedamos con ella o adquirimos alguna otra compatible con Koha. Reciban un cordial saludo, Felipe Adalid Ortiz Anzaldo Biblioteca Loyola Ibero Tijuana ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- Este correo electronico puede contener informacion confidencial y privilegiada, por lo que se prohibe el uso, reproduccion, retransmision o divulgacion no autorizada, parcial o total, de su contenido. Si usted no es el destinatario del presente correo, por favor notifiquelo al remitente mediante reenvio a su correo electronico y borrelo de inmediato. Para conocer el aviso de privacidad le pedimos acceder a la siguiente liga: http://www.iberotijuana.edu.mx/?doc=/avisoprivacidad/index.html -- Los acentos han sido removidos intencionalmente para facilitar la lectura del mensaje independiente a la codificacion del mismo.

1 0

Configuring Koha Defaults Documentation
by Peter Bradley 05 May '16

05 May '16

I've written a document about configuring Koha defaults that expands on the couple of sentences provided in the Koha Debian installation instructions. It's turned out to be a rather longer document than I expected and so is probably not suitable as a replacement for what is there already, but could perhaps be linked to. Can anyone tell me who I should approach to get the document made available, if it's considered suitable? Thanks Peter -- Yn rhedeg 5k Caerdydd i Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Corriendo el 5k de Cardiff para Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Running the Cardiff 5k for Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> JustGiving - Sponsor me now! <http://www.justgiving.com/tg-dyslexia>

2 1

Re: [Koha] Indexing MARC21 tag 264, why not use indexes pl and
by David Cook 05 May '16

05 May '16

Ugh, I hadn't seen https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14198 before... that's not good. I'm not 100% sure on those indexes, Zeno, I'd have to double-check Zebra files and Koha code, but yeah... we definitely want to change how 264 is being indexed. I think it should be indexed the same as 260. Maybe a bit differently due to some conditions tied to indicators, but yeah... ugh. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > Date: Wed, 4 May 2016 11:38:48 +0200 > From: Tajoli Zeno <z.tajoli(a)cineca.it> > To: koha list <koha(a)lists.katipo.co.nz> > Subject: [Koha] Indexing MARC21 tag 264, why not use indexes pl and > copydate > Message-ID: <5729C327.4060809(a)cineca.it> > Content-Type: text/plain; charset=iso-8859-15; format=flowed > > Hi to all, > > reading the log of 264 indexing setup, > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14198 > > I see that the final decision is to insert > all 264 data into indexes Providera and pv. > > As I have undestand, 264 doen't insert data into pl [place] and into > copydate [year]. > The comment speaks "Note that if you search again with pb only one > record appear. This is because the suggestion of LOC". > Can you link me the suggestion of LOC ? > I don't find it. > > And about the other two indexes, pl and copydate ? > Why we dont' do something like those line ? > > <index_subfields tag="264" subfields="a"> > <target_index>pl:w</target_index> > <target_index>pl:p</target_index> > </index_subfields> > <index_subfields tag="264" subfields="c"> > <target_index>copydate:w</target_index> > <target_index>copydate:s</target_index> > </index_subfields> > > > In my MARC21 records we are starting to use 264 and we don't use 260 > anymore [is an early adopter policy]. > > Thank you for everything. > Zeno Tajoli > > -- > Zeno Tajoli > / SVILUPPO PRODOTTI/ - Automazione Biblioteche > Email: z.tajoli(a)cineca.it Fax: 051/6132198 > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) > >

1 0

Koha support for offline checkin/checkout
by Hans Hvelplund Odborg 04 May '16

04 May '16

Does Koha support offline checkout/checkin? E.g. does Koha support "no block", "nb duedate", "return date" and "transaction date" fields (and sets the corresponding fields accordingly in the internal records). Hans Hvelplund Odborg VP Software Development e: h.h.odborg(a)bibliotheca.com t: +45 30 23 59 40 | m: +45 30 23 59 40 linkedIn | facebook | youtube | website Vallensbækvej 22A, 2. th. | DK – 2605 Brøndby | Danmark bibliotheca

2 1

Introduction and questions about defaults configuration
by Peter Bradley 04 May '16

04 May '16

Hi, I'm a retired librarian interested in some local community library projects. To this end I'm interested in being able to suggest Free/OSS library automation solutions to groups of people who may not normally think about using IT solutions because they either consider them to be too costly or too complicated. So what I'm planning to do is to set up a demonstration system on a redundant desktop box I've got kicking about the house. This will be a local system (i.e. will not have contact to the wider network) and so far I've got as far as installing Debian and Koha (via the Debian packages). MySQL is also installed. I do have a couple of questions, if I may. Having got as far as I mention above, the documentation then talks about configuring the defaults. There appear to be two: DOMAIN and INTRASUFFIX. What would I set DOMAIN to, if I wanted other computers on the local network to connect to Koha. Presumably I could always use 'localhost' for connections from the server itself and the server's NAT address (192.168.x.x) from other boxes, or have I misunderstood? But a nice domain name would be more impressive and less scary to the people I have in mind, so how would I go about setting that? And finally, what is INTRASUFFIX and what should I set it to? It means absolutely nothing to me. Many thanks for any help. Peter -- Yn rhedeg 5k Caerdydd i Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Corriendo el 5k de Cardiff para Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Running the Cardiff 5k for Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> JustGiving - Sponsor me now! <http://www.justgiving.com/tg-dyslexia>

4 7

Re: [Koha] Introduction and questions about defaults configuration
by Peter Bradley 04 May '16

04 May '16

First a thank you to all those who've responded. Merging all the replies I've managed to make some progress. Because my setup is going to be a private one for the LAN, I'm using my /etc/hosts file rather than DNS. So, I've now added the following line to my /etc/hosts file: 192.168.1.136 testlib.peredur.cym The library name is the one used in koha-create and the domain (peredur.cym) is the one set in my koha-sites.conf: DOMAIN=".peredur.cym" All the other values in that file have been left at their defaults. Now if I go to testlib.peredur.cym I get a message saying that Koha is undergoing maintenance, but if I go to testlib-intra.peredur.cym I still get the "server not found" error message. I imagine that this is because the subdomain has not been set up properly. Can anyone tell me how I can set this up properly for Koha? I'm on a brand new Debian 8 install with everything, including apache, set up using the defaults. Thanks again Peter -- Yn rhedeg 5k Caerdydd i Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Corriendo el 5k de Cardiff para Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Running the Cardiff 5k for Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> JustGiving - Sponsor me now! <http://www.justgiving.com/tg-dyslexia> El 04/05/16 a las 03:45, Ketan Kulkarni escribió: > Dear Peter, > > You can use ip address to access the koha server from LAN. > > If you have set up an internal nameserver, you can use name containing > your intranet's domain name. > > Ketan > > On Tue, May 3, 2016 at 6:06 PM, Peter Bradley<peredur.net(a)gmail.com> wrote: >> Hi, >> >> I'm a retired librarian interested in some local community library projects. >> >> To this end I'm interested in being able to suggest Free/OSS library >> automation solutions to groups of people who may not normally think about >> using IT solutions because they either consider them to be too costly or too >> complicated. >> >> So what I'm planning to do is to set up a demonstration system on a >> redundant desktop box I've got kicking about the house. This will be a >> local system (i.e. will not have contact to the wider network) and so far >> I've got as far as installing Debian and Koha (via the Debian packages). >> MySQL is also installed. >> >> I do have a couple of questions, if I may. >> >> Having got as far as I mention above, the documentation then talks about >> configuring the defaults. There appear to be two: DOMAIN and INTRASUFFIX. >> What would I set DOMAIN to, if I wanted other computers on the local network >> to connect to Koha. Presumably I could always use 'localhost' for >> connections from the server itself and the server's NAT address >> (192.168.x.x) from other boxes, or have I misunderstood? But a nice domain >> name would be more impressive and less scary to the people I have in mind, >> so how would I go about setting that? >> >> And finally, what is INTRASUFFIX and what should I set it to? It means >> absolutely nothing to me. >> >> Many thanks for any help. >> >> >> Peter >> -- >> Yn rhedeg 5k Caerdydd i Tomorrow's Generation >> <http://tomorrowsgeneration.co.uk/> >> Corriendo el 5k de Cardiff para Tomorrow's Generation >> <http://tomorrowsgeneration.co.uk/> >> Running the Cardiff 5k for Tomorrow's Generation >> <http://tomorrowsgeneration.co.uk/> >> JustGiving - Sponsor me now!<http://www.justgiving.com/tg-dyslexia> >> _______________________________________________ >> Koha mailing listhttp://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha

1 1

Indexing MARC21 tag 264, why not use indexes pl and copydate
by Tajoli Zeno 04 May '16

04 May '16

Hi to all, reading the log of 264 indexing setup, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14198 I see that the final decision is to insert all 264 data into indexes Providera and pv. As I have undestand, 264 doen't insert data into pl [place] and into copydate [year]. The comment speaks "Note that if you search again with pb only one record appear. This is because the suggestion of LOC". Can you link me the suggestion of LOC ? I don't find it. And about the other two indexes, pl and copydate ? Why we dont' do something like those line ? <index_subfields tag="264" subfields="a"> <target_index>pl:w</target_index> <target_index>pl:p</target_index> </index_subfields> <index_subfields tag="264" subfields="c"> <target_index>copydate:w</target_index> <target_index>copydate:s</target_index> </index_subfields> In my MARC21 records we are starting to use 264 and we don't use 260 anymore [is an early adopter policy]. Thank you for everything. Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

1 0

General IRC meeting tomorrow
by Brendan Gallagher 04 May '16

04 May '16

Hello all - General IRC meeting tomorrow Time converter for your time zone. http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… Agenda https://wiki.koha-community.org/wiki/General_IRC_meting_4_May_2016 Looking forward to seeing you there. -- Sent from Gmail Mobile

1 0

RCM Libary - Koha Implementation - Server Architecure Set-up Best Practices?
by Craig Butosi 03 May '16

03 May '16

Dear CW, I'm happy to announce that, after considerable deliberation, the Royal Conservatory of Music Library in Toronto is implementing Koha ILS, with a projected go-live date of 1 September 2016. In partnership with our IT department, the library is beginning the first stages of the implementation. Our IT director had a question at a recent meeting regarding common server architecture set-up. We are a small library (+/-170000 lines of data across 6 SQL tables) with a user base of about 600. The library has about 70000 items. He was curious about how Koha libraries who are hosting their own instance have set-up their server in terms of LAMP distribution and redundancy. For example, have you installed everything on one hardened server with some sort of RAID configuration and backup system, or do you have an application server, SQL server, and assets server, each with their own hardening, redundancy, and backup regiment? For vendors on the list who host Koha for client libraries, what is your common architecture set-up at your company? Any information or documentation referrals would be helpful, and off-list replies are welcome, too. Thanks all. Very much looking forward to the RCM being part of the Koha community. C Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca<http://www.rcmusic.ca/> Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.

1 0

Re: [Koha] Best practices for koha - journal migration using marcedit
by Paul A 03 May '16

03 May '16

At 09:39 PM 4/28/2016 +0000, Karl Holten wrote: >The MARC format has an individual record size limit of 99999 bytes, but >big serials in Koha can eclipse that size. The result is that really big >serials don't compile as valid MARC if you have a ton of items attached to >them. Thanks for the comment. I think that Indranil Das Gupta was proposing a direct intervention at MySQL level -- that's certainly what I am looking for. I'm uncertain as to _where_ the limit of 99999 bytes applies; it's the formal definition and MarcEdit probably respects that (I only have a very old version, and know very little about it, so cannot properly verify) but I don't think MySQL has any hard limits, nor has Koha unless I'm mistaken. Not at all sure about Zebra... I've just looked at one rather large record <http://opac.navalmarinearchive.com/cgi-bin/koha/opac-detail.pl?biblionumber…> but it has only 94 items (and MarcEdit swallows it, but it's only 31242 bytes, so nowhere near "the limit." We're looking at quite a few serial runs of over 100 years of monthly issues! already in ODS format so a direct import into MySQL might be the fastest way. I keep pushing this project to the back of the queue, but will have to face it sooner or later. Paul >You could try compiling to MARCXML, but I don't think the file importer >for Koha can handle MARCXML. > >The closest I got to creating a massive MRC serials record was to use >YAZ-MARCDUMP (http://www.indexdata.com/yaz/doc/yaz-marcdump.html) to >convert the big MARCXML record into MARC21. It seemed to compile but it >was hard to tell. It wasn't valid MARC after all, and I couldn't exactly >look at it in MARCEDIT. > >Regards, >Karl Holten >Systems Integration Specialist >SWITCH Inc >414-382-6711 > >-----Original Message----- >From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Paul A >Sent: Thursday, April 28, 2016 2:39 PM >To: koha <koha(a)lists.katipo.co.nz> >Subject: Re: [Koha] Best practices for koha - journal migration using marcedit > >At 08:24 PM 4/28/2016 +0530, Indranil Das Gupta wrote: >[snip > > > I would like to know how to covert excel data of journals especially > > > with large number of issues(having more than 600 issues) for each > > > journal. Tried using marcedit and it is giving error - 501 when > > > trying to covert mrk to mrc format. >[snip] > > > Is there any other way how I can covert this data to mrc format. > > > >Yes, if you do programming or have access to a programmer adept at > >handling MARC21 data, you can. > >If you have details, please make them available. We looked into this >(again after MarcEdit attempts), but ran into problems (from memory, >more_subfields_xml) ... and we've got about .25 million items to add ;=} > >Thanks -- Paul > >_______________________________________________ >Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz >https://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 2