Home ›
CMT database schema, mark IICMT database schema, mark II
Submitted by Benjamin Melançon on July 8, 2007 - 7:20pm
cmt_term_description
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
description : same as in term_data. Don't see a reason to put a key on description
cmt_term_weight
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
weight : same as in term_data
name (inserted into synonym-modeled table cmt_term_name, where votes for names are tracked)
LEFT OUT: vid (for now, cannot vote on what vocabulary a term belongs in)
cmt_term_hierarchy
vapi_id : corresponds to votingapi content_id
tid : same as in term_hierarchy
parent : same as in term_hierarchy
cmt_term_node
vapi_id
nid
tid
cmt_term_name (based on term_synonym table)
vapi_id
tid
name
cmt_term_description
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
description : same as in term_data. Don't see a reason to put a key on description
cmt_term_weight
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
weight : same as in term_data
name (inserted into synonym-modeled table cmt_term_name, where votes for names are tracked)
LEFT OUT: vid (for now, cannot vote on what vocabulary a term belongs in)
cmt_term_hierarchy
vapi_id : corresponds to votingapi content_id
tid : same as in term_hierarchy
parent : same as in term_hierarchy
cmt_term_node
vapi_id
nid
tid
cmt_term_name (based on term_synonym table)
vapi_id
tid
name
Comments
Forgot to list an important one there
Forgot to list an important one. Also, vapi_id is now called content_id so it matches what votingapi itself calls it.
cmt_term_merge
content_id : key for votingapi content_id
tid1 : term, that gets to keep its name and info, to merge onto tid2
tid2 : term, that subsumes its name and info, to merge into tid1
-- I will not be able to resist deriving related terms from this
Post new comment