Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Backfill basic spec fields (power_w, release_year, operating_temp, markets)

Open
  • Is something wrong?
#166 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
47/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
data

Research direction

Start by reading the #163 index and the repository’s data-seeding or camera-record entry points; the issue does not name specific files or tests. Choose a brand or series batch and source the four fields from reliable references, especially distributor launch dates or press releases for release_year. Leave unsupported values undefined; done means adding only sourced values without guessing.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

Standing data-backfill lane for four low-coverage but easy-to-source spec fields (all typically on the datasheet). Joins the #163 index.

Coverage of 11,421 cameras (2.17.0 prep):

Field Coverage Notes
markets 10,924 (96%) ISO region tags — now near-saturation
operating_temp_c 9,566 (84%) e.g. -30 to 60
power.consumption_w 7,949 (70%) PoE-budget planning
release_year 2,335 (20%) First-sold year — regressed 41%→20%: new brands land faster than it's filled, and it's rarely on datasheets (copyright/revision year ≠ release year), making it the laggard

markets / operating_temp_c / power.consumption_w are largely done. release_year is the remaining focus — and the hardest, since datasheets seldom state a true first-sold year; prefer distributor launch dates / press releases and leave undefined rather than guess from a datasheet revision date.

Best done in brand/series batches where the datasheet format is shared. Leave a field undefined when not stated — never guess (esp. markets, which is region-availability, not where it could be sold).

Dominant language
JavaScript
Stars
267
Forks
21
Avg merge
4h 18m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ch-bas/cctv-camera-database

All issues in ch-bas/cctv-camera-database

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.