Paul's XSLT was using 001 for the id. El sáb, nov 15, 2014 05:39 AM, Frédéric Demians <frederic@tamil.fr> escribió:
Paul, could you confirm that you use Zebra in DOM mode? It seems Zebra isn't configured properly, and so doesn't know where to pick up unique ID for biblio records (biblionumber field). Without an ID to identify biblio records, Zebra can't neither delete nor update a biblio record.
Check your Zebra index definition file: biblio-koha-indexdefs.xml.
At the beginning of the file, you should have a line like this one:
<id>marc:datafield[@tag='999']/marc:subfield[@code='c']</id>
My assumption is that you haven't this. This could happen if the upgrade isn't done properly, for a reason or another.
I have a feeling that when zebra says "incremental" it means just that -- adding new data, but not deleting what has gone from MySQL.
It works for the vast majority of the Koha crowd. Zebra is obviously designed to be able to add/edit/delete records. It's a minimum :-) You have to figure out what's wrong with your installation.
Kind regards, -- _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha