- Koha-devel - lists.koha-community.org

Barcodes problem
by ZANG 23 Jan '08

23 Jan '08

Dear list I am using a 14 digit barcode and cannot get it to scan. The scanner does not respond at all. I have tried all the different types available (Codabar, 3of5, 5of9, code128). I also cannot get the scaling to work. Are these known issues? I will appreciate your help on this. Zang

2 1

What Server Specs do YOU run Koha on?
by Joshua Ferraro 23 Jan '08

23 Jan '08

Hiya folks, Recently we've had a lot of people ask about recommended server specs for Koha. This is a tough question to answer because it comes loaded with assumptions about the size of the collection, transaction load, etc. So I was wondering if those of you who are running Koha in your libraries could just post a quick email to the list saying how large your collection is, number of transactions, what server specs you use (proc speed, RAM, disk space, etc.), and how the performance has been for you ... and then we can compile that as part of the FAQ. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

6 5

ANN: Koha Community Website announces Plone Theming Contest
by darcihanning 22 Jan '08

22 Jan '08

Koha Plone Website Contest In conjunction with the upcoming Koha 3.0 release, the Koha community is proud to announce a Plone Skinning/Theming contest for a new Koha community website. Koha is an open-source integrated library system application with users from around the world and the Koha community has chosen Plone as its CMS for the Koha community website. Contest Prizes Grand Prize for the selected Plone skin/theme is $2,500 USD and full design and implementation credit given on the Koha website. Honorable mentions will be announced via press release with contact information included (if so desired). Complete details are available here: http://koha.org/about-koha/news/nr1199901668.html Please pass along this announcement to any potentially interested folks! :) Cheers! Darci Hanning -- View this message in context: http://www.nabble.com/ANN%3A-Koha-Community-Website-announces-Plone-Theming… Sent from the Koha - Dev mailing list archive at Nabble.com.

7 10

new acquisition module [announce]
by Paul POULAIN 21 Jan '08

21 Jan '08

Hello folks, Just to let you know : BibLibre (sponsored by SAN-OP), has started to develop a new acquisition module, best suited for larger libraries than the one we have in Koha atm. The specs are written in French. If someone want to have them for translation, let me know (22 pages) To summarize : - divide budget in groups and sub-groups (not only 1 level as we have now) - the library can ask an RFP before the official order. - the bookseller can fill the RFP online if wanted - the orders can be done from scratch, from existing catalogue or from suggestions (as in koha 3.0), but also from an external data source (iso2709 file) - each document bought is attached to group, sub-group, expected audience, expected branch - librarians can be responsible for acquisition on a given group/sub-group - the module will provide a lot of features to plan how the library will spend money, and analyze how they have spent it : group, sub-group (yearly & monthly), audience, branch BibLibre has hired a new developer (Olivier Saury) to work on that (and only on that). The DB schema is done. The coding has started. We will use only Koha tools & it will be fully integrated with Koha (so developed in English, unlike the specs). The 3.0 acquisition module will stay available, for smaller libraries, the new one will be activtaable by a syspref. We also hope to be able to have this module as standalone, for libraries happy with their ILS, but unhappy with it's acquisition module. But the module may not be available as standalone app in 1st version. I don't think I'm missing something, but any question welcomed. -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 2

Koha User Group meetings: questions
by Deb Bergeron 18 Jan '08

18 Jan '08

Hi! We're putting together a Koha User Group in the U.S. If any of you have either attended or helped organize a Koha user group anywhere, can you please give me some ideas on how you: a. formed the group b. what was/is the content of the meeting c. what type of topics did you discuss d. how long was the meeting I'm happy to discuss this either on or off the list. Thank you in advance for any help and suggestions you may have! Sincerely, Deb Bergeron -- Deb Bergeron <mailto:bergeron@macalester.edu> System Admin: User Support CLIC Consortium <http://clic.edu> 1619 Dayton Avenue, Suite 204A Saint Paul, MN 55104 O:*651.644.3878* C:*651.487.7609* F:651.644.6258

1 0

Fwd: [Koha-devel] Custom searches in opac
by Peter Hartmann 18 Jan '08

18 Jan '08

