|
<action> |
|
<field name="id"> |
|
<String>reftest</String> |
|
</field> |
|
<field name="name"> |
|
<String>ref</String> |
|
</field> |
|
<field name="description"> |
|
<String></String> |
|
</field> |
|
<field name="largeIconPath"> |
|
<String></String> |
|
</field> |
|
<field name="smallIconPath"> |
|
<String></String> |
|
</field> |
|
<field name="accessKey"> |
|
<String></String> |
|
</field> |
|
<field name="accelerator"> |
|
<null/> |
|
</field> |
|
<field name="actionModes"> |
|
<actionMode-array> |
|
<actionMode> |
|
<field name="xpathCondition"> |
|
<String></String> |
|
</field> |
|
<field name="argValues"> |
|
<serializableOrderedMap> |
|
<entry> |
|
<String>URL</String> |
|
<String>${RI_DATACOPY_VIA_REST}/indexOfRegests.xml</String> |
|
</entry> |
|
<entry> |
|
<String>element</String> |
|
<String>"<ref xmlns='http://www.tei-c.org/ns/1.0' target='" + @id + "' />"</String> |
|
</entry> |
|
<entry> |
|
<String>expression</String> |
|
<String>//span</String> |
|
</entry> |
|
<entry> |
|
<String>node</String> |
|
<String>//li</String> |
|
</entry> |
|
</serializableOrderedMap> |
|
</field> |
|
<field name="operationID"> |
|
<String>org.bbaw.telota.ediarum.InsertRegisterOperation</String> |
|
</field> |
|
</actionMode> |
|
</actionMode-array> |
|
</field> |
|
<field name="enabledInReadOnlyContext"> |
|
<Boolean>false</Boolean> |
|
</field> |
|
</action> |
This action requires an up-to-date index of regests, but so far no mechanism for updating the index exists.
Proposed solution: create an eXist database trigger to transform the regests into an index file and store it in the database.
Requirement: this needs to work separatley within sections (“Abteilungen”) of the project, so that cross-references are made within the section, but not across sections. (Or at least, this should be a conscious choice, i.e. a separate function.)
ediarum.RI.edit/regesta_imperii_regesten.framework
Lines 2147 to 2204 in f1589af
This action requires an up-to-date index of regests, but so far no mechanism for updating the index exists.
Proposed solution: create an eXist database trigger to transform the regests into an index file and store it in the database.
Requirement: this needs to work separatley within sections (“Abteilungen”) of the project, so that cross-references are made within the section, but not across sections. (Or at least, this should be a conscious choice, i.e. a separate function.)