dernbu/lawnet-scraper
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

[4] eLitigation catalog MVP #39

New issue
Open
opened 2026-06-14 05:23:58 +02:00 by dernbu · 0 comments
dernbu commented 2026-06-14 05:23:58 +02:00
Owner
Copy link

Objective

Add eLitigation listing/catalog ingestion and expose its records next to LawNet records.

After this slice, the product should clearly show that it has two independent sources, including records that do not yet correlate.

Dependencies

Depends on #38.

Scope

  • Add the minimal schema needed for eLitigation source records.
  • Implement eLitigation listing parser/client behavior against fixtures first.
  • Preserve eLitigation slugs exactly as opaque source identifiers.
  • Persist citation, title, decision date, court, case number, version text, availability, and raw listing payload.
  • Preserve unavailable records and unusual source responses.
  • Add source filtering and source labels to the dashboard.
  • Display unmatched LawNet and eLitigation records without forcing correlation.
  • Add fixture-backed tests for listing edge cases, duplicate discrepancies, unusual slugs, and unavailable records.

Out of scope

  • eLitigation document body or PDF fetching.
  • Automatic citation correlation between LawNet and eLitigation.
  • Full-text judgment search.

Done when

  • A mocked eLitigation listing run stores source records in PostgreSQL.
  • The frontend can browse LawNet and eLitigation catalog records.
  • Source filters and labels make source provenance visible.
  • Unavailable or malformed eLitigation records remain visible enough for debugging.
  • Existing LawNet catalog and detail flows still work.
## Objective Add eLitigation listing/catalog ingestion and expose its records next to LawNet records. After this slice, the product should clearly show that it has two independent sources, including records that do not yet correlate. ## Dependencies Depends on #38. ## Scope - Add the minimal schema needed for eLitigation source records. - Implement eLitigation listing parser/client behavior against fixtures first. - Preserve eLitigation slugs exactly as opaque source identifiers. - Persist citation, title, decision date, court, case number, version text, availability, and raw listing payload. - Preserve unavailable records and unusual source responses. - Add source filtering and source labels to the dashboard. - Display unmatched LawNet and eLitigation records without forcing correlation. - Add fixture-backed tests for listing edge cases, duplicate discrepancies, unusual slugs, and unavailable records. ## Out of scope - eLitigation document body or PDF fetching. - Automatic citation correlation between LawNet and eLitigation. - Full-text judgment search. ## Done when - A mocked eLitigation listing run stores source records in PostgreSQL. - The frontend can browse LawNet and eLitigation catalog records. - Source filters and labels make source provenance visible. - Unavailable or malformed eLitigation records remain visible enough for debugging. - Existing LawNet catalog and detail flows still work.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
temp
feat/53-rename-lawnet-routes
push-xrsnvuvuvsul
feat/37-bff-storage-frontend
l
feat/49-pg-bff-storage
push-zzvxlnkylqsp
feat/quick-and-dirty
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dernbu/lawnet-scraper#39
No description provided.