...

• Now the repository is ready for receiving data, which will be analysed and expanded into new triples through inference, by exploiting the new ruleset.

FAQs

1.    If the email configuration for a new user does not work, how to set it up through the DB?

If you did not receive the email to activate the new account you need to modify the admin DB. The complexity of this operation depends on the information you have provided during the creation of the account.

...

2.    When I try to log in I get "No ontology was found for the user".

We get this alert when

• The logged in user doesn't have access to any of the ontology. Ask for administrator to allow permission for that ontology.

• If Administrator user gets this alert, then we will need to add at least one of the ontology accessible to administrator user by running following query in Administrator database.

INSERT INTO users_ontology (`user_id`, `ontology_id`, `status`) VALUES (1, 1, 1);

• If administrator already has access to that ontology, check if that ontology exists in ontology_info table.

SELECT * FROM ontology_info WHERE ontology_id=1

• VocBench can filter ontology by enabling/disabling it for each version of VocBench. For this, we have 'version' field in the onotology_info table. The version of VocBench is set in Config.properties file with parameter name "VERSION". Use the query below to check if the ontology exists for selected version

SELECT * FROM ontology_info WHERE ontology_id=1 and version=2.0

• If no ontology exist add ontology using query below

INSERT INTO ontology_info (ontology_name, ontology_description, db_url, db_driver, db_name, db_username, db_password, ontology_show,version) values ("remoteCompleteAgrovoc", "AGROVOC Multilingual Thesaurus", null,null, null, null,  null, "1","2.0");

Where,

ontology_name = project name of the ontology created in ST server. (This is how VocBench recognizes which project in ST to connect)

ontology_description = description of the ontology

db_url = Ignore for VB 2.0

db_driver = ST server URL

(e.g. . http://127.0.0.1:1979/semantic_turkey/resources/stserver/STServer))

db_name = project name of the ontology created in ST server.  

db_username = Ignore for VB 2.0

db_password = Ignore for VB 2.0

ontology_show = 1 to activate, 0 to disable

version = Version of VB set on Config.properties file

3.    I made a mistake in configuring an OWLIM repository. Since I want to reuse the same ID, I want to delete it and then recreate it with the same ID. But when I do it, the Sesame workbench returns an exception.

• Here is an answer to this question, from the OWLIM mailing list.    

The issue is related to the way repository description is created, managed and deleted through Sesame framework. When repository is created, only its actual configuration/description/ is stored within the SYSTEM repository - it is not immediately instantiated - so the configuration is not immediately verified. When you try to delete it through the workbench app - the server tries to instantiate it first but when that fails due to some misconfiguration you end up with such exception. If there are no other repositories you could simply delete the SYSTEM repository and restart the openrdf-sesame app. But if that is unfeasible for some reason then you could try to remove it's description from the SYSTEM repository using a sparql updates executed directly against it.

...