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

RE: Some script for item deletion - ambiguity
by Tümer Garip 02 Mar '06

02 Mar '06

Hi, Ther was an ambiguity in my previous mail. Sorry. The first line should read: We noticed that the librarian can actaully delete an item (by mistake or while correcting some biblios) even the book is ON LOAN ! -----Original Message----- From: Tümer Garip [mailto:tgarip@neu.edu.tr] Sent: Wednesday, March 01, 2006 3:56 PM To: 'paul(a)koha-fr.org' Cc: 'koha-devel(a)nongnu.org' Subject: Some script for item deletion - suggestion Hi Paul, We noticed that the librarian can actaully delete an item (by mistake or while correcting some biblios). Although KOHA keeps records of deleted items its too much work trying to retrive it. So we think KOHA should prevent deletion of such items. We have added the following script to additem.pl } elsif ($op eq "delitem") { #----------------------------------------------------------------------- ------------------------------------------------------- # retrieve item if exist => then, it's a modif + my $sth=$dbh->prepare("select * from issues i where i.returndate is +null and i.itemnumber=?"); + $sth->execute($itemnum); + my $onloan=$sth->fetchrow; + push @errors,"book_on_loan" if ($onloan); +##error book_on_loan added to template as well + if ($onloan){ + $nextop = "additem"; + }else{ + &NEWdelitem($dbh,$bibid,$itemnum); + $nextop="additem"; + } We also believe a similar code should be inserted to addbiblio.pl as well If you think the sameway can you please commit these, thanks Tumer

1 0

Some script for item deletion - suggestion
by Tümer Garip 01 Mar '06

01 Mar '06

Hi Paul, We noticed that the librarian can actaully delete an item (by mistake or while correcting some biblios). Although KOHA keeps records of deleted items its too much work trying to retrive it. So we think KOHA should prevent deletion of such items. We have added the following script to additem.pl } elsif ($op eq "delitem") { #----------------------------------------------------------------------- ------------------------------------------------------- # retrieve item if exist => then, it's a modif + my $sth=$dbh->prepare("select * from issues i where i.returndate is null and i.itemnumber=?"); + $sth->execute($itemnum); + my $onloan=$sth->fetchrow; + push @errors,"book_on_loan" if ($onloan); ##error book_on_loan added to template as well + if ($onloan){ + $nextop = "additem"; + }else{ &NEWdelitem($dbh,$bibid,$itemnum); $nextop="additem"; + } We also believe a similar code should be inserted to addbiblio.pl as well If you think the sameway can you please commit these, thanks Tumer

1 0

What is GoKoha.com
by Eric Bégin 01 Mar '06

01 Mar '06

1 0

New Feature: Amazon.com Content
by Joshua Ferraro 27 Feb '06

27 Feb '06

Hi all, I've just committed a fully-preferences-based Amazon.com module to rel_2_2. There are three new system preferences: AmazonContent AmazonDevKey AmazonAssocTag To use this new feature, you'll need an Associates login: https://associates.amazon.com/gp/flex/associates/apply-login.html and a developer's key: https://aws-portal.amazon.com/gp/aws/developer/registration/index.html Once you have recieved both IDs from Amazon, and put them into the appropriate system preferences, you can set AmazonContent to 'yes'. At this point, you should have the following content from Amazon.com displaying in your OPAC (NPL template only): * Cover images * "Read it now" * "Search inside" * Descriptions * Reviews * Ratings To see what this will look like, please view this example record from LibLime's OPAC: http://opactest.liblime.com/cgi-bin/koha/opac-detail.pl?bib=21752 Note that if you don't touch these systemprefs, no Amazon.com code will be called. Paul/HDL, if you want to add this to default templates, please take a peek at commits to NPL template files. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

2 2

What is GoKoha.com
by Eric Bégin 27 Feb '06

27 Feb '06

1 0

some perl lines
by Wojciech Zatorski 25 Feb '06

25 Feb '06

Hello koha, why are this lines in koha code? (OPAC/opac-MARCdetail.pl) if ($fields[$x_i]->tag() eq $fields[$x_i-1]->tag()) { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ???? $tag_data{tag}=""; } else { $tag_data{tag}=$fields[$x_i]->tag().' -'. $tagslib->{$fields[$x_i]->tag()}->{lib}; } because this lines of marc display are incorrect with marc standards (for example field 650)... and i find small bug in /usr/share/perl5/5.8.7/CGI.pm when you using utf-8: $toencode =~ s{\x9b}{›}gso; this line corrupt polish utf-8 S letter bye -- <wojciech(a)zatorski.net> tel. +48 509-855-239; GG: 1500861; Skype: zatorski http://www.Zatorski.Net -- Actions speak louder than words.

1 0

Re: [Koha] some perl lines
by Chris Cormack 25 Feb '06

25 Feb '06

On Sat, Feb 25, 2006 at 10:35:57AM +0100, Wojciech Zatorski said: > Hello koha, > > why are this lines in koha code? > > if ($fields[$x_i]->tag() eq $fields[$x_i-1]->tag()) { > $tag_data{tag}=""; > } else { > $tag_data{tag}=$fields[$x_i]->tag().' -'. $tagslib->{$fields[$x_i]->tag()}->{lib}; > } > > because this lines of marc display are incorrect with marc standards (for example field 650)... > Answering on the devel list as this is a more appropriate place for this type of discussion. What module/script is this code in, and what lines? If you provide more information its much easier for people to fix things. Chris -- Chris Cormack Programmer 027 4500 789 Katipo Communications Ltd chris(a)katipo.co.nz www.katipo.co.nz

1 0

Re: News & holiday management
by Paul POULAIN 24 Feb '06

24 Feb '06

Tümer Garip a écrit : >Hi Paul, >I am not able to send all of koha due to my smtp. >See whether you'll find these useful. > Tümer : ====== MANY THANKS People reading koha-devel mailing list : ======================== Tümer just sended me 2 nice features : - holidays management : Some scripts to define closed days in the library and adapt return dates accordingly. - news in home page : some scripts to create basic news on the home page. with all DB definition required and a readme containing explanations. I plan to work on it next week, and include in in CVS head once the code is cleaned, adapted to PROG templates and any non english string removed. Again, many thanks to Tümer. (paul notes to remember adding Tümer as contributor on contributor page...) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

1 0

[mhelman@illinoisalumni.org: Re: [Koha] The '650x' problem]
by Joshua Ferraro 24 Feb '06

24 Feb '06

----- Forwarded message from BWS Johnson <mhelman(a)illinoisalumni.org> ----- Salve! Soooo, if you go to the catalogue you've set up, which makes me want a Corona ;), you'll see that The complete idiot's guide to dealing with in-laws / By Rozakis, Laurie E. gets lumped in with a whole bunch of kid's and adult fiction. If I were a patron looking for how to handle my in-laws, (right now! they're at home!!!!) I would have to sort through all of the Family Life listings, even though, I ought to be able to just view the non fiction adult ones as a separate string. It gets worse! This entry http://opac.liblime.com/cgi-bin/koha/opac-MARCdetail.pl?bib=22186 gets lumped in with family life, even though it's about farm life and family farms. Eeep! It's interesting to me, because if you do the old fashioned give me a search string that looks like this family life -- juvenile fiction under keyword I'll get this http://opac.liblime.com/cgi-bin/koha/opac-MARCdetail.pl?bib=23409 And if I do it under subject I'll get this http://opac.liblime.com/cgi-bin/koha/opac-MARCdetail.pl?bib=23351 It's mashing the 650a s together, which is no good. In any case, just so it's clear, I do appreciate the work that everyone does. I know that MARC is old and it's a crappy thing to work with, but many folks still insist on it because it can sort out things that simple subject searching doesn't. I want to be on the current Koha version, but I'm having issues at work, which is preventing me from doing that. My husband thinks a new router might do the trick, so I'll try and get one. I still get a lot of questions, but I feel bad about not being current, so I can't upgrade the wiki. Cheers, Brooke @ Hinsdale MA ----- End forwarded message ----- -- Joshua Ferraro VENDOR SERVICES 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

[mhelman@illinoisalumni.org: Re: [Koha] The '650x' problem]
by Joshua Ferraro 24 Feb '06

24 Feb '06

----- Forwarded message from BWS Johnson <mhelman(a)illinoisalumni.org> ----- Salve! >Could someone explain to me what the '650x' problem is? Is it a >matter of not being able to search for subjects in 650x? or is it >a matter of not being able to display the subject tags/subfields >correctly in the MARC view of Koha? If you could, it would be great >to get specific examples so we can efficiently find a solution (if >in fact there is a problem). Feel free to use the LibLime demo when >refering to such examples: > It's a little of both :) The whole subject searching can of worms is related to not starting out as MARC, but I bet the keyword search works so well because it's not normal MARC. Anyway, suppose I were holding a book in my hand about space shuttle accidents geared towards children. One of its tags might look like this: 650 _0 $a Space shuttles $x Accidents $v Juvenile literature. 650 means its a topical subject That 0 means we want the computer to search on this field, it's called an access point, and it's rather important. The a is the first part of the subject. That means your free to lump this book in with all of the other books on space shuttles. The x is special. It's there as a subheading. It says hey, this book isn't only about space shuttles, it's about accidents, too. The v lets you know it's geared towards kids, which is happy. Now, here's why you don't necessarily want to bust up the joint. Because the x, and anything else for that matter, is not playing nice with the a, when you go to look up a book by subject, it doesn't compartmentalise with the rest of the kid's books on space shuttle accidents. Instead, it kind of views itself as three different books - one on space shuttles, one on accidents, and one for kids. So that if I were using the linked subject headings that are a nice feature, they don't link up correctly, because this book would show under 3 categories instead of one like I want it to. This can get very sticky indeed when you're helping kids out, or you are helping an adult that doesn't want to look at kid's stuff. Usually because of that v, I can just go ahead and filtre out all of the juvenile literature headings, but I can't with Koha. Does that make it a bit clearer? Cheers, Brooke @ Hinsdale MA ----- End forwarded message ----- -- Joshua Ferraro VENDOR SERVICES 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