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

[Jared Camins-Esakov]

Frédéric,

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.


We should absolutely NOT recreate the DOM configuration from record.abs.
That was a one-time transformation, and must not be repeated, or bug 8665
is liable to recur, as well as various other regressions. As for why we use
biblio-koha-indexdefs.xml to generate biblio-zebra-indexdefs.xsl, I admit I
don't actually know. Galen?

Regards,
Jared

-- 
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcamins at cpbibliography.com
(web) http://www.cpbibliography.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20121221/d714d102/attachment.html>