|GMOD_LOAD_CVTERMS(1p)||User Contributed Perl Documentation||GMOD_LOAD_CVTERMS(1p)|
NAME¶load_cvterms.pl - compares which terms are new in the file compared to the database and inserts them
SYNOPSIS¶Usage: perl load_cvterms.pl -H dbhost -D dbname [-vdntuFo] file
- GMOD database profile name (can provide host, DB name, password, username, and driver) Default: 'default'
- database name for linking (must be in db table, e.g. GO )
- controlled vocabulary name (e.g 'biological_process'). optional. If not given, terms of all namespaces related with database name will be handled.
- File format. Can be obo or go_flat and others supported by Bio::OntologyIO. Default: obo
- update all the terms. Without -u, the terms in the database won't be updated to the contents of the file, in terms of definitions, etc. New terms will still be added.
- verbose output
- outfile for writing errors and verbose messages (optional)
- trial mode. Don't perform any store operations at all. (trial mode cannot test inserting associated data for new terms)
The following options are required if not using GMOD profile
- hostname for database [required if -p isn't used]
- database name [required if -p isn't used]
- password (if you need to provide a password to connect to your db)
- username (if you need to provide a username to connect to your database)
- driver name (e.g. 'Pg' for postgres). Driver name can be provided in gmod_config
The script parses the ontology in the file and the corresponding ontology in the database, if present. It compares which terms are new in the file compared to the database and inserts them, and compares all the relationships that are new and inserts them. It removes the relationships that were not specified in the file from the database. It never removes a term entry from the database.
This script works with Chado schema (see gmod.org) and accesse the following tables:
Terms that are in the database but not in the file are set to is_obsolete=1. All the terms that are present in the database are updated (if using -u option) to reflect the term definitions that are in the file. New terms that are in the file but not in the database are stored. The following data are associated with each term insert/update:
- Term name
- Term definition
- Relationships with other terms
- Secondary ids
- Definition dbxrefs
AUTHOR¶Lukas Mueller <firstname.lastname@example.org>
Naama Menda <email@example.com>
VERSION AND DATE¶Version 0.15, September 2010.