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

RFC: create old_issues and old_reserves
by Galen Charlton 11 Mar '08

11 Mar '08

Hi, I would like to create two new tables, old_issues and old_reserves, that would be used to store completed checkouts (issues) and hold requests (reserves). Similar to how tables like deleteditems function, whenever a checkout or hold request transaction is completed or canceled, the row representing it would be moved to old_issues or old_reserves respectively. I believe doing this would have several advantages: 1. The issues and reserves tables would cease to grow indefinitely; instead, they would have only as many rows as needed for a library's peak number of transactions. It is my hope that this would improve performance, particularly when processing long hold queues. 2. It would become possible to add a unique key constraint on issues.itemnumber (as an item can be issued only once at a time). Similarly, it may become possible to add unique key constraints on reserves. 3. Some queries and joins would be simplified. Perl code and ad-hoc reports could rely on a conceptually simpler notion that if a row is present in issues or reserves, it represents a current or otherwise active transaction. 4. Koha administrators could safely archive or truncate the old_issues and old_reserves tables if they desire to remove or completely anonymize circulation history. Thoughts? Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709

6 7

zebra deleting
by Ignacio Javier 11 Mar '08

11 Mar '08

Good evening to everybody in my GMT area, good night and moorning for the rest, and good whatever for Space Station resident personal: I've been adjusting a little /usr/share/koha/bin/cronjobs/update_items.pl script to change it consequently for koha 3 alpha SQL tables and API, and my doubt is: a) Does not koha make this process directly when the insert/update/delete of a MARC record? , or is always needed to do similar zebraidx -et ceteras... to syncronize it in a cron fashion? Thanks in advance and greetings. Ignacio Javier Gómez Rodríguez Analista - Programador Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com

1 0

Re: [Koha-devel] Welcome new Koha translators
by Joe Atzberger 11 Mar '08

11 Mar '08

Kurt and Tao -- Welcome both of you to the Koha development list. It is great to hear your interest extending the reach of the Koha project. For practical instructions on how to begin translation, the first place to start is: http://translate.koha.org/ There is also a separate translators' listserv via* koha-translate(a)nongnu.org *with more information available at: http://lists.nongnu.org/mailman/listinfo/koha-translate The members of that list are the most likely to be helpful with the details of how to proceed. Tao, you may be pleased to see that 2 partial Chinese translations already have been started. Your vision of Koha in schools across China is very exciting! Kurt, you will want to contact Josh Ferraro (via that list, for example) to request Dutch be added to translate.koha.org. Thanks for your interest and efforts! --Joe Atzberger Systems Administrator, LibLime On Tue, Mar 11, 2008 at 6:58 AM, Kurt Debrouwer < secretariaat(a)academiewaregem.be> wrote: > We are working on implementing the Koha library software in our music > academy which is situated in the northern Dutch speaking part of Belgium. > We would like to translate the OPAC file into Dutch. How do we proceed in > order to do so? Can Dutch be added to the list of languages? And what do > we do next? > > Awaiting your reply, > Kind regards > > Kurt Debrouwer > Administrator in Chief > ______________________________ Previously Tao Huang wrote: > Hi everyone, > > I'm Tao from Shanghai, China. I started to use Koha about one year ago > when I planned to establish a small library in my company. But I'm only a > part-time librarian:) I found that Koha was interesting and powerful. > > I have had this dream for about several months: Every school in China can > use Koha as their electronic library. You may have known or not yet, in some > regions of China, the schools there don't have enough fund to afford > commercial library software. Koha seems to be the best choice for them. > However, the language maybe becomes the biggest problem when they try to use > Koha, although Koha have been partly translated into Chinese. > > That's why I join this list. First I am willing be a translator, then I > will make a wonderful Chinese document for Koha. > > You guys are the most intelligent and experienced. Please give me > suggestions and help to make my dream come true! > > Many Thanks, > Tao Huang

1 0

translating Koha into Dutch
by Kurt Debrouwer 11 Mar '08

11 Mar '08

1 0

Problems on gitWeb
by Zeno Tajoli 11 Mar '08

11 Mar '08

Hi to all, I'm trying to see the koha git web site http://git.koha.org I receive the error: failed: Connection refused. No problems on update the sources with git. What is it the problem ? Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

3 2

Re: [Koha] Follett to Koha 2.2.9 migration help
by Mason James 10 Mar '08

10 Mar '08

