CACrown ArchivesThe cinema collection
EN/FR
Search
Menu
Research dossier · General Reference

VanHacks

Open-knowledge reference entry

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionOct 19, 2025
Entity authorityQ104844814 ↗
Source-derived summary

VanHacks is an annual hackathon that is part of Vancouver Startup Week. The focus of the hackathon is creating solutions for local non-profit organizations from the Vancouver area over the course of 36 hours. Sponsors of the event have included KPMG, Best Buy, Slack (software), Lighthouse Labs, Nespresso, and Red Bull.

History

VanHacks was created in 2016 by TTT Studios. The event did not run in 2017. In 2018 and 2019 VanHacks partnered with Vancouver Startup Week, and served as an official hackathon for the week long event held in September.

The 2018 and 2019 versions of the event were held at the TEC Hub at the downtown campus of BCIT (British Columbia Institute of Technology).

Editorial summary

This brief starts where responsible research should: with the source description of “VanHacks” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.

Editorial reviewA practical starting point whose main value is the path it opens into stronger specialist and primary sources. The current lead gives the account dated anchors—2016, 2017, 2018, 2019—that can be checked directly. The linked authority record independently contributes the date 2016. The account is most persuasive where VanHacks, Open-knowledge and entry can be independently traced.
Editorial analysis

Why this record matters

The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.

Evidence profile

The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Oct 19, 2025. The linked authority identifier is Q104844814. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2016, 2017, 2018 and 2019.

Critical limits

The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “VanHacks”, its source revision and the description used here.
  2. Expand the search: follow VanHacks primary sources, VanHacks archive and VanHacks research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “VanHacks”?
  2. Which cited source is closest to the event, object or claim?
  3. What terminology or title could unlock a more precise catalogue search?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “VanHacks” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.