Difference between revisions of "Website:Adding new Species"

From WormBaseWiki
Jump to navigationJump to search
(Created page with "Whenever a new species is added, we need to update the website in several places. = Wormbase/website = In the main website repository: https://github.com/WormBase/website ...")
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
Whenever a new species is added, we need to update the website in several places.
 
Whenever a new species is added, we need to update the website in several places.
  
 +
 +
The normal "low-maintainance" species procedure described below is for non-core species (aka Tier III). When a core-species (aka Tier II) is added, which shouldn't happen too often, different steps need to be taken.
  
 
= Wormbase/website =
 
= Wormbase/website =
Line 10: Line 12:
 
== wormbase.conf <gff> <data_sources> ==
 
== wormbase.conf <gff> <data_sources> ==
  
== GBrowse config added ==
+
== GBrowse ==
 +
 
 +
GBrowse configuration will be created automatically during the build process.  The new species will need to be manually added to the primary GBrowse.conf file.
  
 
= WormBase/website-admin =
 
= WormBase/website-admin =

Latest revision as of 14:10, 10 April 2014

Whenever a new species is added, we need to update the website in several places.


The normal "low-maintainance" species procedure described below is for non-core species (aka Tier III). When a core-species (aka Tier II) is added, which shouldn't happen too often, different steps need to be taken.

Wormbase/website

In the main website repository: https://github.com/WormBase/website

wormbase.conf <species_list>

wormbase.conf <gff> <data_sources>

GBrowse

GBrowse configuration will be created automatically during the build process. The new species will need to be manually added to the primary GBrowse.conf file.

WormBase/website-admin

In the website admin repository: https://github.com/WormBase/website-admin

/lib/WormBase/Update/Staging/BuildXapianDB.pm