Distinguish scraped from manually verified/corrected entries
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 95
- Forks
- 52
- Avg merge
- 7h 33m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100