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

[6] eLitigation document ingestion and detail parity #41

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

Objective

Fetch eLitigation detail pages and PDFs so eLitigation reaches detail-page parity with LawNet.

After this slice, a correlated or unmatched case can expose eLitigation metadata, judgment HTML, and PDF artifacts alongside LawNet artifacts where both sources exist.

Dependencies

Depends on #40.

Scope

  • Implement eLitigation detail-page fetch and parsing.
  • Implement eLitigation PDF fetch and validation.
  • Detect page-not-found, maintenance, invalid detail pages, and invalid PDF responses even when HTTP status is 200.
  • Store raw detail pages, extracted judgment HTML, PDFs, source URLs, content hashes, and artifact metadata.
  • Preserve exact slugs and unavailable records throughout detail ingestion.
  • Update case detail API and UI to expose eLitigation source artifacts.
  • Let users choose between LawNet and eLitigation renditions where both exist.
  • Add fixture-backed tests for unusual slugs, unavailable records, semantic error pages, and invalid PDF responses.

Out of scope

  • Full public sanitized HTML reader experience.
  • Full-text judgment search.
  • Broad queue/scheduler hardening beyond what this flow needs.

Done when

  • eLitigation records can be fully ingested from listing to detail artifacts.
  • Case detail pages can show eLitigation metadata and available artifacts.
  • Invalid HTML and PDF responses are rejected without poisoning stored artifacts.
  • Existing unavailable records remain visible.
  • Correlated LawNet/eLitigation cases can display source-specific artifact choices.
## Objective Fetch eLitigation detail pages and PDFs so eLitigation reaches detail-page parity with LawNet. After this slice, a correlated or unmatched case can expose eLitigation metadata, judgment HTML, and PDF artifacts alongside LawNet artifacts where both sources exist. ## Dependencies Depends on #40. ## Scope - Implement eLitigation detail-page fetch and parsing. - Implement eLitigation PDF fetch and validation. - Detect page-not-found, maintenance, invalid detail pages, and invalid PDF responses even when HTTP status is 200. - Store raw detail pages, extracted judgment HTML, PDFs, source URLs, content hashes, and artifact metadata. - Preserve exact slugs and unavailable records throughout detail ingestion. - Update case detail API and UI to expose eLitigation source artifacts. - Let users choose between LawNet and eLitigation renditions where both exist. - Add fixture-backed tests for unusual slugs, unavailable records, semantic error pages, and invalid PDF responses. ## Out of scope - Full public sanitized HTML reader experience. - Full-text judgment search. - Broad queue/scheduler hardening beyond what this flow needs. ## Done when - eLitigation records can be fully ingested from listing to detail artifacts. - Case detail pages can show eLitigation metadata and available artifacts. - Invalid HTML and PDF responses are rejected without poisoning stored artifacts. - Existing unavailable records remain visible. - Correlated LawNet/eLitigation cases can display source-specific artifact choices.
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#41
No description provided.