Provider Review Workflow ======================== Provider source sweeps create observations, not approved BC-NPPD facts. The expert review workflow turns an ignored sandbox into an approval manifest that can be validated and applied. Generate Review Inputs ---------------------- The preferred P29 path is to let FreshForge run the provider source-review workflow. Install the workflow extra if needed: .. code-block:: console python -m pip install -e .[workflow] Then run the provider review package launcher: .. code-block:: console .\scripts\build-provider-source-review.cmd PROV-SATIN -OpenReview The launcher invokes ``freshforge run`` against ``examples/workflows/providers/PROV-SATIN.yaml`` and opens ``outputs/provider_approval_review/PROV-SATIN/index.html`` when ``-OpenReview`` is included. Use ``PROV-NWM``, ``PROV-WCS``, ``PROV-PREMIER``, or ``PROV-OAKSUMMIT`` to select a different provider workflow. When adding or revising a provider workflow, generate a correctly shaped FreshForge YAML file rather than hand-building a command sequence: .. code-block:: console bc-nppd generate-provider-source-workflow PROV-PREMIER \ --catalog-url https://premierpacificseeds.ca \ --out-path examples/workflows/providers/PROV-PREMIER.yaml \ --force Then validate or run that file with FreshForge. For a new provider bootstrap smoke test, Oak Summit can be run with: .. code-block:: console .\scripts\build-provider-source-review.cmd PROV-OAKSUMMIT -OpenReview The lower-level manual fallback is to run or reuse a provider sandbox. For the Satinflower seed source sweep: .. code-block:: console bc-nppd scrape-provider-sandbox PROV-SATIN \ --database-instance vancouver \ --live-fetch \ --source-sweep \ --catalog-url https://satinflower.ca/collections/seed \ --max-pages 5 \ --raw-dir local/provider_raw \ --out-dir outputs/provider_sandbox_source_sweep/PROV-SATIN \ --json Build the expert approval review app: .. code-block:: console bc-nppd build-provider-approval-review \ outputs/provider_sandbox_source_sweep/PROV-SATIN \ --poc-dir data/poc/vancouver \ --out-dir outputs/provider_approval_review/PROV-SATIN \ --reviewer "expert reviewer" \ --json Open ``outputs/provider_approval_review/PROV-SATIN/index.html`` locally. Review And Export ----------------- The review app groups rows by botanical name. Use the search box, filters, and detail panel to inspect: * whether the candidate already matches a Vancouver PoC species; * supplier availability rows; * candidate attribute rows, including product descriptions and extracted ``Plant Details`` / ``Seed Details`` values when available; * provisional mowability rows, if present; * provider URLs and taxonomy/source-review flags. Use the selection checkboxes and **Batch Review** controls when several species need the same decision. Batch actions can: * select all currently visible species after search/filtering; * clear the current selection; * set the approval status on all selected species; * include or defer supplier rows on all selected approved species; * include or defer candidate attribute rows on all selected approved species; * include or defer provisional mowability rows on all selected approved species. Set a species-level decision: * ``approved`` for observations ready to enter the candidate PoC layer; * ``rejected`` for rows that should stay out; * ``deferred`` when no decision is ready; * ``needs_source_review`` when the source/provenance is not sufficient; * ``needs_taxonomy_review`` when the taxon needs name review before approval. Attribute rows default to deferred. Mowability rows default to deferred because mowability remains provisional. Supplier rows can be included with the species decision when supplier availability is the reviewed claim. Use **Download approval_manifest.csv** or **Copy CSV**. The static app does not write directly to the repository. Simple Apply Preview -------------------- For the easiest user-test path, download ``approval_manifest.csv`` from the review app into the default Downloads folder, then run: .. code-block:: console .\scripts\apply-downloaded-provider-approval.cmd -OpenPreview The command wrapper works on Windows systems that block direct PowerShell script execution. It validates the downloaded manifest, infers the provider ID from the CSV, copies it to the matching ignored scratch path, applies approved rows into ``outputs/provider_approved_vancouver``, regenerates downstream preview artifacts, validates the preview, and opens the static preview app when ``-OpenPreview`` is included. It also prints the preview path: .. code-block:: text outputs/provider_approved_vancouver/usability/index.html Use ``-ManifestPath`` when one CSV was saved somewhere else. Use ``-ManifestPaths`` to rebuild a cumulative preview from multiple reviewed provider manifests: .. code-block:: console .\scripts\apply-downloaded-provider-approval.cmd ` -ManifestPaths outputs/provider_approval_review/PROV-SATIN/approval_manifest.csv,outputs/provider_approval_review/PROV-NWM/approval_manifest.csv,outputs/provider_approval_review/PROV-WCS/approval_manifest.csv ` -OpenPreview The preview is cumulative only when all approved manifests are supplied, or when prior provider approvals have already been promoted into the tracked ``data/poc/vancouver`` base. A single-manifest preview starts from the tracked PoC base and will not include earlier provider runs that only existed in ignored ``outputs/``. The direct PowerShell fallback is: .. code-block:: console powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\apply-downloaded-provider-approval.ps1 -OpenPreview Greg or an automation agent can use the FreshForge workflow shape in ``examples/p21_downloaded_provider_approval_freshforge.yaml`` for the same validate/apply/validate-preview sequence. Reusable workflow sequencing should stay in FreshForge YAML; direct ``bc-nppd`` commands are fallback primitives. The script does not promote reviewed manifests into tracked product data. Only after human inspection should a reviewed manifest be copied into a tracked input path such as ``data/poc/vancouver/provider_data/reviewed_manifests/``. Validate And Apply ------------------ Save the exported CSV as a local approval manifest, then validate it: .. code-block:: console bc-nppd validate-provider-approvals path/to/approval_manifest.csv --json Dry-run an approved manifest into ignored outputs: .. code-block:: console bc-nppd apply-provider-approval-sequence path/to/approval_manifest.csv \ --poc-dir data/poc/vancouver \ --out-dir outputs/provider_approved_vancouver \ --json Dry-run multiple approved manifests cumulatively: .. code-block:: console bc-nppd apply-provider-approval-sequence \ path/to/satinflower_approval_manifest.csv \ path/to/nwm_approval_manifest.csv \ path/to/wcs_approval_manifest.csv \ --poc-dir data/poc/vancouver \ --out-dir outputs/provider_approved_vancouver \ --json For an unsupervised fixture-backed or explicitly requested preview, skip the static review app and auto-approve all non-excluded sandbox rows: .. code-block:: console bc-nppd auto-import-provider-sandboxes \ PROV-NWM PROV-WCS PROV-PREMIER \ --input-dir tests/fixtures/providers \ --poc-dir data/poc/vancouver \ --out-dir outputs/provider_auto_import_vancouver \ --sandbox-root outputs/provider_sandbox_auto_import \ --json This is a preview/import automation path, not a claim that provider-derived ecological attributes are reviewed facts. WCS excluded rows and any other ``excluded`` or ``ineligible`` sandbox candidates stay out of the import. Generated ``provider_data/`` outputs include the auto-approved manifest plus provider-side ``candidate_species.csv``, ``candidate_attributes.csv``, ``supplier_availability.csv``, and ``mowability.csv`` tables so all imported provider observations remain inspectable. If a full static review app has already produced an ``approval_manifest_draft.csv``, convert that draft to the same all-included decision shape before applying it: .. code-block:: console bc-nppd auto-approve-provider-manifest \ outputs/provider_approval_review/PROV-NWM/approval_manifest_draft.csv \ --out-path outputs/provider_approval_review/PROV-NWM/approval_manifest.csv \ --json The command approves every non-rejected row in the draft manifest, including species, supplier availability, candidate attributes, and mowability rows. Pass ``--approve-rejected`` only for explicitly requested exploratory previews where rejected rows should be included too. Only after expert review should the manifest be promoted to a tracked reviewed input path such as ``data/poc/vancouver/provider_data/reviewed_manifests/``. Raw fetched catalogue JSON, HTML, screenshots, and generated review apps remain ignored. Caveats ------- Provider approvals create candidate PoC data. They do not make native status, ecological scores, pollinator scores, UNI, PSI, RVI, or mowability score-readiness final.