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

Bug fix
by Andrés Tarallo 12 Nov '04

12 Nov '04

Today we've been hunting a strange BUG. While doing that we updated the C4 modules from the latest one in the CVS. Our test instlation is 2.1.2 version of Koha. Attached below you'll find a patch with some bugfixes for the Auth.pm module. Maybe calling them bugs is not a good idea, but we took away some annoying messages from the logs. Any feedback is welcome Andres

1 0

Users table
by Ernesto Silva - Webmaster 11 Nov '04

11 Nov '04

hi, what is the "users" table for? is it deprecated? it seems to me that all permissions are managed in the borrower's flags. Regards -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law.

1 0

member-flags.pl patch
by Ernesto Silva - Webmaster 11 Nov '04

11 Nov '04

Hi, We are using Koha version 2.1.2 and we detected that the user flags didn't show up. This is one possible patch. Regards. -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law. --- member-flags.pl.original 2004-11-11 11:28:00.684539200 -0300 +++ member-flags.pl 2004-11-11 12:17:10.340123392 -0300 @@ -58,8 +58,14 @@ $sth->execute($flags, $member); print $input->redirect("/cgi-bin/koha/members/moremember.pl?bornum=$member"); } else { - my ($bor,$flags,$accessflags)=getpatroninformation(\%env, $member,''); - +#---------------------------------------------------------------------------- +# 11-11-2004 - Ernesto Silva (silva(a)ort.edu.uy) - member flags didn't show up +# because getpatroninformation returned a complex "borrower" object not a list. +# More information in: C4/Circulation/Circ2.pm - line 238 + my $bor = getpatroninformation(\%env, $member,''); + my $flags = $bor->{'flags'}; + my $accessflags = $bor->{'authflags'}; +#---------------------------------------------------------------------------- my $dbh=C4::Context->dbh(); my $sth=$dbh->prepare("select bit,flag,flagdesc from userflags order by bit"); $sth->execute;

1 0

[Fwd: [Koha] Koha Docs]
by Stephen Hedges 09 Nov '04

09 Nov '04

Note to developers - I decided to use the GNU Free Documentation License ("copyleft") on these documents, with disclaimer, too. While this may seem like it's overly protective, the copyright belongs explicitly to the author, and he/she can always choose to make it looser later. (Though I think it would be very difficult or impossible to make it tighter later.) Meanwhile, the documents should be free enough for most purposes. I also decided to use version numbering related to the software version, as much as possible. So if a document refers mainly to Koha version 2.0.0, for example, the initial version will be 2.0.0, the first revision would be 2.0.0p1, etc. Many thanks to everyone for the helpful suggestions and information. Stephen ---------------------------- Original Message ---------------------------- Subject: [Koha] Koha Docs From: "Stephen Hedges" <shedges(a)skemotah.com> Date: Tue, November 9, 2004 2:04 pm To: koha(a)lists.katipo.co.nz -------------------------------------------------------------------------- I have begun the process of loading some Koha documents to Sourceforge, which will be the repository for Koha docs until we come up with a better place to store them. Look in koha-doc/en/general and you will find the "official" XML version of Brooke's "Newbie Guide" from the Koha wiki, as well as an HTML conversion of the XML source. Look in koha-doc/en/sysadmin/migration and you'll find the XML and HTML of my "Migrating to Koha" document. I'm working on Nick Rosasco's official Koha Manual (for version 1.2.3) as well as Paul's brochure for version 2.2.0 (in both French and English). I'm open to suggestions for more documents to transfer to XML and load to Sourceforge, so send 'em my way! -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com _______________________________________________

2 1

EU Library Barcode Identification Standard (slightly off-topic)
by Bruffey, Mark 08 Nov '04

08 Nov '04

Our seminary has an extension in Romania. I am attempting to set up a barcode system for the library there. I know that a number of participants this list are in the EU. Is there a standard for library identification by barcode in the EU? If there is, I would like to use that as a model, or try to conform to it. For instance, here in Minnesota, MINITEX assigns a unique combination of the 1st 5 or so digits of barcode to each library in Minnesota. Is there a similar standard in the EU? Sincere thanks for your consideration of this off-topic post. Best, Mark Bruffey, Minneapolis MN.

1 0

Document revision numbering system
by Stephen Hedges 05 Nov '04

05 Nov '04

Hi all - As I am working on moving Koha docs to XML, I would like to start using a uniform system of numbering document revisions. I noticed while working on converting the SGML version of Nick Rosasco's manual that he had numbered the first version as "0.1." So what should I now use for the new XML revision? "0.2" obviously, but what would then justify moving to version 1.0? A google search didn't produce any results that were really helpful. I did see that Gnome documentation is supposed to be numbered according to the version of Gnome that is current. In other words, if a document is produced when Gnome version 1.x is the most current, then that document version starts with "1" and so forth. (For example, the first version of a document produced when Gnome 2.x is the most current would be version 2.0, the next revision would be 2.1, etc., until Gnome version 3.0 is released.) I suppose we could do something similar for Koha. That would change Nick's version 0.1 to 1.0, and the XML version to 1.1, while Brooke's Newbie Guide would be version 2.0 right from the start -- which seems a little confusing to me. Does anybody have any suggestions and/or strong feelings about a document revision numbering system? -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

4 3

KohaWiki defaced daily
by MJ Ray 05 Nov '04

05 Nov '04

http://www.koha.org/wiki/ is being attacked by linkspammers almost every day. Recently, they have become more destructive, wiping out acres of material, such as on the QuestionsPosed page. I'm against forcing user registration, but can we take some other action against these? Maybe some simple way to mark a change as spam, revert to the previous and flag it for the admin to look at (to ban IPs, contact remote network admins or whatever). It's not as easy to deal with total destruction of pages, unlike the simple "add links to end of page" spam we used to get. -- MJR/slef My Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ Unsolicited attachments to the pipex address deleted Will HLF fund tree-killings? http://www.thewalks.co.uk/

3 4

help needed
by Andre du Plessis 04 Nov '04

04 Nov '04

Hi Can KOHA keep track of circulation history? Thus, can it keep records for all the people who had a specific book over a period of time? Andre du Plessis

2 1

mod_perl bug: fixed
by Ernesto Silva 04 Nov '04

04 Nov '04

Hi, Our koha installation is running on SuSE 9.1 with apache2 and mod_perl. We found a bug in the admin/marc_subfield_structure.pl in the intranet, it works fine as a cgi but fails in mod_perl mode. We fixed it so now runs via mod-perl and via pure cgi. Please re-fix it if it's not technically right. Regards -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law.

1 0

Additional item information
by Andrés Tarallo 04 Nov '04

04 Nov '04

Our current library system holds in one of its database many information specific to the item This information is mostly about who asked for the the item , who autorized it, where was purchased, how much we paid for .... . We're mapping this information to free subfields in the 952 field (we use it for koha-marc item mapping). On the other side our librarians are intraducing manually a few books in order to gain experience with Koha. They pointed out us that they can't load this subfields. We've been investigating and found out that only the fields that have a mapping in the non-marc (koha.item table) database are requested for a new item or biblio. We need to keep this information,is badly needed for our librarians. We're asking for your advice. One Possible solution is adding our needed fields in the koha.item table, but we're aware that we will open from the mainstream development, we're willing to contribute back our changes; but we think that they could be useless for most koha users. Thanks in advance Andres

1 0