...
There is a list of Frequently Asked Questions (FAQs) addressing specific issues related to installation
Appendix A: Behind the Scenes Configuration and Management
Configuring the Administration DB for a new project
The following steps can be skipped if the new project is created through the VocBench interface.
VocBench stores all the ontologies information in the “Administrator database” under “ontology_info” table. The structure of this table contains various fields. Please ignore the fields: (db_url, db_driver, db_name_ db_password) as the RDF data is no more stored in a database. These fields have been maintained for compatibility with the previous 1.3 version of VB (thus enabling use of the same admin DB with two different versions of VB).
ontology_id: (Auto increment)
ontology_name: <ontology-name> (use {ST.PROJECT.NAME})
ontology_description: <description-of-ontology> (not important)
db_url: null
db_driver: <ST-Server URL> (e.g. http://127.0.0.1:1979/semantic_turkey/resources/stserver/STServer)
db_name: (use {ST.PROJECT.NAME})
db_username: null
db_password: null
ontology_show: 0 for hide and 1 for show (use 1)
version: <version-number> (this should be 2.0 for VB2.0 data)
You may check through some explorer tool if the data is already configured in the Administrator Database that you have downloaded. However, these instructions allow you to define a new entry, should you have the system already installed, but in need of setting up a new project/configuration.
Here follows an example for immediately adding an entry to the admin db for a new project.
To connect to different ST server instances, set the value of <db_driver> with different ST server URL.
debian: mysql –u root –p
mysql> Show databases
mysql> Use < administrator database>
mysql> SELECT * FROM ontology_info
'1', 'AGROVOC_SKOS_VB_2013-02-05', 'Full Agrovoc', '', 'http://127.0.0.1:1979/semantic_turkey/resources/stserver/STServer', 'AGROVOC_SKOS_VB_2013-02-05', '', '', '1', '2.0'
'2', 'AGROVOC-PRODUCTS-AGRONTOLOGY', 'Agrovoc small cut with top concept Products', '', '', '', '', '', '0', '2.0'
You will see that ontology with project name 'AGROVOC_SKOS_VB_2013-02-05’ is already configured for VB 2.0. If you want to add new ontology, follow query below.
mysql> INSERT INTO ontology_info
(ontology_name, ontology_description, db_url, db_driver, db_name, db_username, db_password, ontology_show,version) values
(“{ST.PROJECT.NAME}”, "AGROVOC Multilingual Thesaurus", null, “http://127.0.0.1:1979/semantic_turkey/resources/stserver/STServer”, “{ST.PROJECT.NAME}”, null,
null, "1","2.0");
Managing a project through Semantic Turkey services
The following actions (Import ontology, Namespace management) can be skipped as can done via VocBench interface.
- Then from a web browser paste the following URLs and wait for their relative responses:
- This action may take a while, as Semantic Turkey is importing the definition of OWL, SKOS and SKOS-XL dictionaries. This is done only the first time the project is being created. You should see an XML reply on the browser (and in the STServer console if proper logging is activated) once the request is satisfied.
- The first time that you run Semantic Turkey on a given project, you have to import the ontology: agrontology.owl (you need an internet connection!), containing all the domain properties used in AGROVOC and other FAO concept schemes. This is the service call:
- This action takes a while, as Semantic Turkey will download the agrontology and, recursively, other ontologies imported by it, such as VOAF and Dublin core. You can check news on the console, if proper logging is activated.
- Check if the import is successful by running query below:
- Add namespace prefix for imported agrontology vocabulary.
- Check added namespace mapping in the list by running query below.