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

Distinguish scraped from manually verified/corrected entries

Open
#77 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
database

Research direction

Start by locating the scraping and update flow, then inspect how entry metadata is stored and replaced. Compare separating raw scraped data from user corrections with recording each field's source. Done means repeated scrapes no longer overwrite manually verified or corrected metadata.

Written by the indexing model from the issue text.

Description

schema

In the event of an active platform which is being scraped multiple times, it's a good idea to know which entries have been manually adjusted or corrected, so that their metadata is not overridden with a flawed or incomplete version.

An ideal solution, IMO, would be for the raw, scraped data to be stored separately from manually corrected/user-provided data. From there, they could be merged every time an update is performed.

An alternate solution would be for the metadata to contain the source of the information, allowing skipping such unwanted overrides in this way.

Dominant language
C
Stars
95
Forks
52
Avg merge
7h 33m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 gbdev/database

All issues in gbdev/database

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.