[Koha-devel] DOM Indexing--why several config files from which generating indexes XSL?

[Frédéric Demians]

Zebra DOM model indexing had been introduced into Koha, deprecating
GRS-1 model.

With GRS-1, we used to have a records.abs file defining Koha indexes.

With DOM model, an XSL file transforms MARCXML biblio records into Zebra
indexes. This file is named biblio-zebra-indexdefs.xsl, and is stored in
marc_defs/[marc21|unimarc]/biblios directory.

But it seems that this file is not supposed to be modified directly.

Going to DOM model, records.abs had been transformed into a
biblio-koha-indexdefs.xml. This transformation is done with a XSL
koha-indexdefs-to-zebra.xsl. Then biblio-koha-indexdefs.xml is
transformed into biblio-zebra-indexdefs.xsl with
biblio-koha-indexdefs.xml

We have this chain of transformations:

  records.abs
    >>> XSLT koha-indexdefs-to-zebra.xsl
  biblio-koha-indexdefs.xml
    >>> XSLT biblio-koha-indexdefs.xml
  biblio-zebra-indexdefs.xsl

The question is, using Zebra in DOM mode, why should we continue to
modify records.abs file, and then cascading generating following files?
Or even, why should we modify biblio-koha-indexdefs.xml, and then create
from it biblio-zebra-indexdefs.xsl? Why not modifying from now directly
biblio-zebra-indexdefs.xsl.


-- 
Frédéric DEMIANS
http://www.tamil.fr/u/fdemians.html