[glotpress-updates] [GlotPress] #97: Glossary

[GlotPress]

#97: Glossary
--------------------------+----------------------
  Reporter:  nbachiyski   |      Owner:  yoavf
      Type:  enhancement  |     Status:  assigned
  Priority:  minor        |  Milestone:  1.1
 Component:  general      |    Version:
Resolution:               |   Keywords:
--------------------------+----------------------
Changes (by yoavf):

 * owner:  somebody => yoavf
 * status:  new => assigned


Comment:

 My initial thoughts on this:

 '''Schema and structure'''

 - We'll add two table gp_glossaries and gp_gloassary_items.
 - A glossary will be linked to a translation set, so will inherit a link
 to a project/language
 - A glossary can have a parent glossary, which would be useful when we
 want to create a separate glossary for a sub project, that will also
 include entries from the parent project.
 - A glossary item will include the term, it's morphological type
 (verb/noun), possible examples, comments, and suggestion translation.

 Here are very early schemas for the tables:

 {{{
 CREATE TABLE IF NOT EXISTS `gp_glossaries` (
   `glossary_id` int(10) NOT NULL AUTO_INCREMENT,
   `translation_set_id` int(10) NOT NULL,
   `parent_glossary_id` int(10) DEFAULT NULL,
   PRIMARY KEY (`glossary_id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
 }}}

 {{{
 CREATE TABLE IF NOT EXISTS `gp_glossary_items` (
   `item_id` int(10) NOT NULL AUTO_INCREMENT,
   `glossary_id` int(10) NOT NULL,
   `term` varchar(255) NOT NULL,
   `type` varchar(255) DEFAULT NULL,
   `examples` text,
   `comment` text,
   `suggested_translation` varchar(255) DEFAULT NULL,
   `last_update` datetime DEFAULT NULL,
   PRIMARY KEY (`item_id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
 }}}

 '''UI'''

 Viewing: I'm thinking a floating window/sidebar that will open via an
 always visible link (inside the translation set view). The window will
 list all items in the glossary, with a quick search box.
 Need to figure out how exactly this will look, since the examples and
 comment fields could be quite long.
 There should be a way to quickly search for originals containing the
 original term, and translations containing the suggested translation.

--
Ticket URL: <https://glotpress.trac.wordpress.org/ticket/97#comment:4>
GlotPress <https://glotpress.trac.wordpress.org>
Easy comin', easy goin'