Metaphrase SQL-Queryable Database Tables

This page describes those tables stored in the Metaphrase database that are meant to be queryable using SQL. These tables include submit, a table that stores any new terms submitted by Metaphrase users who could not find their term in the existing Metaphrase database (see Metaphrase.submitTerm()), and edit_log and edit_log_return, which store a representation of all changes made to a Metaphrase database using the GoodEnoughUpdate interface.

Submitted-terms table

The submit table stores terms submitted using the Metaphrase.submitTerm() method. The fields in this table and their corresponding Oracle SQL data types include:

tempcui CHAR(8) - the temporary conceptID (aka Concept Unique Identifier or CUI) assigned by Metaphrase to this term
name VARCHAR2(800) - the submitted term itself
source VARCHAR2(10) - the SAB() of the Source "source" which the user passed to the submitTerm() call
nearest CHAR(8) - the conceptID of the Concept "nearestConcept" which the user passed to the submitTerm() call
note VARCHAR2(900) - the "note" text passed to the submitTerm() call
related VARCHAR2(255) - a string consisting of the |-separated conceptID's of the Concept[] "relatedConcepts[]" which the user passed to the submitTerm() call
attrs LONG RAW - the Java serialization of the java.util.Dictionary "attributes" which the user passed to the submitTerm() call

Edit_log table

The edit_log table stores a representation of all the changes made to a Metaphrase database since its creation. The fields in this table and their corresponding Oracle SQL data types include:

seq NUMBER - a sequence number uniquely identifying this entry in the edit_log table. This can be used to join to the seq column of the edit_log_return table to find the corresponding rows of that table

tstamp DATE - the date/time when this edit was performed

userid VARCHAR2(16) - the username of the Metaphrase user who performed this edit

fun VARCHAR2(10) - the "editing function" represented by this edit. This is typically a code name such as "EV1" or "EV12" - see the Editing API Spec for documentation of the editing function codes
args VARCHAR2(2000) - a representation of the arguments to the editing function

Edit_log_return table

The edit_log_return table stores a representation of the information returned from Metaphrase in response to an "EV4" edit. The fields in this table and their corresponding Oracle SQL data types include:

seq NUMBER - a sequence number from the edit_log table. This row represents (a segment of) the return from the edit described in the row of edit_log that has this seq value
segment NUMBER - a sequential number specifying which segment of the return this row represents. If the return from the editing function contains more than 2000 characters, it is stored in multiple rows of this table, all with the same seq value, and with sequential segment values, starting from 0
return VARCHAR2(2000) - the specified segment of the return from the specified edit

If you cannot find the answer to your API question, or have a comment or suggestion, please send email to metaphrase-support@lexical.com.