How jellyellie/parkinson-annotator works
Project type and purpose
• It is neither a typical full-stack web app nor a compiler, but a data-integration and annotation tool that likely runs as a batch or on-demand pipeline with a small user-facing search component.
File structure
• At present the project only contains README.md, implying the full directory layout is not yet committed.
• Expect future top-level directories such as:
· src/ (pipeline code)
· data/ (raw and processed files)
· config/ (database and API credentials)
· scripts/ (build or deployment scripts)
· tests/ (unit/integration tests)
README for additional insights
• Key milestones:
1. Extract data from various input files
2. Load data into SQL
3. Incorporate ClinVar API enrichment
4. Create a search function
• Use clear labels such as “Ingestion”, “Transformation”, “DB Storage”, “ClinVar API”, “Search Service”, “UI/CLI.”
Detail
• Pipeline stage as its own block.
• Config/orchestration layer to show how the pipeline is deployed or scheduled.
• Retry, logging, or monitoring components if present.