new member form template abstraction
Greetings, Has anyone started working on an abstraction of the new member forms? Some of the values on the lists appear to be hardcoded into the pages/templates. It would seem useful to allow a per-setup(institution) list of Town names, and localities, perhaps a list of valid Areacodes for members of the institution. It seems to me this would be best done as a small set of tables rather than in the templates themselves. My own background should illustrate my biases here: I work for a system in an urban region of about 2 Million people; my own city, the nominal "capital" of the region is about 500,000. The library I work in has 22 branches within our city, and extensive lending arrangements throughout the larger region. A new patron will register with our system in the context of a primary agency, their "local" branch. The branch records should be accessible for linking into the new patron record as a foreign key, and for display during the registration process. Further, pattern matching logic could be used against postal codes, which are nationally administered, and uniquely identify a neghbourhod (even down to a specific block). In the administrative area, a new branch would be "created" including postal area and contact info. Is any of this making sense ? Cheers, Erik Stainsby Modern Alchemy
Erik, would you mind moving this discussion over to the koha-devel mailing list? koha is really meant to be a users list, and I'm afraid that we're going to be scaring people off if we keep escalating the technical level here. thanks, -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org On Sat, 25 Jan 2003, Erik Stainsby wrote:
Greetings,
Has anyone started working on an abstraction of the new member forms? Some of the values on the lists appear to be hardcoded into the pages/templates.
It would seem useful to allow a per-setup(institution) list of Town names, and localities, perhaps a list of valid Areacodes for members of the institution.
It seems to me this would be best done as a small set of tables rather than in the templates themselves.
My own background should illustrate my biases here: I work for a system in an urban region of about 2 Million people; my own city, the nominal "capital" of the region is about 500,000. The library I work in has 22 branches within our city, and extensive lending arrangements throughout the larger region.
A new patron will register with our system in the context of a primary agency, their "local" branch. The branch records should be accessible for linking into the new patron record as a foreign key, and for display during the registration process.
Further, pattern matching logic could be used against postal codes, which are nationally administered, and uniquely identify a neghbourhod (even down to a specific block).
In the administrative area, a new branch would be "created" including postal area and contact info.
Is any of this making sense ?
Cheers, Erik Stainsby Modern Alchemy _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I'm trying to tighten down a Debian install of Koha. Could someone whack me with a clue-bat and list the required packages (particularly the Apache modules) that Koha requires in a Debian install? TIA. -- Regards, | "A contribution by Microsoft Corporation to South Carolina's . | Republican Party during the 1998 campaign preceded a decision Randy | by the state's GOP attorney general to withdraw from an | antitrust suit against the computer software giant." | Source: API, 24 December 1998
Hi, I have installed Koha 1.2, Apache 1.3 + ldap, i am using Debian packages as below; ii apache 1.3.26-0woody3 Versatile, high-performance HTTP server ii apache-common 1.3.26-0woody3 Support files for all Apache webservers ii libapache-auth 1.6.0-3 LDAP authentication module for Apache ii libapache-auth 0.19-1 LDAP authentication for Apache+mod_perl ii libapache-auth 0.3-2 LDAP access control for Apache+mod_perl ii libapache-mod- 1.4-3 Apache authentication via LDAP directory ii libapache-mod- 1.26-3.0woody1 Integration of perl with the Apache web serv Let me know if you need all Debian packages list or more details as httpd.conf file for example. Regards Serge Randy Edwards wrote:
I'm trying to tighten down a Debian install of Koha. Could someone whack me with a clue-bat and list the required packages (particularly the Apache modules) that Koha requires in a Debian install? TIA.
-- Serge Renaux Groupe ESIEE / CCI Paris EMail:s.renaux@esiee.fr Tel:(33)1.45.92.67.46
Mandi! Randy Edwards In chel di` si favelave...
I'm trying to tighten down a Debian install of Koha. Could someone whack me with a clue-bat and list the required packages (particularly the Apache modules) that Koha requires in a Debian install? TIA.
I'm triying, in spare time, to build a koha debian package, so i think i can reply. ;) [very spare time...] Ok, start reading the installer.pl seems that koha depends on: + perl ;) + apache ;) + libdate-manip-perl + libdbi-perl + libdbd-mysql-perl also depend on: + Set::Scalar that is not a woody/unstable package, but you can build it with dh-make-perl very easy and lead to the libset-scalar-perl_1.17-1_all.deb package. Also depend on: + Net::Z3950 and also this is not in woody nor in unstable. If you try to build with dh-make-perl, as above, you can see in readme that depends on package: + Event again you can build it with dh-make-perl and lead to libevent-perl_0.86-1_i386.deb + MARC (this is present in koha, but...) again dh-make-perl -> libmarc-perl_1.15-1_all.deb + Index Data's Yaz toolkit looking into http://indexdata.dk/yaz/ you can download also the debian package, but this is not present in woody nor unstable. Clearly would be a right suggestion to have some other module for apache authentication and some other bits, but i think that these are not *needed* to run koha. So they are not properly dependencies. Ok, i'm here, i can send you/put somewhere the package i've mentioned, next step will be the build of the Net::Z3950 debian package. Someone would help?! ;) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) gaio(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Difendiamo PeaceLink! Campagna di solidarietà per la tutela legale di una voce scomoda. http://www.peacelink.it/emergenza/
Does anyone have a chunk of httpd.conf that's specifically set up for the installer.pl's default locations (e.g. /usr/local/...) of where it puts things? TIA. Regards, . Randy P.S. Is the 1.2.2 tarball missing from SourceForge deliberate?
On Wed, Jan 29, 2003 at 05:17:00PM -0000, redwards@golgotha.net said:
Does anyone have a chunk of httpd.conf that's specifically set up for the installer.pl's default locations (e.g. /usr/local/...) of where it puts things? TIA.
Regards, . Randy
P.S. Is the 1.2.2 tarball missing from SourceForge deliberate?
Yep, Theres a new 1.2.3 there :-) Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
participants (7)
-
Chris Cormack -
Erik Stainsby -
Marco Gaiarin -
Pat Eyler -
Randy Edwards -
redwards＠golgotha.net
-
Serge Renaux