adding in-progress code for annotations module
Merge branch 'METS-crxq' of github.com:vronk/SADE into METS-crxq
updating @type on index elements and adding configuration elements for lucene fulltext indexes in project template
minor changes in config.xqm:

- run-time injection of project-specific paths did not work as expected because of range index lookup behaviour (when operating on mixed stored and in-memory nodes, the range index only returns the stored nodes): workaround for the time being, by expanding all components first
- making parameter to project:exists() optional
- simplifying lookup XPath for path in config:path()
adding mappings config feature: ignore and inline elements in the lucene configuration section of the mappings (ft element) can now have a '@index' attribute that restricts its scope to the index referenced

<ft>
    <ignore index="cql.serverChoice">tei:note</ignore>
    <ignore>tei:lb</ignore>
</ft>

means: ignore tei:lb in all full text indexes and ignore tei:notes in the cql.serverChoice

this will be transformed into an xconf containing

<lucene>
    ...
    <text qname="{match of cql.serverChoice}">
        <ignore qname="tei:note">
    </text>
   <ignore qname="tei:lb"/>
</lucene>
minor fixes to core/index.xqm
adding default declarations of system namespaces to generate-index-functions.xqm (METS, FCS, cr)
replacing 'persistent link' option with 'cite':

- adding dataview 'cite' to fcs.xqm and project.xqm
- adding functions resourcefragment:cite() and resource:cite()
- updating HTML templates, JS and CSS
added code and XSL stylesheet to preprocess KWIC output
adding german collation in fcs:term-from-nodes()
adding query/index.xqm and query-index-tests.xql
adding some debug logging to facs.xqm
minor changes to resourcefragment.xqm

- adding check for content for each fragment individually (to be tested!)
- resolving label and resourcefragment-path via index:apply-index()
bugfix in toc.xqm:

toc mets:fptrs representing resourcefragments got lost, when preceding or following a mets:div because the generated stylesheet decided outputting either nested divs or fptrs: a structure like

<TEI>
   <pb/>
   ...
   <div type="toBePutIntoToc">...</div>
   ...
   <pb/>
</TEI>

would have only resulted in

<mets:div TPY="resource">
    <mets:div TYPE="toBePutIntoToc">
        <mets:fptr/>
    </mets:div>
</mets:div>

... thus loosing the representation of the preceding and following resourcefragments/pages.
The stylesheet's behaviour is changed now to:

<mets:div TYPE="resource">
    <mets:fptr>
        <mets:area/>
    <mets:fptr>
    <mets:div TYPE="toBePutIntoToc">
        <mets:fptr/>
    </mets:div>
    <mets:fptr>
        <mets:area/>
    <mets:fptr>
</mets:div>

HOWEVER the resulting structure is not valid against the METS schema: while there might be a fptr BEFORE a div,
fptrs AFTER a div are not allowed. TODO: find a solution, maybe auto-wrap those floating fptrs into divs that are
ignored in the output of fcs.toc - losing fptr information is not an option.
added handling of boolean values in $sanitized-term in query/cql.xqm
fixed module-specific permissions check
just attribute reordering
added classes to form labels, to allow css customization
set 'metadata' as default  to fetch
WATCHME! some extra handling(?) in lookup-generation