From e85df2916ce7ba74c0dc8fd6f01d2ddf2337fb0d Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Wed, 19 Aug 2026 08:09:51 +0000 Subject: [PATCH] docs: clarify CVP IS basic-search pagination --- references/cvp-is-organization-route.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/references/cvp-is-organization-route.md b/references/cvp-is-organization-route.md index 94eff3b..7b283f3 100644 --- a/references/cvp-is-organization-route.md +++ b/references/cvp-is-organization-route.md @@ -13,7 +13,7 @@ Keep the remaining advanced-search fields present and empty when reproducing the 1. Search the exact authoritative client name first. A partial legal-name substring is supported as a discovery fallback, but it can broaden results and must not be treated as identity evidence. 2. Require HTTP success and HTML content, then parse complete result-table rows. The live table exposes basic fields including procurement title, procurement ID, contracting authority, publication date, submission deadline, procedure, status, winner-selection date when present, and estimated value. 3. Compare the contracting-authority cell in every retained row against the intended VSSA client. Preserve exact names and reject near-name or parent/subordinate-authority collisions rather than assuming that the search input scoped every result correctly. -4. Follow all result pages. Derive pagination from the returned HTML or its `writePageSelection(...)` call rather than hard-coding a table identifier or page count. +4. Follow all result pages. Derive pagination from the returned HTML or its `writePageSelection(...)` call rather than hard-coding a table identifier or page count. On the validated basic-search response, the first `writePageSelection("", "...d--p=...")` argument is the **last page number/page count**, not the number of result rows; request pages `1..N` using the live `d--p` key and de-duplicate complete rows. Do not divide that argument by the visible page size—a client with `writePageSelection("23", ...)` exposed 229 rows across 23 pages, not three pages derived from an assumed 230-row total. 5. Treat the HTML table as discovery metadata only. Open the procurement record and its relevant notice/attachment, classify the body and procurement stage, and cite the direct supporting page or document before mapping a system, supplier, contract, delivery, hosting, or completion claim. Live validation on 2026-08-19 used both `Lietuvos Respublikos Vyriausybės kanceliarija` and partial `Vyriausybės kanceliarija`. Each returned HTTP `200` HTML, the same `39` total rows, and authority cells displaying the exact full legal name. The first page exposed ten rows, including IT-relevant titles, confirming that this route is useful for current-procurement discovery but still requires row-level identity and body-level stage checks.