GenomeHubs
  • Introduction
  • Introduction
    • GenomeHubs
    • Files and containers
    • Demo
  • Quick Start
    • 1. Prepare
    • 2. Setup MySQL database server
    • (optional) Test Ensembl browser
    • 3. Import assembly and gene models
    • 4. Export files
    • 5. Run analyses
    • 6. Import analysis results
    • 7. Update meta
    • 8. Start download site
    • 9. Start BLAST server
    • 10. Start search container
    • 11. Edit Ensembl plugin
    • 12. Start Ensembl browser
  • Next Steps
    • Setup with multiple hosts
    • Understand the GFF parser
    • Import additional assemblies
    • Run comparative analyses
    • Import variation data
    • Add track hubs
    • Connect using Perl API
    • Set up REST API
Powered by GitBook
On this page

Was this helpful?

  1. Quick Start

7. Update meta

Previous6. Import analysis resultsNext8. Start download site

Last updated 4 years ago

Was this helpful?

Values in the [META] section of each <database name>.ini file are written to the meta table of the corresponding Ensembl database when it is created during the initial step. Often it is convenient to add to or amend these entries after the initial import, for example to set suggested search terms after importing blastp or InterProScan results, but note that values such as production name, species url and assembly name cannot be changed in this way after the initial import.

If a single value is present in the database for a given key, it will be replaced. If multiple values are present, an additional value will be added.

Add/replace metadata values

Add suggested search terms:

$ nano ~/genomehubs/v1/import/conf/operophtera_brumata_obru1_core_40_93_1.ini
$ nano ~/genomehubs/v1/import/conf/operophtera_brumata_obru1_core_36_89_1.ini
$ nano ~/genomehubs/v1/import/conf/operophtera_brumata_obru1_core_32_85_1.ini
# existing entries not shown
[META]
        SAMPLE.LOCATION_PARAM    = OBRU01_Sc00001:57580-69243
        SAMPLE.LOCATION_TEXT     = OBRU01_Sc00001:57580-69243
        SAMPLE.GENE_PARAM        = OBRU01_00004
        SAMPLE.GENE_TEXT         = OBRU01_00004
        SAMPLE.TRANSCRIPT_PARAM  = OBRU01_00004-RA
        SAMPLE.TRANSCRIPT_TEXT   = OBRU01_00004-RA
        SAMPLE.SEARCH_TEXT       = OBRU01_00015-RA

Run an EasyImport Docker container with -u flag to update metadata:

$ docker run --rm \
             -u $UID:$GROUPS \
             --name easy-import-operophtera_brumata_v1_core_40_93_1 \
             --network genomehubs-network \
             -v ~/genomehubs/v1/import/conf:/import/conf \
             -v ~/genomehubs/v1/import/data:/import/data \
             -e DATABASE=operophtera_brumata_obru1_core_40_93_1 \
             -e FLAGS="-u" \
             genomehubs/easy-import:19.05
$ docker run --rm \
             -u $UID:$GROUPS \
             --name easy-import-operophtera_brumata_v1_core_36_89_1 \
             --link genomehubs-mysql \
             -v ~/genomehubs/v1/import/conf:/import/conf \
             -v ~/genomehubs/v1/import/data:/import/data \
             -e DATABASE=operophtera_brumata_obru1_core_36_89_1 \
             -e FLAGS="-u" \
             genomehubs/easy-import:17.06
$ docker run --rm \
             -u $UID:$GROUPS \
             --name easy-import-operophtera_brumata_v1_core_32_85_1 \
             --link genomehubs-mysql \
             -v ~/genomehubs/v1/import/conf:/import/conf \
             -v ~/genomehubs/v1/import/data:/import/data \
             -e DATABASE=operophtera_brumata_obru1_core_32_85_1 \
             -e FLAGS="-u" \
             genomehubs/easy-import:17.03
assembly import