### writedb_entry - exports EMBL or GFF3 files from Chado.

### Synopsys

writedb_entry is a wrapper script around Artemis's ReadAndWrite entry functions, which allows export to EMBL and GFF3 formats. It can be run in 3 ways.

The default method is the 'swing' method (because that's the original behaviour), which assumes that you are running it either on your own machine or on a server with X11 forwarding setup. Any errors or login prompts will popup in a graphical user interface as windows. In this mode, if it is not on your machine or no X11 is available, then any attempts to prompt will result in exceptions.

The 'console' mode is for running interactively on the shell without the need for a graphical user interface. All user-prompting (like password entry) is done inside the shell. Useful for one-offs where there is no X11 forwarding.

The 'script' mode is for batch runs where you don't want any user prompting. Passwords must be supplied as a command line parameter if needed in this case.

### Command line parameters

-f
  [y|n] flatten the gene model, default is y
-i
  [y|n] ignore obsolete features, default is y
-s
  space separated list of sequences to read and write out
-o
  [EMBL|GFF] output format, default is EMBL
-a
  [y|n] for EMBL submission format change to n, default is y
-pp
  [y|n] read polypeptide domain features, default is n
-c
  the URL for your Chado database e.g. db.genedb.org:5432/snapshot?genedb_ro (you can also do this by using the -Dchado=... method, but this -c parameter will override that)
-u
  [swing|console|script] the UI mode : run in swing (with popup dialog boxes) mode, run in console mode (choices entered in the console window), or in script mode (all choices default to continue, all parameters passed on command line)
-p
  the password for connecting to the Chado database (this is required in script mode, where passwords can not be passed interactively)
-fp
  the file path (the folder you want to save the files in)

### Examples

#### 1. Using in swing mode.

All prompting would then happen via graphical dialog boxes. In this example I am running this locally on my desktop machine. `$ /Volumes/us/data/gv1/workspace/artemis/etc/writedb_entry -c "db.genedb.org:5432/snapshot?genedb_ro" -o GFF -s Tcruzi_999 read :: Tcruzi_999 write :: Tcruzi_999.gff reading options from "/Users/gv1/.artemis_options" done`
A prompt for login details.
A prompt detailing a problem.

#### 2. Using interactively in console mode :

All prompting would then happen on the console. In this example I am running this on a server. `$ writedb_entry -c "db.genedb.org:5432/snapshot?genedb_ro" -o GFF -u console -s Tcruzi_999 read :: Tcruzi_999 write :: Tcruzi_999.gff Enter Password: Destination format can't handle all keys/qualifiers - continue? region can't have isObsolete as a qualifier(y/n): y done`

#### 3. Using in script mode :

In these examples I am running them on a server. Note that there is no password needed as it's going to the public snapshot. `$ writedb_entry -c "db.genedb.org:5432/snapshot?genedb_ro" -o GFF -u script -s Tcruzi_999 read :: Tcruzi_999 write :: Tcruzi_999.gff Desti` If there was a password needed, you would have to enter it as follows. `$ writedb_entry -c "db.genedb.org:5432/snapshot?genedb_ro" -o GFF -u script -p mypass -s Tcruzi_999 read :: Tcruzi_999 write :: Tcruzi_999.gff Destination format can't handle all keys/qualifiers - continue? : region can't have isObsolete as a qualifier : y done`