Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Extract provider, description and price automatically; light invoice ledger view

Aperta
  • Qualcosa non va?
#237 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
10/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
backend-api-design, frontend

Direzione di ricerca

The issue says the work shipped the same day, so first check whether any follow-up remains. Read backend/src/invoices/extract.ts and backend/src/routes/emailDocuments.ts for extraction and intake behavior, then inspect the portal invoice ledger described in the issue. Done means the requested provider, description, and price extraction and dense ledger view are in place without overwriting operator-corrected drafts.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

backend enhancement frontend

Request (user intake, 2026-10-04)

Review all invoices and the intake process. Two complaints:

  1. Provider extraction is poor — rows show "Unidentified provider" or raw
    identifiers like "VAT/GST Number DE…". The operator wants name, title and
    price extracted from a forwarded invoice automatically.
  2. The invoice review table is too heavy. Wanted: a dense ledger view like the
    published expense sheet (Date sent, Date paid, Provider, What, Price $,
    Price EUR, Statement, Count) — not the current 4-column review queue.

../dapier may be updated if processing needs it.

Findings

  • The dapier intake contract already carries the email subject and from,
    and backend/src/routes/emailDocuments.ts already auto-processes invoice
    intakes on arrival — the gap is that extractInvoiceText ignored those
    signals and only parsed two PDF layouts (AWS, Stripe), with an issuer
    heuristic that happily returned "VAT/GST Number …" lines.
  • No dapier change is required; normalization lives dataops-side.

Shipped (same day)

  • Extraction (backend/src/invoices/extract.ts): email subject/sender hints
    with a canonical provider catalog; "receipt/invoice from X" anchor; issuer
    plausibility + credibility filters (field-label lines and payment-processor
    noise rejected); generic labeled total/date/currency/invoice-number parsing
    incl. European comma decimals; subject-derived description. Governance kept:
    extraction never invents amountEur/paymentEvidence.
  • Untouched pending drafts are re-extracted automatically when a duplicate
    arrives; new POST /invoices/{id}/reextract action (portal + CLI) upgrades
    old bad rows on demand. Operator-corrected drafts are never overwritten.
  • Portal: the heavy table is replaced by a dense invoice ledger (sheet columns,
    pending first, negative prices, row-click review, compact reprocess form,
    re-extract button on eligible drafts); 44px mobile row floor kept.

Refs #232

Lingua principale
TypeScript
Stelle
2
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DataTalksClub/dataops

Tutte le issue di DataTalksClub/dataops

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.