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

RE: [Koha] from ISIS to Koha
by Lucia Phillip 03 Nov '03

03 Nov '03

Hi, I know a number of libraries that would like to use Koha. Many of them are at present working with WINISIS. With the version 1.92 i was able to take MARC records exported as an ISO 2709 and import them into the breeding farm. i was then able to search for records and then import them into KOHA. To do this I reversed the changes that had been made to fit Winisis such as the subfield delimiters, the end of field and the end of record symbols. With this latest version however although I am able to import records into the breeding farm, when I go to Add biblio and do a search of a record that I know was among those imported, I get the message that <Nothing found>. I am wondering why this is happening with this version. Lucia Phillip National Library and Information System Authority Trinidad nad Tobago -----Original Message----- From: paul POULAIN [mailto:paul.poulain@free.fr] Sent: Monday, October 13, 2003 8:35 AM To: koha; Koha-devel Subject: [Koha] from ISIS to Koha Hi, I've a (future ?) customer that want to switch from winISIS to Koha. He sends me lot of exports, but none of them work with classic dumpmarc.pl script of Koha (refused by MARC::Record) Does anyone here know how to setup winISIS export options to get a valid iso2709 file ? Thanks -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org) _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

3 2

Re: Koha documents?
by Pat Eyler 31 Oct '03

31 Oct '03

On Fri, 31 Oct 2003, Auvo Finne wrote: > Dear Pat, Hello Auvo, > > I act as a consult and codeveloper for the Tumaini University (Tanzania) library system. > One of our alternatives is Koha. To seriously assess the suitability of Koha for Tumaini > I would like to see some architectural documents. > Sadly, architectural documents are one of the things that we don't have in abundance. If you were willing to spend a bit of time asking questions (even just passing a list of questions you need answers to), we could probably use them to build a set of answers/documents that might help. I'm answering this on the koha-devl mailing list as well, hopefully this will help generate a bit more help for you as well. thanks, -pate > We are applying the universal software development process. This process is very much > architecture centric and uses several general or detailed diagrams. > > Does it exists any descriptions of Koha main components and their purposes, roles, > interaction? Descriptionsof the use of programming languages in implementing these > components? Etc. > > I'll be grateful if you could help me in getting some of these documents. > > Very best wishes, > > Auvo Finne > Pitkakatu 44, Jyvaskyla, Finland > +358 400 646 815 > auvo.finne(a)cccc.fi > >

1 0

RE: [Koha-devel] "XX at /usr/local/koha..."
by Anthony W Youngman 29 Oct '03

29 Oct '03

As it looks like nix, there's always grep ... Run that over it to display any lines that DON'T match that pattern ... Or use sed to delete those lines ... There's plenty ways to skin a cat ... Cheers, Wol -----Original Message----- From: Owen Leonard [mailto:oleonard@athenscounty.lib.oh.us] Sent: 29 October 2003 16:48 To: Koha-Devel Subject: [Koha-devel] "XX at /usr/local/koha..." > Why does Koha.pm constantly write the error "XX > at > /usr/local/koha/intranet/modules/C4/Koha.pm line > 198," when this is > actually not an error? This has the unfortunate side effect of giving us daily a 30 megabyte error log full of "XX at /usr/local/koha/intranet/modules/C4/Koha.pm line 198." This makes it awfully difficult to find *actual* errors. What can we do to make it stop? -- Owen ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel *********************************************************************************** This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. ***********************************************************************************

1 0

circulation broken in pre5
by robweir＠alum.drexel.edu 29 Oct '03

29 Oct '03

Hi all: In preparing a windows release of pre5, I note that circulation appears to be broken in pre5. When trying to bring up circulation, I get an apache internal error 500. The apache error log shows: [Tue Oct 28 22:25:07 2003] [error] [client 127.0.0.1] Premature end of script headers: circulation.pl, referer: http://intranet/cgi-bin/koha/mainpage.pl [Tue Oct 28 22:25:07 2003] [error] [client 127.0.0.1] HTML::Template->new() : Syntax error in <TMPL_*> tag at C:\usr\koha200pre5\intranet\htdocs\intranet-tmpl\default\en\circ\circulation .tmpl : 80. at C:/usr/site/lib/HTML/Template.pm line 2243., referer: http://intranet/cgi-bin/koha/mainpage.pl I get the same error using both default en and default fr templates. I get the same error with either perl 5.6 or 5.8. Have there been any changes in the required perl modules? If I copy circulation.tmpl from the pre4 release the error goes away and the page displays properly. However, I know you've been working on circulation templating, and I suspect the older version of circulation.tmpl will not work properly with the newer release. I did a diff of the two file versions, but differences are drastic enough, I'm not going to be able to figure it out. Any ideas on what I can do to fix this before I build the windows install package? I am testing with the default settings of simple acqusitions, MARC yes, MARC21, and default english themes and templates. Thanks! I appreciate the good job you guys are doing! Rob

