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

Date defaults in pendingreserves.pl (holds to pull report)
by Wagner, Jane 20 Mar '09

20 Mar '09

The pendingreserves.pl script is defaulting to a date range of 10 years ago to yesterday. However, the last bit of the below part of the script -- the if !defined($startdate) piece -- seems to be implying that other start and end dates could be provided. I'm not finding any place where other dates can be set by the user before the report is run. After it runs (first entry into screen), the user can change dates in the Refine Results section. Is there a syspref I'm missing, or somewhere else, that the user can specify different dates as a default? Thanks. my $todaysdate = sprintf("%-04.4d-%-02.2d-%02.2d", $year, $month, $day); my $yesterdaysdate = sprintf("%-04.4d-%-02.2d-%02.2d", Add_Delta_YMD($year, $month, $day, 0, 0, -1)); # Find 10 years ago for the default shelf pull start and end dates # A default of the prior day's holds is a reasonable way to pull holds my $pastdate = sprintf("%-04.4d-%-02.2d-%02.2d", Add_Delta_YMD($year, $month, $day, -10, 0, 0)); # Predefine the start and end dates if they are not already defined $startdate =~ s/^\s+//; $startdate =~ s/\s+$//; $enddate =~ s/^\s+//; $enddate =~ s/\s+$//; # Check if null, should string match, if so set start and end date to yesterday if (!defined($startdate) or $startdate eq "") { $startdate = format_date($pastdate); } if (!defined($enddate) or $enddate eq "") { $enddate = format_date($yesterdaysdate); } Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner(a)ptfs.com

3 5

Re: [Koha-devel] [Koha] Item Type Defined in MARC
by Doug Dearden 20 Mar '09

20 Mar '09

Ed, Take a look at the script. That is largely what it does. My notes at the beginning speak to this, that is parses the FSC line using the @ delimiter, and where you can modify it for your item types. The simple MarcEdit move this to there function won't cut it. Doug >>> "Roche III, Edward" <edward_roche(a)solanco.k12.pa.us> 3/20/2009 10:05 AM >>> Ok...I can move the $x data to a dummy field but does anyone know how to strip the @a from the field so I can move it to the $y in 952? Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" -----Original Message----- From: koha-devel-bounces(a)lists.koha.org [mailto:koha-devel-bounces@lists.koha.org] On Behalf Of Roche III, Edward Sent: Thursday, March 19, 2009 2:35 PM To: Doug Dearden Cc: koha-devel(a)lists.koha.org Subject: Re: [Koha-devel] [Koha] Item Type Defined in MARC Thank you this helps a lot. Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" -----Original Message----- From: Doug Dearden [mailto:dearden@sarsf.org] Sent: Thursday, March 19, 2009 2:03 PM To: Joe Atzberger; Doug Dearden; Roche III, Edward Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Item Type Defined in MARC Just looked again, also put it into 942$c. Doug >>> "Doug Dearden" <dearden(a)sarsf.org> 3/19/2009 11:57:21 AM >>> Ed, I believe your answer is in here: =952 \\$bFiction$hFIC DLA$pT0025982$t1$xFSC@aR@b148@c20081014@i1@jHardcover@fFollett$xFUND: District$aSHS The $x fields contain the detail info that was exported from Follett. I think the item code you are looking for in this example is "R". The string that starts $xFSC has fields that are delimited by "@". The item type is in the @a field. The script I sent and later posted to the web site contains code to do the conversion, if you use it you need to modify it to convert from your Follett item type codes to your koha item type codes. Looking at the script I put it into the 952$y field. Best, Doug >>> "Roche III, Edward" <edward_roche(a)solanco.k12.pa.us> 3/19/2009 11:34:27 AM >>> That is what I am trying to do . The only thing I can find for Follett is it put a 3 character code in the LDR field at position 5, 6 and 7 to represent the type of item. Anyone that migrates from Follett how did you assign your item types? Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" From: Joe Atzberger [mailto:ohiocore@gmail.com] Sent: Thursday, March 19, 2009 12:59 PM To: Roche III, Edward Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Item Type Defined in MARC You should create the itemtype codes in Koha to match your data, or edit your data to match your new codes. The question you are asking is better directed to a FOLLETT group regarding where that system outputs itemtype. --Joe 2009/3/19 Roche III, Edward <edward_roche(a)solanco.k12.pa.us> Good Morning All Does anyone know where in MARC is the item type defined? In my exported data from Follett I don't see anything that looks like the item type codes that are in Koha. Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" _______________________________________________ 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 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

1 0

Re: [Koha-devel] [Koha] Item Type Defined in MARC
by Roche III, Edward 20 Mar '09

20 Mar '09

