<FONT SIZE=2>an install script would be really nice... drop in the cd and stand back while the magic happens!<BR>
<BR>
Ed Sharpe archivist for SMECC<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Subj:<B>[Koha] Re: [Koha-devel] For the (non)coder </B><BR>
Date:11/6/01 11:11:32 AM US Mountain Standard Time<BR>
From:<A HREF="mailto:tonnesen@cmsd.bc.ca">tonnesen@cmsd.bc.ca</A><BR>
To:<A HREF="mailto:nsr4n@tetra.mail.virginia.edu">nsr4n@tetra.mail.virginia.edu</A><BR>
CC:<A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel@lists.sourceforge.net</A>, <A HREF="mailto:koha@lists.katipo.co.nz">koha@lists.katipo.co.nz</A><BR>
<I>Sent from the Internet </I><BR>
<BR>
<BR>
<BR>
<BR>
On Tue, 6 Nov 2001, Nicholas Stephen Rosasco wrote:<BR>
<BR>
> Is there any sort of target goal/date (I know MARC/z39.50 "completeness"<BR>
> is coming along soon -- what a fantastic tool that is! thanks!!!) for<BR>
> getting a new version packaged, and are any translation issues for the<BR>
> database for the new format expected?<BR>
<BR>
Chris, of Katipo fame, is trying to convince me to package up a new<BR>
release. I'll probably give it a shot. There are a couple of technical<BR>
issues that I need to work out:<BR>
<BR>
1. how to start the Z39.50 daemon, and make sure it keeps running. There<BR>
are also some issues that I need to work out with the daemon itself.<BR>
Every once in a while it likes to redo all the old queries. :)<BR>
2. how to install the YAZ and Net::Z3950 packages.<BR>
3. script to update existing Koha databases (very scary! Will probably<BR>
have an option to allow backing up the existing databases before doing<BR>
the upgrade). <BR>
4. Need to move away from DebConf for configuring the Koha package. I<BR>
like debconf, but it just isn't portable enough. In its place I'll<BR>
have a script that needs to be run after installing the package (be it<BR>
deb, rpm, or tarball).<BR>
5. Need to set up a preferences configuration system so that Koha admins<BR>
can change system preferences (like which acquisitions module to use).<BR>
6. Need to give some thought to integrating the two acquisitions modules<BR>
so that librarians can use either one at any time.<BR>
7. Permissions controls. This is a big one. I'm not sure how HDL does<BR>
this, but I have a separate package called K12Admin that I use to<BR>
create accounts for all staff and students in my schools. I use this<BR>
package to populate the membership database of Koha, and to create an<BR>
apache password file for authenticating to the librarian interface.<BR>
How should this be handled in the generic case? I'm guessing that<BR>
there should be a superuser account that gets created when the package<BR>
is installed that has access to everything, and the "Members" section<BR>
needs to be modified to allow passwords to be stored for users, as<BR>
well as librarian permissions to be granted. As I said before, this<BR>
isn't a particular itch of mine, as all of this is taken care of by my<BR>
K12Admin program here.<BR>
<BR>
<BR>
I could probably have a package together this week that didn't take of 1,<BR>
2, 5, 6 or 7. Actually, 7 could be semi-taken care of with the superuser<BR>
idea. Then there would be one account that had access to the librarian<BR>
interface. <BR>
<BR>
Anyway, just some random thoughts to get me moving...<BR>
<BR>
<BR>
Steve<BR>
</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>