Difference between revisions of "RadLex SQL Database"
Johnpaulett (talk | contribs) m |
|||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
NOTE: In order to start someplace, there is an entry "ROOT" in the radterms table that acts as the root term of the ontology. This root term has no meaning outside of this database representation of the ontology. The "ROOT" entry appears in the radlinks table to start the relations tree. | NOTE: In order to start someplace, there is an entry "ROOT" in the radterms table that acts as the root term of the ontology. This root term has no meaning outside of this database representation of the ontology. The "ROOT" entry appears in the radlinks table to start the relations tree. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 18:48, 31 July 2009
The Term Browser uses a MySQL database to provide the data. When a new version of the RadLex ontology is available, the SQL Export plugin (RadLex Protege Plugin) is used to generate a file containing SQL commands to create the database and tables, and populate the tables with the latest terminology. This SQL file is then run on the MySQL database of the Term Browser. The SQL file is provided to all users to import into their own databases, if desired. The SQL file has only been tested on an MySQL database, however, the script should be applicable to any SQL based database with little or no modification.
NOTE: In order to start someplace, there is an entry "ROOT" in the radterms table that acts as the root term of the ontology. This root term has no meaning outside of this database representation of the ontology. The "ROOT" entry appears in the radlinks table to start the relations tree.