Opasnet Base

This page is a method. The page identifier is Op_en5474
Moderator:Jouni (see all)
Give your opinion to the peer rating of the content of this page. {{ #opasnet_rater: }} Citation of this page: Juha Villman, Einari Happonen, Jouni T. Tuomisto: Opasnet Base structure. Opasnet 2012. [1]. Accessed 12 May 2024.
Upload data Show results

This page is about the Opasnet Base 2 -database.

Question

How to improve the existing Opasnet Base? Following issues of Opasnet Base 1 must be resolved:

• Opasnet Base 1 structure makes filtering by location very slow on big data
• Opasnet Base 1 structure is perhaps unnecessarily complex = queries are hard to adapt and read
• MySQL is not ideal for storing huge amounts of data, or at least this is how we assume?
• MySQL tables have fixed column types = difficult to store data objects with varying types of indices into one data table
• Multiple languages (localization) not supported

Answer

MySQL is good on relations but weak on dynamic big data. Let's keep the basic "scaffold" in MySQL and store the big data (locations and results) into noSQL-base. After few days of research the best candidate for noSQL-base seems to be MongoDB. Combining relational MySQL and non-relational MongoDB will be the foundation for the new Opasnet Base 2.

Table structure in the database

All tables

acts Uploads, updates, and other actions Field Type Null Extra Key id int(10) unsigned NO auto_increment PRI type ENUM('initial','replace','append') NO who varchar(255) NO when timestamp NO comments varchar(255) YES lang char(3) NO ISO 639-2, default:'eng'		acts_objs Acts of an objects Field Type Null Extra Key act_id int(10) unsigned NO PRI obj_id int(10) unsigned NO PRI series_id int(10) unsigned NO unit varchar(64) YES
objs Object information (all objects) Field Type Null Extra Key id int(10) unsigned NO auto_increment PRI ident varchar(64) NO UNI name varchar(255) NO type ENUM('variable','study','method','assessment','class','nugget','encyclopedia') NO page int(10) unsigned NO wiki_id tinyint(3) unsigned NO	inds Indices Field Type Null Extra Key id int(10) unsigned NO auto_increment PRI act_id int(10) unsigned NO UNI(with ident) ident varchar(64) NO UNI(with act_id) type ENUM('entity','number','time') NO description varchar(255) NO page int(10) unsigned NO wiki_id tinyint(3) unsigned NO order_index int(10) unsigned NO hidden boolean NO false
	wikis Wiki information Field Type Null Extra Key id tinyint(3) NO PRI url varchar(255) NO wname varchar(255) NO

MongoDB

Tables to store all locations and results

db.<obj.ident>.dat

act_id (indexed), <ind.id>, <ind.id>, ..., <ind.id>, res

Tables to store real location values for entity type indices ?

db.<obj.ident>.locs

ind_id(indexed), key, value

See also

• Opasnet structure
• Open assessment