Status of head (some infos)
Hello all, I've installed, as previously said, what will be Koha 3.0 in 2 libraries. Here is a summary of some missing things that have to be done : Installer ========== i've installed from CVS. the 2.2 installer has to be rewritten almost completly, as : 1- the librarian part of the install is now done through the webinstaller 2- the config file has heavily changed (.conf => .xml) Does anyone plan to work on that in the next 2 months ? MARC editor ============ The actual MARC editor has some limits : - the code is ugly (i've written most of it, I assume the ugliness ;-) ) - the templates are heavy & hard to maintain - the indicators are poorly written - duplicating a field requires a form submission, thus it's slow So, i've asket toins to rewrite the editor. There won't be new major features, it's just a "code cleaning" and "very complex bug fixing". Fines and Overdues =================== SAN-OP has commited some interesting features about fines and overdues. Except they work only if you have fines on overdues. Which is not the cas of every libraries. we will fix this problem asap (1 of our 2 koha 3.0 libraries don't have fines, but they want to be able to know which borrowers have overdues) I'll also have to describe a little bit what SAN-OP features does... Letters ======== The new letters system is not yet used everywhere : suggestion accept or reject for example, still have to be completed Database commit ================ A fresh install from the CVS won't work at all, i'm almost sure. I'll commit a uptodate koha.sql and updated UNIMARC frameworks asap. I'll let libLime or anyone else work on MARC21. waiting for your feedback. Don't hesitate to add entries if i've forgotten something... -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
I've installed, as previously said, what will be Koha 3.0 in 2 libraries. Here is a summary of some missing things that have to be done : Installer ========== i've installed from CVS. the 2.2 installer has to be rewritten almost completly, as : 1- the librarian part of the install is now done through the webinstaller 2- the config file has heavily changed (.conf => .xml)
Does anyone plan to work on that in the next 2 months ? I think MJ has talked about re-doing this, but I'm not sure about
----- "Paul POULAIN" <paul.poulain@free.fr> wrote: the timeline ... MJ?
MARC editor ============ The actual MARC editor has some limits : - the code is ugly (i've written most of it, I assume the ugliness ;-) ) - the templates are heavy & hard to maintain - the indicators are poorly written - duplicating a field requires a form submission, thus it's slow
So, i've asket toins to rewrite the editor. There won't be new major features, it's just a "code cleaning" and "very complex bug fixing". Hmmm ... will he be doing only UNIMARC? or MARC21 also?
Fines and Overdues =================== SAN-OP has commited some interesting features about fines and overdues. Except they work only if you have fines on overdues. Which is not the cas of every libraries. we will fix this problem asap (1 of our 2 koha 3.0 libraries don't have fines, but they want to be able to know which borrowers have overdues) I'll also have to describe a little bit what SAN-OP features does... This sounds great!
Letters ======== The new letters system is not yet used everywhere : suggestion accept or reject for example, still have to be completed Sounds great also.
Database commit ================ A fresh install from the CVS won't work at all, i'm almost sure. I'll commit a uptodate koha.sql and updated UNIMARC frameworks asap. I'll let libLime or anyone else work on MARC21. Something for this Koha Project day I think ...
Some additional things: Re-write Members Entry ================== SAN-OP re-wrote member entry and it doesn't conform to our coding guidelines, we need to fix it. Spruce up Templates ================== The prog templates aren't really suitable for a release. I'm wondering if we could maybe do a contest or something for a new design? Extensive User Testing ================== We need volunteers to test all functionality and document those functional tests. Documentation ================== We need documentation of all the new features (and translations of the ones paul has already done). Well that's all I can think of at midnight on a Saturday :-) Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
1- the librarian part of the install is now done through the webinstaller 2- the config file has heavily changed (.conf => .xml)
Does anyone plan to work on that in the next 2 months ? I think MJ has talked about re-doing this, but I'm not sure about the timeline ... MJ?
I would also be pleased to write this script. I'd need a functional description of what it has to do.
Database commit ================ A fresh install from the CVS won't work at all, i'm almost sure. I'll commit a uptodate koha.sql and updated UNIMARC frameworks asap. I'll let libLime or anyone else work on MARC21. Something for this Koha Project day I think ...
FYI, I've done an installation from CVS, doing at the beginning by hand what a futur misc/install3.pl will do: * cvs checkout * koha.xml creation * empty koha_v3 db creation * I run a browser and I am redirected to /installer/install.pl * installation process blocks at step 3 with an error message: Koha › Web Installer › Step 3 The following error occcurred while importing the database structure: Unknown suffix '-' used for variable 'port' (value '-u') mysql: Error while setting value '-u' to 'port' Please contact your system administrator * In install.pl, I've seen that koha db structure can't be loaded. So I create tables with /installer/kohastructure.sql. * I run koha in a browser and go to the next step: o install basic configuration settings, or, o upgrading from a previous version of Koha. * I import frameworks (unimarc). Everything seems ok, except: * authorites_norme_unimarc.sql ERROR 1216 (23000) at line 680: Cannot add or update a child row: a foreign key constraint fails * Unimarc templates may not be complete, as explained Paul. * Installation is blocked at step 3 on frameworks loading. It seems that installer is expecting Version systemepreference variable to be set to 3.0 value. * I do it by hand: INSERT INTO systempreferences (variable, value) VALUES ('Version', '3') * Koha 3 is installed. * Some tweaking: o template variable is at 'default'. template='prog' and Koha is in French o intranetstylesheet=/intranet-tmpl/prog/en/includes/intranet2.css to have Koha 3 new style sheet. Best regards, -- Frédéric
"Joshua M. Ferraro" <jmf@liblime.com> wrote:
i've installed from CVS. the 2.2 installer has to be rewritten almost completly, as : 1- the librarian part of the install is now done through the webinstaller 2- the config file has heavily changed (.conf => .xml)
Does anyone plan to work on that in the next 2 months ? I think MJ has talked about re-doing this, but I'm not sure about
----- "Paul POULAIN" <paul.poulain@free.fr> wrote: the timeline ... MJ?
I'm spending a bit more time on it later today (Monday BST), but the basic problem remains: How to install cgi-bin and config files neatly with MakeMaker? (or another portable solution) I really want to avoid building a new brittle installer if possible. [...]
Extensive User Testing ================== We need volunteers to test all functionality and document those functional tests. Documentation ================== We need documentation of all the new features (and translations of the ones paul has already done).
We need developers to call for tests and docs when they add stuff. Frédéric <frederic@tamil.fr> wrote:
I would also be pleased to write this script. I'd need a functional description of what it has to do.
If we had a functional description (and the default .xml and .sql files), it wouldn't be so hard to do! But, as you quote from Paul's email:
A fresh install from the CVS won't work at all, i'm almost sure. which is rather a hindrance for installer development!
The new installer will replace these steps:
* cvs checkout * koha.xml creation
but only suggest how to do this, with example mysql commands:
* empty koha_v3 db creation
and configuring the webserver, as that's where all the local differences cause problems and where we need total flexibility. Regards, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
(it is just my proposal) hdl wrote installer/webinstall.pl for the librarian part of the install. It requires : - having the virtualhost up and running - having mysql login/password The installer : - creates the database from kohastructure.sql - let the user choose some files to updload to get a working koha immediatly. The later requiring to have files in misc/sql-datas/<language>/<level> I don't have updated french files,but I'll do it quickly. I've fixed a bug in installer, I think it works better now. So, the technical part of the setup just requires : - install the app somewhere. I think we could keep the exact directory structure we have in CVS. one virtual host having cgi-bin pointing to /opac, the intranet one pointing to / The security risk risk (executing a script in misc for example) could be avoided with a .htaccess) I don't think we need to to things too much complex. - write httpd.conf - write koha.conf -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Paul POULAIN <paul.poulain@free.fr> wrote:
The later requiring to have files in misc/sql-datas/<language>/<level>
Does misc have to be alongside installer? It would be good if sql-datas could be somewhere outside the cgi-bin tree. [...]
- install the app somewhere. I think we could keep the exact directory structure we have in CVS. one virtual host having cgi-bin pointing to /opac, the intranet one pointing to / The security risk risk (executing a script in misc for example) could be avoided with a .htaccess) I don't think we need to to things too much complex.
I think I disagree - I'd really like to keep the cgi-bin in one tree and other file types in other trees, to stop people somehow executing a template, C4 module or config file. Makefile.PL now in CVS HEAD is a start of this. perldoc should show the documentation for it.
- write httpd.conf - write koha.conf
These will be made by a Makeconfig.PL which I've yet to commit. Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
Paul POULAIN <paul.poulain@free.fr> wrote:
The later requiring to have files in misc/sql-datas/<language>/<level>
Does misc have to be alongside installer? It would be good if sql-datas could be somewhere outside the cgi-bin tree. I think the sql-datas files should be moved ouside of the misc
----- "MJ Ray" <mjr@phonecoop.coop> wrote: dir, and the sql-datas dir itself should be re-named IMO. I'd suggest something like: koha/installer/data/sql
- install the app somewhere. I think we could keep the exact
[...] directory
structure we have in CVS. one virtual host having cgi-bin pointing to /opac, the intranet one pointing to / The security risk risk (executing a script in misc for example) could be avoided with a .htaccess) I don't think we need to to things too much complex.
I think I disagree - I'd really like to keep the cgi-bin in one tree and other file types in other trees, to stop people somehow executing a template, C4 module or config file. Makefile.PL now in CVS HEAD is a start of this. perldoc should show the documentation for it. I tend to agree with Paul here ... a well written .htaccess can eliminate any security problems and keeping the installation tree identical to the cvs tree makes testing and updating an installation much much simpler.
- write httpd.conf - write koha.conf
These will be made by a Makeconfig.PL which I've yet to commit. I'm planning on testing this out today, I'll let you know how it goes.
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Joshua M. Ferraro a écrit :
So, i've asket toins to rewrite the editor. There won't be new major features, it's just a "code cleaning" and "very complex bug fixing". Hmmm ... will he be doing only UNIMARC? or MARC21 also?
if you're speaking of marc21 plugins, then he will update them as well as unimarc plugins. If you're speaking of something else, pls explain, and remember that it will be essentially a code cleaning.
Database commit ================ A fresh install from the CVS won't work at all, i'm almost sure. I'll commit a uptodate koha.sql and updated UNIMARC frameworks asap. I'll let libLime or anyone else work on MARC21. Something for this Koha Project day I think ...
kohastructure.sql commited
Re-write Members Entry ================== SAN-OP re-wrote member entry and it doesn't conform to our coding guidelines, we need to fix it.
nice to read cheers -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
participants (4)
-
Frédéric -
Joshua M. Ferraro -
MJ Ray -
Paul POULAIN