 |
Page History
...
This LexEVS loader command loads input in OWL format. Substituting the matching LexEVS loader command for the format being used and pointing the loader to a local source file will load most terminologies. In the LexEVS administrative GUI, loading is accomplished using the "Load Terminology" menu. The administrative options must be enabled first in the Command menu.
Best Practices
As you work with terminologies in LexEVS there are some things that you will find are the best way to approach things to make life easy as far as loading goes.
...
Setting a terminology as active:
...
The need to take terminologies offline without unloading them is served by activation. After you load a terminology you must make it active if you want any queries to work against it. The LexEVS Administrative GUI has a button to set the activation state. All the LexEVS loader commands also have a flag that can set a terminology to active upon successful load.
...
Setting at terminology as the production terminology:
...
Even if you do not use the abilities, LexEVS can load multiple copies of terminologies. You may want different versions of the same thing for testing let's say. When this happens, LexEVS needs to know which terminology to treat as the default for a query that only specifies a terminology name. It is best if you always tell LexEVS if a terminology is the default, even if you only have one. Some queries, like queries to terminology metadata, do not work without setting a terminology as the production copy. You do this by tagging a terminology. The LexEVS Administrative GUI has a button to change the tag of any loaded terminology. The LexEVS loader commands have a flag that can be used to set the tag.
The tag is a simple string. You can assign any tag you want, but the string recognized by LexEVS is "PRODUCTION" (all cps, no quotes). You should get in the habit of marking loaded terminologies as PRODUCTION. The opposite of that might be "TEST" or just left blank.
...
Restarting distributed services after loading:
...
After loading terminologies in a LexEVS Distributed environment you will not see any results of doing so until you restart the web container. This is a limitation of the LexEVS Distributed service. Get used to restarting the application server after loading any number of terminologies. You do not have to restart after each one.
Large Terminologies
Loading any larger terminologies can be very time consuming and resource intensive and this can be helped by the following recommendations for database optimization. The primary LexEVS configuration file, <LEXEVS_HOME>/resources/config/lbconfig.props, should be changed depending on how the primary key for the database should be generated. The default setting for the value of the database primary key is the following:
...
