Refine the daily Technopedia API pull so that any child dependencies are automatically resolved
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 8
- Avg merge
- 23h 38m
- Merged PRs (30d)
- 15
Description
Currently in the daily API pull from Technopedia (and subsequent insert into GEAR), if there is a child dependency that is violated (e.g. a softwareProduct title is being inserted into the database, but its parent softwareFamily reference does not exist) the insert fails and is not caught. It has to manually be resolved or hope that a subsequent API pull will correct the issue once that record is updated again. This should be automatically resolved so that GEAR's schema matches the data in Technopedia.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the daily Technopedia API pull through its insertion path into GEAR, focusing on how child dependencies such as softwareProduct and softwareFamily are handled. Done means a missing parent dependency is automatically resolved or otherwise handled so the insert succeeds and GEAR's schema matches Technopedia data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100