2 3

"XX at /usr/local/koha..."
by Owen Leonard 29 Oct '03

29 Oct '03

> Why does Koha.pm constantly write the error "XX > at > /usr/local/koha/intranet/modules/C4/Koha.pm line > 198," when this is > actually not an error? This has the unfortunate side effect of giving us daily a 30 megabyte error log full of "XX at /usr/local/koha/intranet/modules/C4/Koha.pm line 198." This makes it awfully difficult to find *actual* errors. What can we do to make it stop? -- Owen

2 1

Re: [Koha-devel] hard coded stuff?
by Owen Leonard 27 Oct '03

27 Oct '03

> If we had a mechanism to extract the strings for > translation only the translators wouldn't > have to worry about the underlying code behind > it. If you're requesting that all language strings be moved to some kind of master file for ease of translation, then say so! It sounds like the issue of the image path in the css file is unrelated. We've had this discussion before, about how to facilitate internationalization and make template translation easier. There are arguments on both sides, and right now the arguments to keep things the way they are are going to win because we're working up to 2.0 and too much work needs to be done on bug- fixing and functionality-enhancement. I hate tracking changes to templates just as much as you do--probably more, because our custom template is radically different from the default one. I have to look at template changes and translate them not into a different language but into a whole different HTML structure! But I don't know the solution, other than to document modifications much better than we do now. -- Owen

1 0

Re: [Koha-devel] hard coded stuff?
by Owen Leonard 27 Oct '03

27 Oct '03

> .koha { > text-align:center; > background-image:url("/intranet- > tmpl/default/en/images/background-mem.gif"); > } > Now if the whole idea by introducing templates > was to separate the code from the > design then this behavior does not stick to the > rules. But css is not code, it *is* design. The css file is in a directory of files that are available to the template-writer for design. It seems to me that if somone is working on the /default/en/ template then they should be able to specify as much. That said, if template-writers can use HTML:Template variables to specify the current theme, that makes it easier on others--but I disagree that this has much bearing to the goal of internationalization. Template-writers may have very selfish goals: they want to customize Koha for themselves. They may not work with internationalization in mind. It's the developers that need to be held to a higher standard. > An example: a file in .default/en directory > changes. The modification includes a > language string and a path to a perl file ON THE > SAME LINE OF CODE. I don't understand what you're referring to here. The path to Perl files should remain constant no matter what template you use. Only the language string needs to be modified. Of course visual inspection of the template is needed--how else can you make a translation? > Before koha-1.2.3 all the language strings where > in the perl scripts. Now they are found > in the template files. Isn't this better? Maybe I don't understand at all what you're trying to say. -- Owen ---- Nelsonville Public Library

1 0

koha and objecting to libraries [RT]
by MJ Ray 26 Oct '03

26 Oct '03

This is almost a random thought, so I add the RT tag to the subject line. If you've not seen random thoughts before, I stole the idea from apache cocoon and you should brace yourself. The subject line is a tease. This is nothing to do with physical libraries, who I wouldn't dare object to (honest) and all to do with turning libraries into objects. Here, I'm going to explore the use of perl modules by koha a little, or at least the ".pm" files which contain them. I think that the .pm files in koha are used for two purposes at the moment. Some of them are simple libraries, while others are object classes. Libraries are quite simple to evaluate, in a way. You can tell whether libraries are in a sensible structure by using some measures. Two that I know are called "coupling" and "cohesion". Cohesion is a description of the contents of a library. Some common forms are "functional cohesion," "temporal cohesion" and "accidental cohesion". Functional cohesion is what we want: all the things in the library relate to the same task. Temporal cohesion sometimes happens: the things in the library do different tasks, but normally happen around the same time. Sadly, accidental cohesion is most common: it's a rag bag of bits and pieces that have almost nothing to do with each other. Coupling is a description of how two libraries relate to each other, but more vague. If two libraries have "high coupling" with each other, then one requires knowledge of the internal behaviour of another, beyond what is exposed through method calls. Cohesion is almost a given for OO. That may be part of the reason that objects look so nice to software engineers. It solves part of the problem for them. I think it's coupling that normally causes problems for library-based programs that are moving to object orientation. Programs that use libraries with low coupling and functional cohesion normally hold the data that become the objects in the program itself. As the design is refactored, this data becomes part of the "state" of the object, which is normally kept private and accessed through methods belonging to the object. It's actually quite tricky to do the refactoring in a way that still has low coupling without massive changes. Sometimes if you want OO, you have to radically redesign parts of the program. The temptation is to ignore the demands for low coupling and produce programs or libraries that need internal knowledge of the object and objects that show too much of themselves to the outside world. As soon as the object encapsulation has gone, not only do you get high coupling, but you probably damage the cohesion, with one task being implemented across two libraries. That causes all sorts of problems. For example, it reduces the size of unit tests that you can write (and you'd expect me not to like that, wouldn't you?). How do we spot this problem? I don't have an absolute answer. The developers who know their parts of the code might be able to tell from smells. I think a tell-tale sign is when most private data gets exposed to the outside world. If that happens, we should ask just why do we want to be able to access all those parts of the object? Is that object really the right thing to have here? What productive things can we do with this information? We can look at the designs of our own favourite parts of koha and see whether we can organise into functionally cohesive libraries, if we haven't already, and move state from our programs to an object made from our library, if and only if it looks like an object is a good idea. We can look at any objects we've already got and look at how wide open it is. Feel free to question this. I can probably dig up references for parts of it if desired. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef(a)jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/

