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

Wierd bug in addbiblio.pl
by Tarallo, Andres 09 Aug '05

09 Aug '05

We're doing our own bug hunting session. We found a bug in the addbiblio.pl, this bug appears only in fields with authorized values lists. When you click in the + sign to duplicate a field it duplicates AND FILLS with the same value the field. What's more if yu have an empty subfield with the same authorized value list it also does the same behaviour. Since we have been hacking koha, I thougth that was something we broke, but I've found the same behaviour on the demo site of koha france. We tested this with the 041 field (language) y think that in koha france in 106 or something like that (know very little UNIMARC). We've doing all kind of tests and found that this bugs is related to the scrolling_list method of the CGI library, this somewhat caches previous calls to the function. Any help will be appreciated Andres

3 10

long is the road to 3.0...
by Paul POULAIN 09 Aug '05

09 Aug '05

... but the 1st commits will arrive in a few hours, As I hack the code, I see that the field biblio.biblionumber can be called : * biblionumber * bib * oldbiblionumber * bibnum I plan to normalize & use only biblionumber that is more logic. Don't be surprised, if in the next days/weeks, the cvs head is badly broken. (that's why we have a 2.2 branch ;-) ) Every time I commit some code that breaks stability but is a step to 2.2, i'll throw a mail to koha-devel to explain what the commit does & breaks (at least what i'm sure it breaks ;-) ). My plan before the end of the week is (nothing commited yet) : 1/ modify SQL structure to get rid of marc_biblio / marc_subfield_table / marc_word => DONE 2/ modify Biblio.pm to handle biblios in the new structure => 10% done 3/ modify SearchMarc.pm to enable search on the new structure 4/ provide some zebra config files. of course, that will be highly unstable & only for true hackers, the one with a beard that love having bugs :o) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Keeping Up
by Joshua Ferraro 09 Aug '05

09 Aug '05

Hi all, How do you keep up with library, technology and Koha news? What online resources do you use? What Lists, Forums, RSS feeds, Blogs, Wikis, podcasts, etc. do you use? 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

3 2

Searching Group Meeting Notes
by Joshua Ferraro 09 Aug '05

09 Aug '05

Hi everyone, Sorry I'm late in putting this out: Present: kados slef owen chris paul thd rach This is just the highlights. If you want to grok the issues you'll need to read the log: http://koha.org/cgi-bin/logs.pl?recall=recall&saved_query=Searching%20Meeti… 1 Started with a discussion of Zebra: using zebra as a plugin isn't a good idea because we don't want to maintain two koha searching apis we need to test Zebra to determine which option is best: zebra for all (need to test .. does this make circ slower) or zebra for biblio, database for item info paul will begin working on porting Biblio.pm to reindex zebra (to store status info in the MARC record and re-index zebra during circ) chris will work on writing a wrapper for opac searches kados will begin working on configuration of Zebra thd mentioned some problematic UNIMARC issues related to compound fields 2 slef and kados discussed CQL as a query front end. discussion will be moved to koha-devel 3 the discussion turned to opensearch. kados showed the opensearch demo http://liblime.com/opensearchportal.html the idea of federated searching and ILL using opensearch was discussed slef suggested looking at RDF rather than RSS2.0 the discussion will be moved to koha-devel -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

3 6

long is the road (1st commit done)
by Paul POULAIN 09 Aug '05

09 Aug '05

