H3Africa initiative to provide a centralized repository for microbiome metadata associated with African populations.
The African microbiome portal (AMP) is in development under H3Africa initiative to provide a centralized repository for microbiome metadata associated with African populations, with following aims:
- To provide the most rapid and comprehensive overview of all existing African microbiome metadata. The metadata includes sequencing details along with repository link hosting that data and sample details including participant participant demographic details sequences repository links.
- To continuous inclusion of new newly available data, provided by authors, and acquired by publication reviewing and other database mining.
- To establish a free, open and centralised access to harmonized publicly available African microbiome-related metadata that are interactively displayed. The metadata files will also easily downloadable as flat files from the database itself or the github repository.
- To enables submission of newly published metadata after assessing and reviewing the submitted files following the instructions in the metadata submission guidelines section. This will allow researchers with common scientific objectives to contribute to the scientific community by submitting and sharing their new metadata.
This project is created with :
- Python 3.7
- Django 2.2.7
- Liflet
- Jquery 3.3.1
- Chartjs
- Bootstrap4 4.3.1
- sqllite3
Note: Technology and their version might change in final version of the database.
The current code has only tested in Linux enviroment.
- conda env create -f database-spec.yml
- To activate: source activate database
- To deactivate: source deactivate
After activating the environment using command source activate database
- python manage.py runserver
- Launch browser and visit link
If you make any change in the conda environment by adding or removing modules.
conda env export --no-builds > environment2.yml
conda env export -n test-env -f test-env-spec.yml
- To containerise of Django application, instruction from Docker was followed.
- Instruction to run the container was followed from Docker Tip #30: Running Docker Compose from a Different Directory