HGNC
Approved human gene nomenclature and stable HGNC identifiers.
HGNC ↗Identifier sources
VennScope separates literal set comparison from identifier conversion. Online mapping is an explicit network action; local/offline mapping uses a table that you provide.
Supported online conversions use the UniProt ID Mapping service. When you run online mapping, the selected identifiers are sent directly from your browser to the named service. VennScope records the advertised route and access time and reports mapped, unmapped and one-to-many records.
You can use a local mapping table when the required correspondence is available to you. The mapping table is read in the browser. Matching fields and file provenance should be reviewed before creating a derived dataset.
Approved human gene nomenclature and stable HGNC identifiers.
HGNC ↗NCBI Gene, RefSeq and Taxonomy provide gene, sequence and organism identifiers used in biological workflows.
NCBI ↗Ensembl stable identifiers distinguish gene, transcript and protein features.
Ensembl ↗Mappings can be one-to-many, many-to-one, obsolete, species-dependent or unavailable. Moving from gene to protein level can expand a list because one gene can be associated with multiple protein products. VennScope therefore preserves the original list, reports ambiguous outcomes and creates a derived dataset only after an explicit mapping action.
Reference databases evolve. For consequential work, retain the mapping CSV or local mapping table, source/service name, organism, mapping route and access date with the analysis.
External reference services remain governed by their own documentation, licences, terms and availability. VennScope does not redistribute a complete copy of those databases as part of the core web application.