Skip to content

Latest commit

 

History

History
65 lines (44 loc) · 1.99 KB

README.md

File metadata and controls

65 lines (44 loc) · 1.99 KB

ezmasterized virtuoso (Triple store)

Make an ezMaster version of OpenLink Virtuoso (inspired from tenforce's version).

Load data

To load triples files (N-Triples, .nt), use the conductor interface.

Don't forget to create graph explicitly.

Warning: don't use the previous loading method, using ezmaster's WebDAV: the location of the files to load would be different, and, at the moment, this method does not work any more.

Named graphs

To get the named graph into which you want to upload the data, use the naming convention: all pointed parts . (except extension) will be taken as the domain, and underline character(s) _ will be converted into slash characters /.

Example:

ns.nature.com_graphs_articles.nq will be http://ns.nature.com/graphs/articles

Configuration

If you want to change an environment variable within the container, add (or modify) a env section within the ezMaster instance's configuration, and a key value pair.

Ex:

{
  "env": {
    "DBA_PASSWORD": "secret"
  }
}

That will add the DBA_PASSWORD environment variable in virtuoso environment before running it.

Available variables

  • DBA_PASSWORD: the password for the administrator
  • SPARQL_UPDATE: true if you want to update the data via SPARQL

.ini configuration

All properties defined in virtuoso.ini can be configured via the JSON configuration variables. They must follow the section / key / value structure, and are case sensitivE. They should be CamelCased as in virtuoso.ini.

E.g. property ErrorLogFile in the Database section should be configured as following:

{
  "Database": {
    "ErrorLogFile": "error.log"
  }
}