Loading Core Terminologies - Versionsgeschichte

Krebs am 20. Juli 2015 um 13:00 Uhr

2015-07-20T13:00:28Z

Billig am 1. Juli 2015 um 13:30 Uhr

2015-07-01T13:30:22Z

Krebs am 30. Juni 2015 um 08:47 Uhr

2015-06-30T08:47:03Z

Krebs am 30. Juni 2015 um 08:34 Uhr

2015-06-30T08:34:57Z

Krebs am 30. Juni 2015 um 07:49 Uhr

2015-06-30T07:49:10Z

Krebs am 30. Juni 2015 um 07:46 Uhr

2015-06-30T07:46:23Z

Krebs am 30. Juni 2015 um 07:32 Uhr

2015-06-30T07:32:38Z

Krebs: Die Seite wurde neu angelegt: „The process of loading core terminologies comprises 2 steps: # specifiy the terminologies to load by editing a configuration file and # initiate the loading…“

2015-06-30T07:31:55Z

Die Seite wurde neu angelegt: „The process of loading core terminologies comprises 2 steps: # specifiy the terminologies to load by editing a configuration file and # initiate the loading…“

Neue Seite

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

== Edit cts2_conf.xml ==
Loading Core Terminologies is done by editing the file '''cts2_conf.xml''', which is located in the directory that was specified as CTS2LE_RESOURCE_ROOT during the [[CTS2-LE Installation and Deployment|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:
<syntaxhighlight lang="xml">
<vocabulary load="false" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/>
</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.
To load a vocabulary, the attribute '''load''' has to be set to '''true'''.

== 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 [[Loading Terminologies into CTS2-LE]].

@@ Zeile 3: / Zeile 3: @@
 # 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

← Nächstältere Version		Version vom 1. Juli 2015, 13:30 Uhr
Zeile 29:		Zeile 29:

	== See Also ==		== See Also ==
−	To get a deeper understanding of how a terminology is represented by means of CTS2, please visit [[~~Loading~~ Terminologies ~~into~~ CTS2-LE]].	+	To get a deeper understanding of how a terminology is represented by means of CTS2, please visit [[Mapping Terminologies to CTS2-LE]].

@@ Zeile 3: / Zeile 3: @@
 # 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 [[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.
 The XML-structured file lists the available terminologies under the element ''vocabularies''.

@@ Zeile 1: / Zeile 1: @@
 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
+# initiate the loading by executing a script.
 == Edit cts2_conf.xml ==
@@ Zeile 21: / Zeile 24: @@
 == Running the loading script==
 Navigate to the bin-directory located in CTS2LE_RESOURCE_ROOT and execute the script '''WebCts2LEStarter.sh''' by running
   ./WebCts2LEStarter.sh

@@ Zeile 9: / Zeile 9: @@
 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">
 <vocabulary load="false" friendly-name="Unified Code for Units of Measure" resourceID="ucum"/>
 </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">
 == 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
 == See Also ==
 To get a deeper understanding of how a terminology is represented by means of CTS2, please visit [[Loading Terminologies into CTS2-LE]].