Index via ant vs app:index-compos

[hlapin]

I improved the xslt transform that is run by app:index-compos, but I want to suggest a different procedure.

For the align/compare views the site spends a lot of time indexing the repository to figure out what's there and what to display.

Rather than that, what if each time the repository was updated, and generated a new index file that had:

1. the <witList>s and <witness> elements and their descriptive text from ref.xml header
2. an index of all the available units down to the ab level (could include head/trailer too), AND what witnesses have text for that unit (this is what app:index-compos does on the fly).

We could use Ant and make it part of the update process.

[hlapin]

an index of all the available units down to the ab level (could include head/trailer too), AND what witnesses have text for that unit (this is what app:index-compos does on the fly).

See index-m.xml in mishnah-data/mishnah for preliminary.
Generated by //xsl/indexTEI.xsl