home / portal / procurement_coverage_cells

procurement_coverage_cells: 66

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
66 gvibuy_po_detail GVIBuy purchase-order detail pages budget-account-code Fund, appropriation, cost centre or object code on a purchase order not-applicable NOT HELD 0 0 account-coding-unjoined Not one field GVIBuy publishes on a purchase-order detail page is a fund, an appropriation, a cost centre or an object code, and with the detail crawl finished that is now a statement about the whole layer rather than about a sample. The query beside this cell enumerates every column we ingest from those pages and returns none. Separately, the header block of all 1,911 detail records the crawl returned was enumerated at build time and prints 39 distinct field labels in total - not one of them an account, a fund, an appropriation, a cost centre or an object code. That enumeration replaces an earlier hand read of a sample of pages, which had to carry its own denominator while the crawl was still running; the crawl has finished, the check is now the whole of it, and no page-count from the earlier reading is restated anywhere on this surface. We probed the publication route - GVIBuy's own detail page, which is where such a field would live - and it is not there. One qualification, because it is the one route left: 1 of the 10,347 attachment records staged off those detail pages has a filename naming object codes. An attachment is a file we have not opened and do not publish, so that is a place the coding may exist and not a place we have read it. The payment side publishes both halves of the government's account coding; the procurement side publishes neither, and nothing joins them. MEASURED SELECT COUNT(*) FROM pragma_table_info('gvibuy_po_header_detail') WHERE lower(name) LIKE '%account%' OR lower(name) LIKE '%fund%' OR lower(name) LIKE '%appropriat%' OR lower(name) LIKE '%cost_cent%' OR lower(name) LIKE '%object%'     1 0 /procurement/coverage#why-account-coding-unjoined 2026-11-21T22:40:46Z 2026-11-21T22:36:15Z
Powered by Datasette · Queries took 1.658ms