Skip to content

Add geospatial sample provenance guard#379

Open
taherdhanera wants to merge 1 commit into
SCIBASE-AI:mainfrom
taherdhanera:taherdhanera/scibase-17-geospatial-sample-provenance-guard
Open

Add geospatial sample provenance guard#379
taherdhanera wants to merge 1 commit into
SCIBASE-AI:mainfrom
taherdhanera:taherdhanera/scibase-17-geospatial-sample-provenance-guard

Conversation

@taherdhanera
Copy link
Copy Markdown

/claim #17

Summary

Adds geospatial-sample-provenance-guard, a self-contained Scientific Knowledge Graph Integration slice that validates field-sample and specimen location graph edges before they appear on entity pages or public discovery recommendations.

The guard evaluates:

  • latitude/longitude ranges
  • CRS normalization to graph policy
  • country/coordinate consistency
  • sensitive-site coordinate precision and redaction needs
  • sample voucher/specimen accession links
  • dataset DOI resolution and sample-to-dataset edge alignment
  • collection-date plausibility
  • public recommendation safety for sample-location graph paths

Non-overlap

This is not a broad graph extractor/navigator, link audit, ontology drift/alias/synonym guard, relationship conflict arbiter, author-affiliation disambiguation module, artifact lineage guard, evidence freshness checker, instrument-method compatibility guard, reproducibility route module, recommendation visibility/diversity guard, negative-result replication guard, measurement harmonization guard, claim qualifier guard, ethics provenance guard, funder award lineage guard, clinical trial registry guard, or software/runtime compatibility guard. It focuses specifically on geospatial field-sample provenance and safe location-edge publication.

Local validation

Run from geospatial-sample-provenance-guard/:

npm run check
npm test
npm run demo
npm run demo:video

All four commands passed locally.

Reviewer artifacts

  • reports/summary.json
  • reports/reviewer-packet.md
  • reports/summary.svg
  • reports/demo.webm

Safety

All data is synthetic. The module does not call geocoders, repositories, GIS systems, ontology services, specimen registries, journal systems, or external APIs. It does not include private field locations, real endangered species data, credentials, or live graph mutations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant