Add Data Extraction notes to processing for all systems
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by inspecting the existing data-extraction event mechanism in the PubMed system, then compare how other systems currently post oddities and exceptions to the console. Trace the processing entry points involved and identify what must be shared across processes. Done means these events are stored for later inspection and resolution for all systems, rather than only printed.
Written by the indexing model from the issue text.
Description
At the moment oddities and exceptions are not properly logged for future inspection and resolution. There needs to be a mechanism to store these events rather than just post them onto the console, and this mechanism needs to be available to all processes.
This mechanism exists for the pubmed system but not elsewhere.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- 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 ecrin-github/DataHarvester
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in ecrin-github/DataHarvester
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·