Loading Core Terminologies: Unterschied zwischen den Versionen
Krebs (Diskussion | Beiträge) K |
Krebs (Diskussion | Beiträge) K |
||
| (5 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
The process of loading core terminologies comprises 2 steps: | The process of loading core terminologies comprises 2 steps: | ||
# specifiy the terminologies to load by editing a configuration file and | # specifiy the terminologies to load by editing a configuration file and | ||
| − | # initiate the loading by executing a script | + | # initiate the loading by executing a script. |
| + | When loading vocabularies through the hereinafter described strategy, it should be considered that | ||
| + | # the server instance will be shut down for the period of loading and | ||
| + | # any already loaded vocabulary will be deleted | ||
== Edit cts2_conf.xml == | == Edit cts2_conf.xml == | ||
| − | The file '''cts2_conf.xml''' is located in the directory that was specified as CTS2LE_RESOURCE_ROOT during the [[CTS2-LE Installation and Deployment|installation process]]. | + | The file '''cts2_conf.xml''' is located in the directory that was specified as CTS2LE_RESOURCE_ROOT during the [[CTS2-LE Installation and Deployment#Setting_the_resource_root|installation process]]. |
When receiving a CTS2-LE distribution, this file will comprise a reference to any terminology for which the user has obtained a license. | When receiving a CTS2-LE distribution, this file will comprise a reference to any terminology for which the user has obtained a license. | ||
The XML-structured file lists the available terminologies under the element ''vocabularies''. | The XML-structured file lists the available terminologies under the element ''vocabularies''. | ||
A specific vocabulary is defined by a ''friendly-name'' and a ''resourceID'', for example the UCUM code system will appear as the following line: | A specific vocabulary is defined by a ''friendly-name'' and a ''resourceID'', for example the UCUM code system will appear as the following line: | ||
<syntaxhighlight lang="xml"> | <syntaxhighlight lang="xml"> | ||
| + | <!-- not enabled for loading --> | ||
<vocabulary load="false" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/> | <vocabulary load="false" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | The friendly name is a human readable name for a terminology and may be modified by the user if he prefers a different designation. However, the attribute '''resourceID''' must not be changed as it is a system intern identifier for the terminology. | + | The friendly name is a human readable name for a terminology and may be modified by the user if he prefers a different designation. However, the attribute '''resourceID''' must not be changed as it is a system intern identifier for the terminology. To load a vocabulary, the attribute '''load''' has to be set to '''true'''. |
| − | To load a vocabulary, the attribute '''load''' has to be set to '''true'''. | + | <syntaxhighlight lang="xml"> |
| + | <!-- enabled for loading --> | ||
| + | <vocabulary load="true" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/> | ||
| + | </syntaxhighlight> | ||
| + | There are no restrictions concerning the amount of terminologies that can be loaded in one run, thus a user might enable any available resource before saving the file. | ||
== Running the loading script== | == Running the loading script== | ||
| − | Navigate to the bin-directory located in CTS2LE_RESOURCE_ROOT and execute the script WebCts2LEStarter.sh by running | + | Navigate to the bin-directory located in CTS2LE_RESOURCE_ROOT and execute the script '''WebCts2LEStarter.sh''' by running |
./WebCts2LEStarter.sh | ./WebCts2LEStarter.sh | ||
== See Also == | == See Also == | ||
| − | To get a deeper understanding of how a terminology is represented by means of CTS2, please visit [[ | + | To get a deeper understanding of how a terminology is represented by means of CTS2, please visit [[Mapping Terminologies to CTS2-LE]]. |
Aktuelle Version vom 20. Juli 2015, 15:00 Uhr
The process of loading core terminologies comprises 2 steps:
- specifiy the terminologies to load by editing a configuration file and
- initiate the loading by executing a script.
When loading vocabularies through the hereinafter described strategy, it should be considered that
- the server instance will be shut down for the period of loading and
- any already loaded vocabulary will be deleted
Edit cts2_conf.xml
The file cts2_conf.xml is located in the directory that was specified as CTS2LE_RESOURCE_ROOT during the installation process. When receiving a CTS2-LE distribution, this file will comprise a reference to any terminology for which the user has obtained a license. The XML-structured file lists the available terminologies under the element vocabularies. A specific vocabulary is defined by a friendly-name and a resourceID, for example the UCUM code system will appear as the following line:
<!-- not enabled for loading -->
<vocabulary load="false" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/>
The friendly name is a human readable name for a terminology and may be modified by the user if he prefers a different designation. However, the attribute resourceID must not be changed as it is a system intern identifier for the terminology. To load a vocabulary, the attribute load has to be set to true.
<!-- enabled for loading -->
<vocabulary load="true" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/>
There are no restrictions concerning the amount of terminologies that can be loaded in one run, thus a user might enable any available resource before saving the file.
Running the loading script
Navigate to the bin-directory located in CTS2LE_RESOURCE_ROOT and execute the script WebCts2LEStarter.sh by running
./WebCts2LEStarter.sh
See Also
To get a deeper understanding of how a terminology is represented by means of CTS2, please visit Mapping Terminologies to CTS2-LE.
