Do we have a date for the next tarball? Already many bugs from pre5 in the installer and upgrader are fixed. I know at least one really nasty template bug was fixed. I want to make sure the other z3950 fixes are in before pre6 (or rc1?). -- 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/
MJ Ray wrote:
Do we have a date for the next tarball? Already many bugs from pre5 in the installer and upgrader are fixed. I know at least one really nasty template bug was fixed. I want to make sure the other z3950 fixes are in before pre6 (or rc1?).
I would like to add biblio deletion before releasing the next version. And if someone (katipo ?) tried to migrate a 1.2 version in 2.0, pls report success/failure, as the pre5 had a migration tool for the 1st time. feedback required. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-11-05 09:11:38 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
I would like to add biblio deletion before releasing the next version.
I would like to have this working, but not restructured. I have been told that state-funded UK libraries may need to keep records of deleted books until their next audit. I am trying to get more details about this.
And if someone (katipo ?) tried to migrate a 1.2 version in 2.0, pls report success/failure, as the pre5 had a migration tool for the 1st time. feedback required.
I have used koha.upgrade from current CVS on a pre3 system and a 1.2.3 system, successful as far as I know yet. The koha.upgrade in pre5 did not work for my pre3 system, so I rewrote it to use Install.pm more. A little work still remains on that, but it is usable. Does that help pick a target date? -- 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/
On 2003-11-05 09:11:38 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
I would like to add biblio deletion before releasing the next version.
I would like to have this working, but not restructured. I have been told that state-funded UK libraries may need to keep records of deleted books until their next audit. I am trying to get more details about this.
Koha currently moves things to a "deleted" table is that right? Are you talking about a purge of that table, or really deleting things instead of making the move, or just making that move? I think we would agree that biblios shouldn't be deleted off disk as a matter of course unless basically people are running out of disk space, or wish to purge. If I was to take a stab, I'd think that biblios shouldn't be "really deleted" for a year, for exactly the sort of reasons that MJR mentions Cheers R _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications WEBMISTRESS ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org
Rachel Hamilton-Williams wrote:
On 2003-11-05 09:11:38 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
I would like to add biblio deletion before releasing the next version.
I would like to have this working, but not restructured. I have been told that state-funded UK libraries may need to keep records of deleted books until their next audit. I am trying to get more details about this.
Koha currently moves things to a "deleted" table is that right? Are you talking about a purge of that table, or really deleting things instead of making the move, or just making that move? I think we would agree that biblios shouldn't be deleted off disk as a matter of course unless basically people are running out of disk space, or wish to purge.
If I was to take a stab, I'd think that biblios shouldn't be "really deleted" for a year, for exactly the sort of reasons that MJR mentions
I mean : For instance, nothing is deleted in MARC-DB. And you can't delete from MARC view of the biblio. That's trully a problem :-) I plan to : * write MARCdelbiblio & MARCdelitem * write NEWdelbiblio & NEWdelitem * modify OLDdelbiblio & OLDdelitem to delete MARC stuff too * add a column (blob) in deletedbiblio => the MARC version of the biblio will be stored in this field. Same for items. HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-11-06 08:12:03 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
For instance, nothing is deleted in MARC-DB. And you can't delete from MARC view of the biblio. That's trully a problem :-)
Why? Should deleting unattached MARC be a job for a maintenance script and not something that the librarian interface does? Could someone tell me a bit more about MARC*, OLD* and NEW* functions? I thought OLD* was non-MARC and NEW* was MARC, but that doesn't explain MARC*. -- 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/
MJ Ray wrote:
On 2003-11-06 08:12:03 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
For instance, nothing is deleted in MARC-DB. And you can't delete from MARC view of the biblio. That's trully a problem :-)
Why? Should deleting unattached MARC be a job for a maintenance script and not something that the librarian interface does?
Could someone tell me a bit more about MARC*, OLD* and NEW* functions? I thought OLD* was non-MARC and NEW* was MARC, but that doesn't explain MARC*.
It's written at the beginning of Biblio.pm : * 4 types of subs : MARC*, OLD*, NEW* and not(MARC,OLD,NEW)* : - not(MARC,OLD,NEW) => comes from 1.2 koha. They are just a wrapper to OLD* then MARC* - NEW* => full MARC api => call MARC* then OLD* - MARC* => the real MARC stuff. Deals ONLY WITH MARC-DB - OLD* => the real non-MARC stuff. Deals ONLY WITH NON MARC-DB all OLD* subs contains a copy/paste from the catalogue.pm in 1.2 (except for the "OLD" that has been added) all non(MARC,OLD,NEW) subs comes from 1.2 between MARC and OLD calls, I use a MARCkoha2marc or a MARCmarc2koha sub that transforms a non-marc biblio into it's MARC form (or the opposite) The koha2marc & marc2koha exists for biblios & items. HTH -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-11-12 07:58:05 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
It's written at the beginning of Biblio.pm :
Actually, I found it, around line 300 of Biblio.pm -- can the log be moved somewhere else than the start of that file, please? It makes it tricky to keep good patches. -- 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 (3)
-
MJ Ray -
paul POULAIN -
Rachel Hamilton-Williams