Repository navigation
Tokens & Variables
Vince LaGrassa edited this page Mar 20, 2025
·
18 revisions
Tokens are changing values that may be used in strings. They are typically used in filenames / filepaths, to distinguish e.g. between data files for different species or different releases.
For example, some filepaths may be given in the format:
... /{ SPECIES }/{ RELEASE }/sample_file_name-{ SPECIES }-{ RELEASE }.txt
If we wanted to use the version of this file associated with C. elegans from the (made-up) CaeNDR release on Jan 1, 2000, we would look for the file:
... /c_elegans/20000101/sample_file_name-c_elegans-20000101.txt
| Token | Description | Values |
|---|---|---|
SPECIES |
The relevant Caenorhabditis species for a given dataset or operation. The (unofficial) format is genus initial + underscore + species name -- in our case, this means all valid values begin with c_. |
c_elegans, c_briggsae, c_tropicalis
|
RELEASE |
The CaeNDR release that a data file was released in. New values added when new dataset releases are created. | "YYYYMMDD" format |
SVA |
The CaeNDR release to use for the Strain Variant Annotation table & tool. This has the same format (and possible values?) as the RELEASE token, but is kept separate because this tool may lag behind the most recent CaeNDR release - i.e. the SVA release and the "main" release may be different. |
"YYYYMMDD" format, same as RELEASE
|
GENOME |
An attached to a given release, relevant for locating the correct FASTA file. I believe this is now a more generic version of the WB token, since CaeNDR expanded from using specifically WormBase data to also using lab-produced genomes. Typically 1-to-1 with RELEASE values, but (a) it is possible for multiple CaeNDR releases to use the same genome, and (b) the genome value may be lab-internal or lab-specific, i.e. have some meaning within the lab that isn't captured by the CaeNDR release value alone. |
Could be anything - WS276 (from WormBase), Feb2020 (from Andersen Lab), etc. |
STRAIN |
An identifier for a specific strain. Mostly relevant for the Genome Browser tool's IGV Browser element, which needs to pull files for specific strains. |
BRC20067, etc. |
USER_ID |
The unique internal ID of a CaeNDR user who submitted a given data file, e.g. a phenotype trait file. | GCP Datastore Key |
PRJ |
WormBase project number associated with a dataset or release. Pulled from WormBase. May not be relevant going forward, with new CaeNDR release format. |
PRJNA13758, etc. |
WB |
WormBase version associated with a dataset or release. Pulled from WormBase. May not be relevant going forward, with new CaeNDR release format. |
WS276, etc. |
A few notes:
- Probably 85~90% of the time, you only need to care about the
SPECIESandRELEASEtokens. All the others are pretty niche and context-specific; theSVAtoken, for example, is pretty much only relevant to the Strain Variant Annotation tool. - The
SVAtoken may be referred to withRELEASE, if the Strain Variant Annotation versioning scheme isn't relevant from a particular perspective. (This can be a bit confusing, but also, it's pretty infrequent that we actually care about this difference.) - The
GENOMEtoken value is relevant when creating a new dataset release, and will appear on the Dataset Release page. It's mostly used to associate lab-internal versioning with CaeNDR release versioning. It's possible for multiple releases to use the sameGENOMEvalue, if they're based on the same FASTA genome file. - The tokens
PRJandWBare holdovers from an older dataset versioning system, and don't appear to be very relevant going forward. It may be helpful to know what they meant, though, if dealing with old data.
| Variable | Description |
|---|---|
MODULE_{NAME}_CONTAINER_NAME |
The name of the Docker container to look for to access this module. |
MODULE_{NAME}_CONTAINER_VERSION |
The version tag to look for on the Docker container. |
Note that the Image Thumbnail Generator module uses a slightly different format:
| Variable | Description |
|---|---|
MODULE_IMG_THUMB_GEN_SOURCE_PATH |
The path in GCP where images are held. |
MODULE_IMG_THUMB_GEN_VERSION |
The version tag to look for on the Docker container. (Same as above) |
See (tools section)
See (GCloud docs)
| Variable | Description |
|---|---|
MODULE_SITE_BUCKET_PHOTOS_NAME |
The "photos" bucket name. |
MODULE_SITE_BUCKET_ASSETS_NAME |
The "assets" bucket name. |
MODULE_SITE_BUCKET_PRIVATE_NAME |
The "private" bucket name. |
MODULE_SITE_BUCKET_PUBLIC_NAME |
The "public" bucket name. |
MODULE_SITE_BUCKET_DATASET_RELEASE_NAME |
... |
Override:
| Variable | Description |
|---|---|
MODULE_SITE_BUCKET_PUBLIC_NAME_OVERRIDE |
... |
| Variable | Description | File Type |
|---|---|---|
BAM_BAI_PREFIX |
||
BAM_BAI_DOWNLOAD_SCRIPT_NAME |
||
EULA_FILE_NAME |
The file containing the site's End-User License Agreement. | Markdown |
| Variable | Description | File Type |
|---|---|---|
FASTA_FILENAME_TEMPLATE |
||
FASTA_EXTENSION_FILE |
||
FASTA_EXTENSION_INDEX |
Files used primarily to build the SQL database tables.
| Variable | Description | File Type |
|---|---|---|
GENE_GTF_FILENAME |
... | Zipped GTF (.gtf.gz) |
GENE_GFF_FILENAME |
... | Zipped GFF (.gff3.gz) |
GENE_IDS_FILENAME |
... | Zipped Text (.txt.gz) |
SVA_CSVGZ_FILENAME |
... | Zipped CSV (.csv.gz) |
| Variable | Description | Type |
|---|---|---|
MODULE_SITE_PASSWORD_PROTECTED |
Whether to request a password to access the site at all. Relevant for QA site. | boolean |
MODULE_SITE_CART_COOKIE_NAME |
Name for the cookie to use to store the user's cart, if they are requesting strains. | string |
MODULE_SITE_CART_COOKIE_AGE_SECONDS |
Timeout until the cart cookie expires, in seconds. | int |
MODULE_SITE_PASSWORD_RESET_EXPIRATION_SECONDS |
Timeout until a "password reset" link expires, in seconds. | int |
USER_OWNED_ENTITY_CACHE_AGE_SECONDS |
Timeout for the local cache of User entities, specifically when loading entities that are owned by users. Makes big queries where many objects have the same users much more efficient (e.g. pulling up all of a user's generated reports). | int |
...
Getting set up? Start here!
Looking for tutorials on the software & services we use?
Trying to figure out what goes where?
Want to make changes?
Having trouble?
- Troubleshooting