Thank you this helps a lot. Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" -----Original Message----- From: Doug Dearden [mailto:dearden@sarsf.org] Sent: Thursday, March 19, 2009 2:03 PM To: Joe Atzberger; Doug Dearden; Roche III, Edward Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Item Type Defined in MARC Just looked again, also put it into 942$c. Doug >>> "Doug Dearden" <dearden(a)sarsf.org> 3/19/2009 11:57:21 AM >>> Ed, I believe your answer is in here: =952 \\$bFiction$hFIC DLA$pT0025982$t1$xFSC@aR@b148@c20081014@i1@jHardcover@fFollett$xFUND: District$aSHS The $x fields contain the detail info that was exported from Follett. I think the item code you are looking for in this example is "R". The string that starts $xFSC has fields that are delimited by "@". The item type is in the @a field. The script I sent and later posted to the web site contains code to do the conversion, if you use it you need to modify it to convert from your Follett item type codes to your koha item type codes. Looking at the script I put it into the 952$y field. Best, Doug >>> "Roche III, Edward" <edward_roche(a)solanco.k12.pa.us> 3/19/2009 11:34:27 AM >>> That is what I am trying to do . The only thing I can find for Follett is it put a 3 character code in the LDR field at position 5, 6 and 7 to represent the type of item. Anyone that migrates from Follett how did you assign your item types? Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" From: Joe Atzberger [mailto:ohiocore@gmail.com] Sent: Thursday, March 19, 2009 12:59 PM To: Roche III, Edward Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Item Type Defined in MARC You should create the itemtype codes in Koha to match your data, or edit your data to match your new codes. The question you are asking is better directed to a FOLLETT group regarding where that system outputs itemtype. --Joe 2009/3/19 Roche III, Edward <edward_roche(a)solanco.k12.pa.us> Good Morning All Does anyone know where in MARC is the item type defined? In my exported data from Follett I don't see anything that looks like the item type codes that are in Koha. Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" _______________________________________________ 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 1

Koha 3.0 with postgresql
by florian litot 19 Mar '09

19 Mar '09

Hi, I would like to install Koha 3.0 wiht postgresql but the script on the installation is not good Somebody install this and help me? thank you Regards Florian Litot

2 1

bugs.koha.org upgrade 3/18/2009
by Galen Charlton 19 Mar '09

19 Mar '09

Hi, LibLime is moving the Koha bugs database to a new server tomorrow. In the process, we'll be upgrading the software to Bugzilla version 3. In order to copy the database and give time for a DNS change to propagate, we'll be freezing the bugs database between 18:00 and 20:00 UTC-4 (22:00 and 24:00 UTC) tomorrow. Thanks to Clay Fouts for performing the upgrade. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 1

Fwd: Koha 3 vmware appliance download error
by Kyle Hall 18 Mar '09

18 Mar '09

I received this email, I'm not sure who is handling contribs.koha.org right now. Hi Kyle, I'm sorry to take a little bit of your time but i'm trying to download your vmware appliance of Koha 3 at this location : http://contribs.koha.org/revision_view.php?rid=14 And i'v got a 403 http error code. Do you know if i can download it from another location ? Thx in advance and sorry to disturb you, Laurent PERRIER http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) ---------- Forwarded message ---------- From: <laurent.perrier(a)nimes.fr> Date: Wed, Mar 18, 2009 at 6:22 AM Subject: Koha 3 vmware appliance download error To: kyle.m.hall(a)gmail.com Hi Kyle, I'm sorry to take a little bit of your time but i'm trying to download your vmware appliance of Koha 3 at this location : http://contribs.koha.org/revision_view.php?rid=14 And i'v got a 403 http error code. Do you know if i can download it from another location ? Thx in advance and sorry to disturb you, Laurent PERRIER _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 2

Koha database installation
by Edisnel Carrazana Castro 18 Mar '09

18 Mar '09

Greetings, I have the fallowing question: How can I to install Koha (the aplication) in one server, with the database in other server. It is possible to do that?

4 3

LDAP replication without update
by Dobrica Pavlinusic 16 Mar '09

16 Mar '09

Let me quickly explain our situation: we want to get data from ldap for new users, but allow librarians to edit data in Koha, and preserve this changes. Logical solution would be to turn replication on, and update off in /etc/koha/koha-conf.xml with something like this: <replicate>1</replicate>  <update>0</update>  but that doesn't work. I tracked problem to || 1 in Auth_with_ldap.pm which always turn both options on no matter what user specifies in xml file. Attached patch fixes this problem. We also needed to augment data available in LDAP with data from CSV files generated by other systems, so I wrote ldap rewriter documented in following blog post: http://blog.rot13.org/2009/03/virtual_ldap_rewrite_or_augment_data_on_the_f… It's somewhat specific for our needs, but I hope that it will also be useful to other as food for thought if nothing else. -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

2 1

Re: [Koha-devel] Bug#389876: ITP: koha -- web-based library catalogue (ILS/OPAC)
by Vincent Danjean 16 Mar '09

16 Mar '09