---------- Forwarded message ---------- From: Peter Hartmann <peter(a)hartmanncomputer.com> Date: Jan 17, 2008 8:29 PM Subject: Re: [Koha-devel] Custom searches in opac To: Henri-Damien LAURENT <laurenthdl(a)alinto.com> Can I make the search criteria not so strict? I did notice that with my previous 952p test that partial searches didn't work. Searching for '6' did not return results although that are many sixes in barcodes. These 521a fields have spaces in them as well which may be causing a problem. Examples: PreK. - K 4 / 3 - 7 Not sure what the second one indicates....but that's the librarians doing. With name="operator" value="contains": Searching for 'prek' gives 7 results even though there are man more there. Searching for any of the numbers doesn't work. name="operator" value="=" Single numbers and floating point numbers work but not 'Prek'. Is there some way of combining "=" and "contains"? I tried using 'or' like this but no good: <input type="hidden" name="operator" value="contains" or "=" /> and also two separate lines with each variation.... thanks, Peter here it is again... <th><label for="level">Reading Level:</label></th> <td><input type="hidden" name="marclist" value="521a" /> <input type="hidden" name="and_or" value="and" /> <input type="hidden" name="excluding" value="" /> <input type="hidden" name="operator" value="contains" /> <input type="text" id="level" name="value" /> </td> </tr> On Jan 17, 2008 7:33 PM, Peter Hartmann <peter(a)hartmanncomputer.com> wrote: > Hey Henri-Damien , > That's what this bit of code originally looked like. Just for > kicks I changed it to 952b -barcode- and searched for a valid barcode. > It does indeed work, just not for 521a which is populated in the > aforementioned table . So does this mean that I have to link 521a > with a koha-marc? Sorry this sliding in to userville. > > Thanks, > > Peter > > > > > On Jan 17, 2008 6:04 PM, Henri-Damien LAURENT <laurenthdl(a)alinto.com> wrote: > > Hi, > > Peter Hartmann a écrit : > > > Hey, I'm looking to set up a custom search in the npl opac for > > > 'Reading Level". This is a big one for elementary schools. This > > > information is under 521a in the marc records that I have imported > > > into koha database. This mysql query lists the information in a table > > > that I need: > > > > > > select * from marc_subfield_table where tag = 521 and subfieldcode = 'a'; > > > > > > Any ideas how I could search this as a temporary table from the opac. > > > Or is there an easier way? > > > > > > > > > <th><label for="level">Reading Level:</label></th> > > > > > > <td><input type="hidden" name="marclist" > > > value="marc_subfield_table.subfieldvalue" /> > > > > > try this here : value="'521a'" It should work. > > > > > <input type="hidden" name="and_or" value="and" /> > > > <input type="hidden" name="excluding" value="" /> > > > <input type="hidden" name="operator" value="contains" /> > > > <input type="text" id="subfieldvalue" name="value" /> > > > </td> > > > </tr> > > > > > > > > > this is how far I've gotten in altering the opac-search.tmpl file for > > > the npl template. It doesn't work. > > > > > So long. > > -- > > Henri-Damien LAURENT > > >

1 0

Custom searches in opac
by Peter Hartmann 17 Jan '08

17 Jan '08

Hey, I'm looking to set up a custom search in the npl opac for 'Reading Level". This is a big one for elementary schools. This information is under 521a in the marc records that I have imported into koha database. This mysql query lists the information in a table that I need: select * from marc_subfield_table where tag = 521 and subfieldcode = 'a'; Any ideas how I could search this as a temporary table from the opac. Or is there an easier way? <th><label for="level">Reading Level:</label></th> <td><input type="hidden" name="marclist" value="marc_subfield_table.subfieldvalue" /> <input type="hidden" name="and_or" value="and" /> <input type="hidden" name="excluding" value="" /> <input type="hidden" name="operator" value="contains" /> <input type="text" id="subfieldvalue" name="value" /> </td> </tr> this is how far I've gotten in altering the opac-search.tmpl file for the npl template. It doesn't work. Thoughts anyone? Thanks, Peter

1 0

Installation on Solaris
by Evelio Martínez 17 Jan '08

17 Jan '08

