Proposal packet evidence

One source-backed handoff for review.

This page collects the scope facts, public data pull, QA results, requirement coverage, export manifest, and vendor-portal boundaries that support the proposal packet.

0

Requirement gaps

54

QA route/viewport checks

0

Axe-core violations

Scope lock

Buyer
City of San Jose
Title
Open Data Portal
Close
2026-06-24 12:00 PM PT
Submission
Electronic submission through the City's procurement portal, including all required forms and documentation if applicable.

Open-data pull

CKAN packages
170
Datastore resources
265
ArcGIS layers
149
Pull timestamp
2026-06-14T09:36:45.996Z
Refresh runs logged
7
Latest Hub views
1,776,736
Endpoint checks
59
CKAN package-search source

Requirement coverage

23 requirements tracked, 0 gaps, and 3 portal-dependent partials.

  • Electronic submission: the final upload and any portal-specific fields are completed in the City's procurement portal.
  • Local/small business preference: eligibility and any preference forms are confirmed before submission.
  • Portal attachments and forms: any portal-only attachments are completed within the procurement portal.

QA and fact-check status

The latest QA run checked 54 route and viewport combinations plus 23 functional behavior checks, with 0 axe-core violations, 0 overflow failures, 0 console errors, and 0 functional failures.

  • Every public record and metric on this site traces to the City's live CKAN and ArcGIS endpoints listed under Sources.

Export manifest

Each export is generated from the current public source pull and mirrored in the proposal packet for review.

ArtifactRows/itemsPurposePrototype asset
Source refresh log7Timestamped CKAN/ArcGIS source-pull history across recurring build pulses.source-refresh-log.csv
Source change monitor7Refresh-to-refresh count deltas for CKAN packages, datastore resources, ArcGIS layers, selected layers, and ArcGIS Hub views.source-change-monitor.csv
Search evidence12Live CKAN package_search terms, match counts, top source records, and launch discovery actions.search-evidence.csv
Source registry319Every CKAN package and ArcGIS layer, with owner/category/source URL.source-registry.csv
Resource inventory1,169Files, APIs, downloads, datastore flags, and generated package pages.resource-inventory.csv
Refresh plan19Launch refresh candidates with source endpoints and proposed review cadence.refresh-plan.csv
Field inventory368Field/schema metadata from selected CKAN datastore and ArcGIS pulls.field-inventory.csv
Source lineage319Crosswalk from source rows to prototype pages, briefs, APIs, and exports.source-lineage.csv
Launch readiness319Source-by-source launch review status, launch signals, quality issues, proof URLs, source URLs, and next actions.launch-readiness.csv
Topic taxonomy9Reviewer-facing portal topics generated from source rows, owners, readiness signals, and source URLs.topic-taxonomy.csv
Story evidence16Launch story sources, counts, fields, source URLs, resident questions, and delivery notes.story-evidence.csv
Owner review10Source-owner queue for launch review and department confirmation.owner-review.csv
Data quality audit319Freshness, metadata completeness, and source-linked cleanup notes.data-quality-audit.csv
Developer endpoints19Copy-ready CKAN datastore_search and ArcGIS REST examples.developer-endpoints.json
Endpoint health59Pull-time HTTP status and elapsed-time checks for CKAN, datastore, ArcGIS, layer-query, and Hub item URLs.endpoint-health.csv

Portal-only items

The prototype and proposal packet do not bypass protected Biddingo access. These items remain for normal vendor-portal review before upload.

  • Biddingo attachments
  • Biddingo forms
  • Q&A/addenda not visible unauthenticated
  • Hidden pricing worksheets or line-item fields
  • Mandatory certifications