MJ Ray wrote: > "Trent W. Buck" <trentbuck(a)gmail.com> wrote: [...] >> Firstly, what is the status of the ITP? Chris (part of the upstream >> Koha team) told me in #koha that in Lenny the dependencies are all >> resolved, so I guess that all that remains is to package Koha itself. > > I've asked Chris Cormack about that on #koha just now. I thought > we're still two short: Class::Adapter and SMS::Send. It will be easy to put them in lenny-backport if needed. >> How far along are you with that? > > There's the collab-maint tree that you're probably aware of. > I'm currently testing a clean install at a client site. > > The thorny problems are the ones where the koha installation usually > "interferes" with mysqld and wider system settings. > >> I looked briefly at upstream yesterday, and it seems to me that at a >> minimum you will want a -common package (due to the large amount of >> architecture-independent data files) and as there are apparently 50MB >> of translation files, possible also seperate koha-language-<ISO 639> >> packages. > > Yes, I'd agree with that split as a minimum. I'm open to suggestions > about whether we want libkoha-perl and koha packages split or not. collab-maint tree is a work-in-progress I did and that I never had time to complete. It already splits koha into several packages more or less automatically (ie manual debian/rules target to (re-)create all language packages in debian/control, ...) For now, the koha is split in: Package: koha-config: koha-config provides several files and scripts used by the other koha package to handle its configuration. This package will be automatically pulled when needed. [see below for more information] Package: koha-common: This package include base-files of koha. Unless you have very specific needs, you would like to install koha-zebra or koha-nozebra that provides a default configuration. Package: koha-nozebra Koha-nozebra is dedicated to small libraries who need who do not need the power of the IDZebra search engine. Package: koha-zebra Koha with zebra Package: koha-zebra-pazpar2 Koha with zebra and pazpar2 (not ready at all since pazpar2 is not yet packaged) Package: koha-zebra-server This package configures an instance of IDZebra to be used with Koha. Package: koha-pazpar2-server This package configures an instance of PazPar2 to be used with Koha. Package: koha This metapackage install the full-featured koha system (koha-zebra) and all Koha localisation packages. Package: koha-l10n-XX This package contains the localization of Koha in XXXXXXX Idea: * koha-config and koha-common are helper packages (not really useful on their own) * koha-nozebra, koha-zebra, and koha-zebra-pazpar2 are mostly empty packages that only depends on koha-common and koha-config and provide a good default configuration. * koha-zebra-server and koha-pazpar2-server can be installed on other host than the koha web-application (so koha-zebra recommends koha-zebra-server but does not depend on it) Managing mysqld settings is not really a problem: dbconfig-common is here to help. But I hit several problems: - the perl parser must be selected system-wide. I already wrote on the Koha ML to ask them to manually select the parser directly in the Koha code. I do not know if all required modification have been done - several configuration files (in particular /etc/koha/koha.conf) are used by different programs that will be in different packages. I need to know a precise description of all settings (in particular all settings in /etc/koha/koha.conf) and I need to know which programs use each of them => note to koha developers: it would be easier if different programs have different configuration files - koha comes with a lot of scripts/utilities in /usr/share/koha/bin I need a description of their goal and of their use (how and when should we use them) I will try to setup a wiki page with all these questions. When they will be answered, it will be possible to finish the Debian Koha packaging. And any help is welcome of course. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanjean(a)debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main

2 1

Possible bad patch to stable
by Joe Atzberger 16 Mar '09

16 Mar '09

A user ("imp") on IRC reported being unable to add patrons to a new installation of 3.00.01.005 because of the error "This patron does not exist." Of course that doesn't make any sense when one is trying to add a new patron. Their logs also showed: [Sun Mar 15 18:20:19 2009] [error] [client 172.16.1.164] [Sun Mar 15 18:20:19 2009] memberentry.pl: Use of uninitialized value in string eq at /mnt2/koha-install/intranet/cgi-bin/members/memberentry.pl line 139., referer: http://10.23.42.14:8080/cgi-bin/koha/members/memberentry.pl?op=add&cate… [Sun Mar 15 18:20:19 2009] [error] [client 172.16.1.164] [Sun Mar 15 18:20:19 2009] memberentry.pl: DBD::mysql::st execute failed: Column 'surname' cannot be null at /mnt2/koha-install/lib/C4/Members.pm line 768., referer: http://10.23.42.14:8080/cgi-bin/koha/members/memberentry.pl?op=add&cate… I have some problems with this patch introduced 8 days ago: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commit;h=239700d079ca6c33d3… Maybe it is unrelated, but that patch includes unnecessary changes to memberentry.pl (all whitespace... on a stable release?) and an apparently unconditional warn statement in Members.pm. I suggest it should be reverted and the addition of new patrons retested via STAFF interface. The symptoms as reported would seem to affect all users trying to add patrons w/ the current stable codebase. --Joe

3 2