Hello everyone! I would like to know if someone tried to install KOHA on this platform: - OS: Solaris - Database: Oracle - Web Server: websphere I suppose minimum problems could appear on Solaris and Websphere, but there is a medium probability to have problems with Oracle database, concerning reserved word on columns names, tables names or similar things. I have search on google, have read some posts and also http://www.koha.org/download/other-os.html Has anyone first hand info about the previous configuration? Thanks in advance -- Evelio Martínez

2 3

Status of Koha 3 Translations (two weeks remaining)
by Joshua Ferraro 17 Jan '08

17 Jan '08

Hi all, Since the announcement on January 8th (8 days ago) that Koha 3 is ready to be translated, we've heard from dozens of translators around the globe who have collectively agreed to translate Koha into over 26 languages! So first off, a big round of applause to all who have volunteered! Just to give you all an update, I just approved all pending translations, and we're up to about 16% completion for all translations. Some are finished, and some haven't been started yet. Please bear in mind the deadline for submissions is 1 February, just two weeks away! I'll send another reminder in about a week. In the meantime, happy translating everyone! Finally, for those who would like to translate Koha into their langauge, and missed the original email, here are the relevant instructions (most folks seem to be using the web-based translation manager FYI): 1. Please take a look at http://translate.koha.org. Some translations already exist; please consider taking over an existing translation rather than starting a fresh one, unless the existing one is un-usably poor :-) 2. Please post your intent to translate Koha to the koha-translate list: http://lists.nongnu.org/mailman/listinfo/koha-translate In your email, please specify your Language, and Country/Region (and if your language uses a non-latin script, please also indicate the Script). Koha uses RFC4646 for managing language subtags, so it's important that we know all of those aspects of the language you're providing. It's important that you post your intent, this way we can avoid overlap and perhaps can even do some collaboration. Note: even if you've contributed a contribution previously, please announce your intent so we can have you on record for the 3.0 version. 3. Determine the application you intend to use to do the translation. You have a few options: a. http://translate.koha.org will allow you to add your translations via a web-based interface. If your language, region, country and script are not listed, please email me and I will add them. b. Desktop Application - there are a few: LocFactory Editor (for OSX), POEdit (for Windows), Kbabel (for Linux). If you use a desktop application, please ensure that your encoding is set either UTF-8 or UTF-16, depending on your language's script support in UTF-8. Most languages should use UTF-8. c. Text file -- yes, you can edit POT files directly in a text editor, but please make sure you have the proper encoding as with the Desktop application. 4. Obtain the Translation Files. (doesn't apply if you use translate.koha.org) You need to copy two files from the Koha 3.0 repository, one for the OPAC, and one for the Staff Client: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… 5. Naming your files. (doesn't apply if you use translate.koha.org) Starting with Koha 3, we're using RFC4646 language subtag naming conventions, (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). RFC4646 has a concept of 'extensions' that Koha uses to tag for the 'theme' (t) 'interface' (i) and 'version' (v). For example, if you're creating a French translation from France, for the staff interface, and version 3.00.00.00, the filename would be: fr-FR-i-staff-t-prog-v-3000000.po 6. If you've used translate.koha.org to submit your translation, when you have finished, the system will have that indicated on the report (100%). Otherwise, you'll have to send the file to us somehow. You can do that via email to the list (in which case i recommend creating an archive of the completed files, rather than sending them through in raw format). Or, if you are reasonable comfortable with the command line, you can submit them via Git as a patch. Here are the basic instructions for how to contribute using Git: http://wiki.koha.org/doku.php?id=en:development:git_usage Translations go in the misc/translator/po file, and should utilize the standard naming conventions. If you have a question, don't hesitate to ask. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Wiki Section on Bar Code Scanners
by Chris Nighswonger 16 Jan '08

16 Jan '08

Sorry for the cross post... FWIW, I added a section to the wiki containing bar code scanner info. The namespace follows 'en:documentation:barcode_scanners:foobrandscanner' I have munged up a section containing some config notes I made while getting my Metrologic VoyagerGS up and working. Any additions/corrections/criticisms (constructive) would be appriciated. Also, if you use a different scanner it would be nice to add a section for others as well. http://wiki.koha.org/doku.php?id=en:documentation:barcode_scanners:ms9590_v… Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

1 0