Curated Hubs

QA on hgwdev

From a user's perspective, the curated hubs should behave like all other assemblies. The data files for curated hubs live in /gbdb like all other assemblies:

• /gbdb/$db/

You make any HTML edits in /trackDb and continue with a make to update hgwdev and hgwbeta. Performing a make will populate one of the following directories:

• /gbdb/$db/hubs/alpha
• /gbdb/$db/hubs/beta
• /gbdb/$db/hubs/public

These directories have the HTML files for the track description pages, hub.txt, and trackDb.txt files.

To keep the file list organized, you should create a list of the general /gbdb files and another file list for the alpha/beta/public directories.

Staging on hgwbeta

When staging the assembly to hgwbeta, you will FIRST have to push:

• /gbdb files
• Create an empty database for the assembly

Then do a make beta DBS=$db in trackDb to update the /gbdb/$db/hubs/beta directory. Using the gbdbPush script, push the entire contents of that directory to hgwbeta.

Staging on hgwbeta-public

Similar to the staging process on hgwbeta, the /gbdb files will have to the RR since /gbdb is shared between hgwbeta-public and the RR.

• Push /gbdb files to the RR
• Do a make public DBS=$db
• Use the gbdbPush script to push the /hubs/public directory from hgwdev to hgwbeta

Releasing to the RR

Once everything looks good on hgwbeta-public:

• Push the empty database to the RR (tdbPush script works just fine)
• Ask cluster-admin to push the /gbdb/$db/hubs/public from hgwbeta to the RR.

After the assembly is on the RR, finish the QA like any other assembly (edit newsarch.html, credits.html, FAQreleases.html, etc.)