Bug 67 - admin script for editing z39.50 servers
Summary: admin script for editing z39.50 servers
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: 1.2.x
Hardware: PC All
: P2 normal (vote)
Assignee: Chris Cormack
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-10 04:24 UTC by Chris Cormack
Modified: 2012-10-24 21:03 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-20 23:26:04 UTC


---- Reported by tonnesen@cmsd.bc.ca 2002-07-10 04:24:48 ----

 



---- Additional Comments From micheas@micheas.dyns.net 2002-07-11 17:54:41 ----

From an admins point of view, the ideal would be to have the list of servers
stored as a flat text file in /etc/koha/ so that commandline Junkies, like
myself can edit the list with vim and cat the list to mail and all sorts of
other mundane admin tasks.  But this more of an enhancement than a bug.  Thanks. 



---- Additional Comments From tonnesen@cmsd.bc.ca 2002-07-11 18:03:26 ----

I was under the impression that it might be _librarians_ and not _technicians_
that will be setting and editing Z39.50 servers.  I certainly agree it would be
a whole lot easier for me to just create a section of koha.conf for z39.50
servers or something like that, but the librarians might prefer it to be
editable in the web interface?



---- Additional Comments From micheas@micheas.dyns.net 2002-07-11 18:39:43 ----

I was hoping for both :-)
I was thinking that the webpage would read and write to the file.



---- Additional Comments From am12@bolis.com 2002-07-12 02:18:58 ----

Commandline junkies should be able to run

  mysql -uUSER -pPASS Koha  <<END
  select * into outfile '/tmp/z3950servers' from z3950servers;
  END

from their script.

Let's keep the application consistent, and all data
in the database.  The only thing that should be in
/etc/koha.conf is minimal bootstrap info to find the
code and database.  All other operational data
should be in the DB.



---- Additional Comments From am12@bolis.com 2002-07-12 02:24:57 ----

Better yet, the new code hopefully will have some new
subroutines in C4::Z3950.pm  along the lines of
addz3950server, getz3950serverlist, etc.  Please?

A command-line junkie should be able to have/create/use 
a 5-line wrapper script to those.  And this way
the command-line script will work with both MySQL
and PostgreSQL.




---- Additional Comments From micheas@micheas.dyns.net 2002-07-12 06:04:30 ----

I have an active firewall so I will need to see the portnumbers to punch holes
for  z3950 servers on odd ports (it almost seems that people use a random number
generator to pick there port number instead of port 210) having the portnumbers
in a flat file is just easier than getting the info from mysql.  I'm pretty low
on the people to make life easy for :-)
Thanks for taking note.



---- Additional Comments From tonnesen@cmsd.bc.ca 2002-10-26 07:30:09 ----

Added



--- Bug imported by chris@bigballofwax.co.nz 2010-05-20 23:26 UTC  ---

This bug was previously known as _bug_ 67 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=67

Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was tonnesen@cmsd.bc.ca.