1st commit done. It contains : * updater/updatedatabase : get rid with marc_* tables, but DON'T remove them. As a lot of things uses them, it would not be a good idea for instance to drop them. If you really want to play, you can rename them to test head without them but being still able to reintroduce them... * Biblio.pm : modify MARCgetbiblio to find the raw marc record in biblioitems.marc field, not from marc_subfield_table, modify MARCfindframeworkcode to find frameworkcode in biblio.frameworkcode, modify some other subs to use biblio.biblionumber & get rid of bibid. * other files : get rid of bibid and use biblionumber instead. What is broken : * does not do anything on zebra yet. * if you rename marc_subfield_table, you can't search anymore. * you can view a biblio & bibliodetails, go to MARC editor, but NOT save any modif. * don't try to add a biblio, it would add data poorly... (don't try to delete either, it may work, but that would be a surprise ;-) ) IMPORTANT NOTE : you need MARC::XML package (http://search.cpan.org/~esummers/MARC-XML-0.7/lib/MARC/File/XML.pm) that requires a recent version of MARC::Record Updatedatabase stores the iso2709 data in biblioitems.marc field & an xml version in biblioitems.marcxml Not sure we will keep it when releasing the stable version, but I think it's a good idea to have something readable in sql, at least for development stage. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Website / ID Group Meeting Reminder
by Joshua Ferraro 09 Aug '05

09 Aug '05

Just a reminder that our Website / ID meeting is tomorrow (Wed, Aug 10) at 20:00GGMT (time in your area: http://tinyurl.com/dbueu) I've put up a basic agenda on the wiki, please feel free to add or expand on your items: http://tinyurl.com/d7de3 Hope to see you tomorrow! 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

1 0

about leader management
by Paul POULAIN 08 Aug '05

08 Aug '05

Hi koha devs, I'm working on leader support atm. It works quite well now (on rel_2_2 cvs branch) I'm waiting for some feedbacks from joshua. I'm working on 2 plugins that will help the library to fill it. I work on UNIMARC as well as on MARC21 plugin. I have some questions to make them as powerful as possible : * the default values, when the biblio is created. I suggest : - n (new/creation) for byte 5 - a (printed material) for byte 6 - m (monography) for byte 7 all other bytes being empty. * when biblio is modified, is it interesting to set byte 5 to c (Corrected or Revised) automatically ? * any other suggestion or interesting idea ? (link to marc21 : http://www.loc.gov/marc/bibliographic/ecbdldrd.html) (note : the leader will be in MARC editor in a "virtual field", named 000@, field 000, subfield @, but it's handled as the leader in the MARC record, of course) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 1

Authorities reporting to one tag only?
by Tümer Garip 08 Aug '05

08 Aug '05

I am using koha2.2.2b on a windows machine. It took me while to figure out how to work the authority file with MARC21 and may be I am still not very clear. I want to use an Authors authority table to report to MARC 100 field OR Marc 700 field That is if I am filling the 100 field (that field being set to be filled by authority table) searching for an author from the authority table and getting it works. However I cannot do the same with 700 field. This I believe is because the authority-file checks for ‘tag_to_report’ which can only be set to one tag only. Is this to mean that for each tag I have to recreate an authority table which does not sound logical as I will be just duplicating all the same data? Am I missing something here? Or is this what is ment to be? Tumer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.2/53 - Release Date: 20/07/2005

2 1

Alert / letter system done
by Paul POULAIN 05 Aug '05

05 Aug '05

Hi, I think the Letter system is ready, as well as the Alert one (although it will have to be improved with some other alerts) I have successfully : - defined a letter for serials. - in Serials modules, - selected this letter for alert - been in OPAC, and put an alert on this subscription - been back in librarian interface, and recieved an issue for the subscription. Few seconds later, I got a mail in my mailbox, everything worked fine. what has to be done : 1- I need at least 1 "letter" in english, to include it in CVS, for inclusion during install stage. 2- Ideas to extend the Alert system. I think we could create alerts for Virtual shelves (= be warned when a virtual shelf is modified). Does anyone have an idea. This system should be working for any module (acquisition/cataloguing/members/circulation/authorities/...) (I also plan to modify mails sent on suggestions to use the letter system. Most of my libraries want to have their own letter ;-) ) Next week should be used to play with Zebra & 3.0 version and begin point 2-H circulation list. (Will use Letters system probably ;-) ) (+ ending a data migration) Have nice week-end koha fans. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

LOG and USERENV specific information
by Henri-Damien LAURENT 05 Aug '05

05 Aug '05

Adding Log Facility. Needs Two Update in database... On more table (action_logs) And One more syspref Activate_Log, with YesNo values. Maintainance has been sweeped of previous Log functions addbiblio.pl contains a sample of code using Log.pm Could be generalized to Authorities, acquisitions, members soon. Adding page to display log views. can be called by admin/viewlog.pl Works with C4/Log.pm uses action_logs table using C4::Log, you have access to : - logstatus, a simple Boolean Function which returns True if Activate_Log is set false if off. - logaction that takes : * usernumber returned by gettemplateanduser * modulename a string (acquisition, catalogue, asoasf) * actionname a developper defined string (add, modify, delete) * objectnumber, primary key of object modified * infos, if needed (not a DELETE action) should contain the informations stored) - displaylog takes a modulename and a list of filters (list of hashes with keys name and value) and returns a result list of hash-record and a count of records returned. the information returned by displaylog should be different whether you modify a book or an order. That's Why a modulename is needed. The userenv cookie is set in Auth.pm. To get the userenv information, you must FIRST gettemplateanduser, which verifies whether the user is granted access to the demanded page, and set informations with decoding the cookie. Then you can get : $ bornum, $ userid, $ cardnumber, $ firstname, $ surname, $ branchcode, $ userflags of the active user calling the C4::Context->userenv which returns a hash with number, id, cardnumber, firstname, surname, branch, and flags keys. Any further information can be provided if needed. Enjoy. -- Henri-Damien LAURENT

2 1