On 2008/03/8, at 5:24 AM, Darren De Zeeuw wrote: > I am the volunteer IT guy for a small private school. We have been > using > Follett's Circ Plus/Cat Plus software for many years, but their > upgrade path > is too expensive and our old Mac OS 9 machine running the software > in the > library had a disk failure. It's time to find another solution. > Koha seems > to be the perfect fit for us, but I need to show that it's better > than what > we have in order to get approval. Hi Darren, Recently at LIblime, we did some conversions from Follet systems to Koha. > I have a MICROLIF file with around 8000 records > exported from our Follett catalog. I ran the bulkmarcimport.pl > script and > it brought most of the data over as far as I can see (I'm not a > librarian), > but seems to be missing our bar-coding information at least. I'm also > unsure if I can migrate over our patron list as well. The missing item info you are describing is because Follet's MICROLIF marc records store their item-info in the 852 fields ( from memory... ) (Every ILS vendor have their little quirks about where they stuff the item-level info, Follets looks to be in 852 What is needed is a small script to fetch those Follet 852 item- values and move them to their corresponding Koha 952 fields, then write those corrected records out to a new file. Run Bulkmarcimport.pl on this new file, and you will successfully pick up those missing item-level values in your Koha marc import. FYI: when i get some time, I plan to add to the koha-wiki some general code examples of this mapping process I described. I hope that helps, Cheers, Mason.

2 1

RFID and other hardware moves...
by Ignacio Javier 10 Mar '08

10 Mar '08

Hi all: I just was wandering if Koha 3 has done any integration with RFID and/or optical barcode readers, is already started, planned or is just a "wrap, wrap... doit yourself"?. There seems to be a world down under lib/C4/SIP but.... is "baby safe"? Thanks, Ignacio Javier Gómez Rodríguez Analista - Programador Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com

2 2

Re: [Koha-devel] Re: [Koha] Follett to Koha 2.2.9 migration help
by Mason James 10 Mar '08

10 Mar '08

On 2008/03/10, at 4:07 PM, Jesse Weaver wrote: > > > > The missing item info you are describing is because Follet's MICROLIF > marc records store their item-info in the 852 fields ( from > memory... ) > (Every ILS vendor have their little quirks about where they stuff the > item-level info, Follets looks to be in 852 > > What is needed is a small script to fetch those Follet 852 item- > values and move them to their corresponding Koha 952 fields, then > write those corrected records out to a new file. > Run Bulkmarcimport.pl on this new file, and you will successfully > pick up those missing item-level values in your Koha marc import. > > > > Can't you just change the marc -> koha links from the 952 subfield > to 852 ones? Granted, this won't work if you have anything that > needs to go into the biblio-level tables (like the itemtype), but > it's worth a shot. > > -- > Jesse Hi Jesse, That is a good idea to test, and the exercise may highlight some subtle mapping bugs in Koha too I'm not quite sure how Koha would behave set up like that, but it would be good to confirm either way. Because i was involved in quite a few ILS to Koha conversions, it made sense to map the various ILS's marc formats to a 'standard' Koha format, rather than creating a custom Koha mapping setup for each client, based on their existing marc format But for a small one-off install by a library, it could make sense to change the Koha mapping to match the existing marc format Cheers, Mason.

1 0

Re: [Koha] HTML not being encoded for display?
by Rick Welykochy 07 Mar '08

07 Mar '08

Chris Cormack wrote: > Short answer is yes, there are more checks on the use side (opac). The > staff interface has some checking, but as Joe pointed out if you have > staff inserting html into your marc data, you have bigger problems. What checks can you do? Characters like "<" and "&" are valid in titles. They cannot be escaped before storing in the database. I could easily imagine a book or article entitled "The danger of <script>s", for example. Joe misses the point with a glib answer "you have bigger problems". First off, staff entering data into the catalogue would hardly be typing in "&" characters maliciously. Rather, they do not know that this is a special character in HTML. Neither should they have to know this. The software must handle it and handle it correctly. Second, more and more Koha instances are now on the Internet. It ain't staff I am worried about. It is cookie and identity thieves who can access the OPAC (P=public) and enter XSS exploits into things like suggestion boxes and registration forms. Innocent staff are caught when they open admin pages that transmit XSS data. And it is their cookies (to the Intranet area) that can then be stolen. This is the fast track to your server being compromised and zombied. > Ill let the other developers answer more fully, but one thing to bear in > mind is that the data is used in more than just a web interface, so > storing things like html entities in the database isnt feasible. Exactly. It takes careful encoding of data which is served up on web pages. The encoding varies, depending on whether the data is inline in text, inside a tag attribute, inside a URL or nested at a 2nd level in any of the above. Not an easy task to get correct. This is why XSS is so prevalent on the Internet. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor A terrorist is someone who has a bomb but can't afford an air force. -- William Blum

1 0

Re: [Koha] HTML not being encoded for display?
by Chris Cormack 07 Mar '08

07 Mar '08

Shifting this over the devel lists, where it can be discussed more fully. Chris On 3/7/08, Chris Hammond-Thrasher <hammondthrasher_c(a)usp.ac.fj> wrote: > > This could be a serious problem. Is this addressed in Koha 3? Are their > any > checks for dangerous user input in Koha 2 or 3? > > -cht > > > > Chris Hammond-Thrasher MLIS CISSP > Library Systems Manager > University of the South Pacific > Suva, Fiji > +679 3232233 > hammondthrasher_c(a)usp.ac.fj > > > -----Original Message----- > From: koha-bounces(a)lists.katipo.co.nz > [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Rick Welykochy > Sent: Thursday, 6 March 2008 12:39 PM > To: George Adams > Cc: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] HTML not being encoded for display? > > > George Adams wrote: > > > For example, in the "Add a MARC Record" section, I can enter in a title > (tag 245c) of the following: > > > > My Book is <font size="+5">Great</font> > > > > Sure enough, when the completed MARC record is submitted, the additem.pl > page will show the title with the word "Great" really big. Once added to > the catalog, it will show up in the search engines with that word really > big > as well. > > > > Surely everything entered by users and librarian in the OPAC and > Intranet > sites should be HTML-encoded if it's going to be redisplayed, right? Did > I > miss some setting in the Administration menus that would disallow HTML > from > being entered in a form, or is this a fairly big bug? > > > This is why Koha is susceptible to cross-site scripting attacks, as > already > raised by someone else on this list a few months back. > > Example: > > My book is <script>alert("Gotcha!")</script> > > > cheers > rickw > > > > -- > ________________________________________________________________ > Rick Welykochy || Praxis Services || Internet Driving Instructor > > A terrorist is someone who has a bomb but can't afford an air force. > -- William Blum > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0