home / portal / procurement_coverage_cells

procurement_coverage_cells: 49

The coverage matrix, one row per source x record kind x fiscal year, each carrying its state, its count, why it is in that state and the SQL that produced the count. Run the evidence_sql and you get n_records back.

This data as json

rowid source_key source_label record_kind record_kind_label fy_key state n_records prev_n_records why_code why_text evidence_kind evidence_sql evidence_citation evidence_lf_id probed_for_publication is_crawl_dependent drill_url computed_at run_id
49 gvibuy_requisitions GVIBuy requisitions requisition-identifier Requisition numbers printed on the line items of purchase orders we hold not-applicable PARTIAL 3284 3284 requisition-identifier-without-the-document PARTIAL here means one specific thing: we hold the IDENTIFIER and not the DOCUMENT it names. The detail crawl read 3,284 distinct requisition numbers off 12,736 of the 22,957 line items held, on 3,320 of the 4,391 purchase-order documents that have a detail page; the other 1,071 of those documents print no requisition number on any line. That is enough to say which purchase orders share a requisition and to hang the chain one link higher, and it is not enough to say what was requested, by whom, when, or what was approved or refused - none of which GVIBuy publishes. This count is also a count of numbers seen from below: a requisition that never became a purchase order prints on no line item and is invisible here, so nothing about how many requisitions were raised, rejected or abandoned may be read off it in either direction. Whether the requisition documents are published anywhere was not probed. MEASURED SELECT COUNT(DISTINCT requisition_number) FROM gvibuy_po_items WHERE requisition_number IS NOT NULL AND requisition_number <> ''     0 0 /procurement/coverage#why-requisition-identifier-without-the-document 2026-11-21T22:40:46Z 2026-11-21T22:36:15Z
Powered by Datasette · Queries took 1.767ms