262 |
<isis type="display" append="1" delimiter=" " format_name="IDths" format_delimiter=";;">5761;;576a</isis> |
<isis type="display" append="1" delimiter=" " format_name="IDths" format_delimiter=";;">5761;;576a</isis> |
263 |
</MicrothesaurusGE> |
</MicrothesaurusGE> |
264 |
--> |
--> |
|
<!-- |
|
|
order is important for type="lookup_key|lookup_val" |
|
|
They create internal hash file for lookups from other |
|
|
fields. Therefore, you mist ensure (in config file) that |
|
|
databases which are source of lookup are called before |
|
|
databases that use lookup fields. |
|
|
Those lookup are then used using special ##lookup## |
|
|
token inside formating instructions like this: |
|
|
<isis type="lookup">999x</isis> |
|
|
--> |
|
265 |
|
|
266 |
<IDths name="ID" order="300"> |
<IDths name="ID" order="300"> |
|
<isis type="lookup_key">900</isis> |
|
267 |
<isis type="swish">900</isis> |
<isis type="swish">900</isis> |
268 |
</IDths> |
</IDths> |
269 |
|
|
|
<SubjectIndex name="Predmetno kazalo" order="301"> |
|
|
<isis type="lookup_val">eval{v901^a eq "Deskriptor"} / [5724] 572a</isis> |
|
|
<isis type="lookup_val">eval{v901^a eq "Deskriptor"} [251]</isis> |
|
|
<!-- |
|
|
<isis type="lookup_val" append="1"> 562a</isis> |
|
|
--> |
|
|
</SubjectIndex> |
|
270 |
|
|
271 |
</indexer> |
</indexer> |
272 |
</config> |
</config> |