Hello all, I've added in CVS a misc/rebuildnonmarc.pl script : run this script when you change a link between marc and non MARC DB. It rebuilds the non-MARC DB (long operation) Note : don't forget to export PERL5LIB=/path/to/koha before running this script. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-10-14 10:53:06 +0100 paul POULAIN <paul.poulain@free.fr> wrote:
I've added in CVS a misc/rebuildnonmarc.pl script : run this script when you change a link between marc and non MARC DB. It rebuilds the non-MARC DB (long operation)
Paul, Why do we not use views? Is there a way that we can trigger this script, running it automatically when needed? Probably we are approaching the point where we need a "housekeeper" program, suitable for running from cron. -- MJR/slef My Opinion Only and possibly not of any group I know. http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
MJ Ray wrote:
On 2003-10-14 10:53:06 +0100 paul POULAIN <paul.poulain@free.fr> wrote:
I've added in CVS a misc/rebuildnonmarc.pl script : run this script when you change a link between marc and non MARC DB. It rebuilds the non-MARC DB (long operation)
Paul,
Why do we not use views?
???
Is there a way that we can trigger this script, running it automatically when needed?
imho, it's not a good idea to run it without human confirmation => it takes minuts to run, and uses 100% CPU. Worst that this : if the user makes a mistake, he can loose data (not with rebuildnonmarc.pl, but with cleanmarcdb.pl, he can) However, we could imagine a way to "validate" the "cron request", that would be run every night. In this "cron request", we could have a trigger "2" => always asked "1" => asked, "0" => not asked. Every night, each operation asked, when done reports status in the "cron request table", and change every "1" to "0", to be sure it won't be done next night again.
Probably we are approaching the point where we need a "housekeeper" program, suitable for running from cron.
you're right. But, as usual : do we have a volunteer ? Which task is more important : * debugging & releasing a good 2.0.0 version ? (everybody agrees this task is the 1st one to do :-) ) but after, should we : * document & code cleaning * add missing "minor" features (LDAP,...) * add major features like serials, report generator ? * move the default template to xhtml with css positionning ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-10-20 15:04:26 +0100 paul POULAIN <paul.poulain@free.fr> wrote:
Why do we not use views? ???
Someone off-list reminded me why: koha uses MySQL and MySQL still cannot do views.
you're right. But, as usual : do we have a volunteer ? Which task is more important : * debugging & releasing a good 2.0.0 version ? (everybody agrees this task is the 1st one to do :-) )
We still seem to have some way to go on this. I have started doing daily burn tests and will file any bugs that I find. Today was mostly install bugs, with other ones being things I can handle too.
but after, should we : * document & code cleaning
Documenting is essential and should be added to 2.0, then merged across to 2.1 series. Code cleaning is 2.1 stuff, I think.
* add missing "minor" features (LDAP,...) * add major features like serials, report generator ?
These are 2.1 stuff too.
* move the default template to xhtml with css positionning ?
This is essential and should be added to 2.0. Failing accessibility is a bug to me, as you know, and that includes any mandatory Javascript. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
participants (2)
-
MJ Ray -
paul POULAIN