Opasnet Base

From Opasnet
Jump to: navigation, search

This page is about the Opasnet Base database. The previous version is described on page Opasnet Base (2008-2011).


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


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

Uploads, updates, and other actions
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
obj_id int(10) unsigned NO
series_id int(10) unsigned NO
unit varchar(64) YES
type ENUM('replace','append') NO
who varchar(255) NO
when timestamp NO
comments varchar(255) YES
lang char(3) NO ISO 639-2, default:'eng'

--1 : I guess this should have field obj_id to identify which object we are updating. In the previous version, act - obj was many-to-many relationship, but it can as well be many-to-one which makes life easier; it is not important to know that two variables were uploaded in the same model run. Also series_id and unit could be in this table. --Jouni 22:56, 22 February 2012 (EET) 2 : I have now altered the table structure to implement Jouni's idea. --Einari 12:31, 19 March 2012 (EET)

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
subset varchar(255) NO UNI(with ident)
type ENUM('variable','study','method','assessment','class','nugget','encyclopedia') NO
page int(10) unsigned NO
wiki_id tinyint(3) unsigned NO
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
series_id int(10) unsigned NO UNI(with ident)
ident varchar(64) NO UNI(with series_id)
type ENUM('entity','number','time') NO
name varchar(255) NO
unit varchar(64) YES
page int(10) unsigned NO
wiki_id tinyint(3) unsigned NO
order_index int(10) unsigned NO
hidden boolean NO false
Wiki information
Field Type Null Extra Key
id tinyint(3) NO PRI
url varchar(255) NO
wname varchar(255) NO


Tables to store all locations and results


Column names:
sid(series.id), aid (act.id), <inds.ident>, <inds.ident>, ..., <inds.ident>, res (result)

<acts.series_id>, <acts.id>, <locs.id | data>, <locs.id | data>, ..., <locs.id | data>,

db.<objs.ident>(.<objs.subset>).dat.ensureIndex({_sid:1, _aid:1});

--# : I guess this is about loc.id's, not about ind.id's. Loc.id's are either identifiers explained below or values of continuous indices. --Jouni 22:56, 22 February 2012 (EET)
# : It was actually about ind.id, but the line described column names, not the data itself. To avoid future misleads I added data describing line as well. Object data can consist of location identifiers or e.g. real numbers, depending of the type of the column index. --Einari 13:33, 19 March 2012 (EET)

Tables to store real location values for entity type indices


Column names:
iid (index id), lid (location id), val

ensureIndex(array("iid" => 1, "lid" => 1));

# : If the index is entity type, inds.id is the identifier of the index (whose details are in MySQL) and value is the name of the location. If the index is continuous, it does not need rows in this table, as everything necessary is described in the tables inds and db.<object.ident>.dat. --Jouni 22:56, 22 February 2012 (EET)

--# : What is key? --Jouni 22:56, 22 February 2012 (EET)
# : Key was something that I cannot really confirm. I altered the table description so that index id and location id together make the key (indexed in that order). This means that location values must always be accessed through index id. I believe that this is the fastest way in practice. --Einari 14:35, 19 March 2012 (EET)

--Toinen asia OB2:een liittyen: Indekseille pitäisi pystyä antamaan yksiköt, koska ne eivät ole itsestäänselviä (Erkki huomasi tämän). Onko tämän toteutus suunniteltu? Seka kannassa pitää olla paikka, ja lisäksi esim. t2b:ssa olisi syytä olla parametri yksiköiden antamista varten (tai pitäisikö nykyistä unit-parametrin käyttöä laajentaa?).: --Jouni 16:25, 1 January 2013 (EET) {{{3}}}

JSON interface

The interface is based on a PHP script that outputs JSON, so data can be transferred using ordinary HTTP requests. One could even read through most of the meta-data in a web browser with a plugin that displays json better:


See also

Other databases with (ot without) R connectivity

Pages related to Opasnet Base

Opasnet Base · Uploading to Opasnet Base · Data structures in Opasnet · Opasnet Base UI · Modelling in Opasnet · Special:Opasnet Base Import · Opasnet Base Connection for R (needs updating) · Converting KOPRA data into Opasnet Base · Poll

Pages related to the 2008-2011 version of Opasnet Base

Opasnet base connection for Analytica · Opasnet base structure · Related Analytica file (old version File:Transferring to result database.ANA) · Analytica Web Player · Removed pages and other links · Standard run · OpasnetBaseUtils