1 0

Missing headers in 1.2.3
by Abu Obeida O. Bakhach 25 Oct '03

25 Oct '03

HI there, I just installed 1.2.2. I am noticing that the headers are not available, except in the case of Acquisitions and Circulation. By header I mean the 'koha:main menu <catalogu><members>..<home>' that should appear in each page. Was this a 1.2.2 bug? I installed 1.2.3 and it seems to be gone. I am debating to whether fix 122 or go ahead with 123. Thanks in advance, Obeida

2 1

koha 2.0.0pre5 released
by paul POULAIN 24 Oct '03

24 Oct '03

Koha 2.0.0pre5 has been released here : http://sourceforge.net/project/showfiles.php?group_id=16466 RELEASE NOTES ============= This version of Koha is the last one of the 2.0.0 series in the "unstable" tree. 5 libraries are using it, so it's quite useable. 2 last problems have to be solved before 2.0.0RC1 : * biblio deletion : at the moment, biblio deletion is buggy (does not work in MARC, delete only non-marc data) * upgrader is provided for the 1st time, so it's probably buggy. If you want to use Koha, you're welcomed, but you're warned that this version still has some bugs and missing features. INSTALLATION ========== * Download the package * tar xvfz koha-version.tar.gz * cd koha-version * ./installer.pl * follow the instructions. NOTE: You will need to add lines to your main httpd.conf to include /etc/koha-httpd.conf and to make sure it is listening on the right ports (using the Listen directive). Previous versions updated the httpd.conf file, some users thought it was bad/poor decision. UPGRADE from previous 2.0.0preX version ======= * Download the package * tar xvfz koha-version.tar.gz * cd koha-version * ./koha.upgrade * follow the instructions. UPGRADE from previous 1.2.x version ======= This upgrade is possible with this release for the 1st time. EXPECT IT TO HAVE SOME BUGS SOMEWHERE. USE IT ONLY IF YOU KNOW HOW TO GO BACK TO PREVIOUS SITUATION. Otherwise, WAIT for next version or so. * Download the package * tar xvfz koha-version.tar.gz * cd koha-version * ./koha.upgrade * follow the instructions. * launch Koha * Go to Parameters >> Marc structure option and Koha-MARC links option. * Modify default MARC structure to fit your needs. * open a console/term * Enter : cd /path/to/koha/misc export PERL5LIB=/path/to/koha ./koha2marc.pl the old DB is "copied" in the new MARC one. Koha 2.0.0 is ready. BUGFIXES/IMPROVEMENTS ======= BUGS FIXED : +++++++++ 619 : Visiting selectbranchprinter.pl automatically resets branch 618 : Add member process does not check for duplicate barcode 532 : Can't assign new password without changing UserID 599 : edited items are stored incorrectly in old Koha DB (aka : barcode non mandatory bug) 616 : MARCgetbiblio doesn't create leader 500 : [INTRANET]Only 21 items are displayed in the search result 595 : 'Add field' link in /acqui.simple/addbiblio.pl adds incorrect field. 622 : processz3950queue fails 576 : add install locale test 39 : Update Dirs in z3950 scripts 536 : bulkmarcimport.pl generates subtitle error 436 : circulation.pl only partially templated (this bug is partially fixed) IMPROVEMENTS +++++++++ * Polish version of Koha (courtesy of Benedykt) * some useful tools in misc directory to manage the DB * adding "fines" entry in parameters section : to manage fees when a book is returned too late -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0