MOLGENIS components

Here you can find summaries and links on the components listed in the ticket system. In the software, these components become packages. For example: org.molgenis.db for shared pacakes or org.col7a1 for application specific packages. We distinguish two groups of components as listed below. Also the use of keywords is explained which we use to clarify relationships from shared packages to application. For example: tickets in the 'auth' component can be marked with keywords 'animaldb' to enable tracking by the animaldb team.

TODO

animaldb auth rwagner biobankexplorer col7a1 compute convertors curation datamodels db documentation gids gwas-workbench impute jamboreecards lifelines lims molgenis newsfeed ngspipeline pheno ui xgap jvelde xqtl

Shared components

these are reusable models (or 'semi-finished module) used across multiple molgenis applications.

component	summary	used
db	molgenis database backend including mysql and jpa	all systems
ui	molgenis user interface framework	all systems
compute	molgenis compute framework including 'cluster' and 'script submission' tools	impute, xqtl, ngs
xgap	high-throughput low variability data model for markers, snps, probes, qtls etc	xqtl-workbench, ngs-lims, gwas-workbench
pheno	low-throughput data model high variability data model for phenotypes	col7a1, animaldb, biobank-warehouse
data	data model, user interface & back-end to browse and search available data in a matrix form	col7a1, animaldb, biobank-warehouse
convertors	convertors that transform external file formats into org.molgenis data models so they can be imported automatically

Application components

These are specific applications (or 'end-product') build for a particular project or user group.

application	description	projects that participate in this component
data-explorer	datawarehouse application to explore all available observation data	lifelines, bbmri, gids, animaldb

Dependencies and other keywords

Obviously there can be a dependency between components. For example, 'animaldb' depends on 'auth'. To make this dependency visible and queryable we use the keywords field. For example: if 'animaldb' and 'col7a1' both have a dependency on a ticket in the auth component this ticket will have keyewords 'animaldb col7a1'.