cache raw ORDS data in myra
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- data-engineering, databases
Research direction
Start by tracing the existing discrepancy check that uses agreement changed dates and the ORDS/FTA JSON-to-CSV workflow. Confirm how current Myra data is stored and how Metabase reports are scheduled. Done means raw ORDS data is refreshed daily and available for the proposed discrepancy report.
Written by the indexing model from the issue text.
Description
Doing discrepancy checks always means the same thing, either directly querying ORDS/FTA or converting the JSON to CSV, dumping in a table, and comparing to what's in Myra. If we cache the up to date ORDS data daily we can schedule a report in metabase to make sure things are set. Right now it just checks the changed date on agreements.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from bcgov/range-api
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100