https://wiki.cebitec.uni-bielefeld.de/brf-software/index.php?action=history&feed=atom&title=MeltDBWiki%2FDeveloperDocumentation%2FDatabaseSetupMeltDBWiki/DeveloperDocumentation/DatabaseSetup - Revision history2026-06-01T14:31:57ZRevision history for this page on the wikiMediaWiki 1.39.7https://wiki.cebitec.uni-bielefeld.de/brf-software/index.php?title=MeltDBWiki/DeveloperDocumentation/DatabaseSetup&diff=1876&oldid=prevAdmin: 1 revision2011-10-26T06:16:35Z<p>1 revision</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 08:16, 26 October 2011</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Adminhttps://wiki.cebitec.uni-bielefeld.de/brf-software/index.php?title=MeltDBWiki/DeveloperDocumentation/DatabaseSetup&diff=1875&oldid=previmported>HeikoNeuweger at 08:14, 25 July 20062006-07-25T08:14:12Z<p></p>
<p><b>New page</b></p><div>__NOTOC__<br />
= MeltDB Database Setup =<br />
<br />
The MeltDB data scheme has been defined using O@DBI and the GPMS. <br />
The persistent storage of the metabolomic datasets is achieved using a<br />
object-relational mapping of Perl Objects to an SQL (MySQL) database.<br />
<br />
Fine grained user roles, rights and permissions have been defined both on the underlying <br />
database tables as well as on the application level. This makes it possible to <br />
have secured acces to experiment and analysis data. The user management can be performed<br />
using the web based access management system.<br />
<br />
== Setting up the database == <br />
<br />
Use the following GPMSDB scripts to set up a MeltDB database.<br />
(Assuming the three files MELTDB.sql, meltdb_rights and meltdb_roles are in the current directory)<br />
These files are found here:<br />
/vol/gpms-intern/var/SQL-Table-definitions/<br />
/vol/gpms-intern/projectmanagement/share/rights_and_roles/MySQL4.x/<br />
<br />
<br />
<pre><nowiki><br />
add_project_class.pl -c MeltDB -d 'MeltDB Metabolomics Projects'<br />
add_datasource_type.pl -y MeltDB -s MELTDB.sql -m 'MELT::DB'<br />
add_project.pl -p 'MeltDB_Test' -c MeltDB -d 'Metabolomics test project (H.Neuweger)' -a 'CeBiTec'<br />
add_db.pl -H dbhost -t MySQL-4.1.8 -y MeltDB -A O2DBI2 -p MeltDB_Test -D MeltDB_Test<br />
add_rights.pl -f meltdb_rights<br />
add_role.pl -f meltdb_roles<br />
add_member.pl -l 'hneuwege' -p 'MeltDB_Test' -r Developer<br />
</nowiki></pre><br />
<br />
<br />
=== Refreshing the Database ===<br />
<br />
The development strategy of MeltDB realizes prototype based exploration.<br />
Changes in the database design will therefore be quite common, the update of the database <br />
files can be achieved in the following way (GPMS user gpmsadmin is required):<br />
<br />
<br />
<pre><nowiki><br />
cd /vol/gpms-intern/projectmanagement/share/exec<br />
export INSTALLDIR=/vol/gpms-intern/projectmanagement/<br />
. build_environment<br />
perl del_datasource.pl -D MeltDB_Test -z<br />
perl add_db.pl -H dbhost -t MySQL-4.1.8 -y MeltDB -A O2DBI2 -p MeltDB_Test -D MeltDB_Test<br />
perl add_member.pl -l 'hneuwege' -p 'MeltDB_Test' -r Developer<br />
</nowiki></pre></div>imported>HeikoNeuweger