SUEWS parameter database

curated values, linked and searchable, a citation on every one Home · Map · suews.io

Browse database / Review procedure

Review provenance with a registered verifier identity

Read the original evidence and assess the stored claim carefully. A review becomes part of the database’s verified state only when it is submitted by a GitHub account in the reviewed verifier registry and passes CI.

  1. Check that an assessment exists

    An Unaudited entry is not ready for sign-off. It first needs a structured evidence or composition assessment. Contact the team to add it to the review queue; report any concrete data problem separately.

  2. Read the original sources

    Verify the exact values, parameter source, method, place, representativeness, any declared urban setting, target and identity. For a composite, review component selection, completeness and slot or season mapping instead of re-reviewing each component’s values.

  3. Choose an evidence-based decision

    Use Verified only when the current assessment is fully supported. Otherwise request changes, mark the question unresolved, or require curation. Never infer a citation or correct a value by plausibility.

  4. Submit from your own GitHub account

    When the entry reaches Awaiting sign-off, use its GitHub sign-off button. CI authenticates your immutable GitHub user ID and checks the entry, evidence and policy revisions before incorporating the decision. An accepted issue closes automatically and remains linked as the durable review record. A rejected issue stays open and receives a CI comment with the failure reason; unregistered reviewers are also directed to the verifier qualification request.

Report an issue