Extract provider, description and price automatically; light invoice ledger view
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 10/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
Request (user intake, 2026-10-04)
Review all invoices and the intake process. Two complaints:
- 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. - 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
subjectandfrom,
andbackend/src/routes/emailDocuments.tsalready auto-processes invoice
intakes on arrival — the gap is thatextractInvoiceTextignored 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
- 主要语言
- TypeScript
- 星标
- 2
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DataTalksClub/dataops 的其他 Issue
-
backend bug human P1 portal testing
难度 4/5 3-5 天 新手友好度 35/100
DataTalksClub/dataops#248 · 4 条评论 ·
-
backend bug data frontend human P1 portal
难度 5/5 一周以上 新手友好度 25/100
DataTalksClub/dataops#244 · 7 条评论 ·
-
infra needs grooming P1
难度 4/5 3-5 天 新手友好度 35/100
DataTalksClub/dataops#235 ·
-
backend data enhancement frontend P1
难度 5/5 一周以上 新手友好度 25/100
DataTalksClub/dataops#232 · 10 条评论 ·
-
backend bug needs grooming
难度 3/5 1-2 天 新手友好度 75/100
DataTalksClub/dataops#227 · 1 条评论 ·
查看 DataTalksClub/dataops 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
farbenmeer/tapi#531 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
naver/egjs-flicking#971 ·
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
Tenant
难度 2/5 1-3 小时 新手友好度 66/100
MTES-MCT/Dossier-Facile-Frontend#2061 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
backnotprop/plannotator#1784 ·
维护者通常 1 天内回复