Skip to content

Grant data intake template

Use this template when adding a new grant to data/grants.yaml (and the companion link files). Copy the block below into a working note or pull request description, fill in what is known, and leave unknown fields blank.

Governance: Grant ingestion governance — grant existence, PI identity, and facility linkage are separate evidence questions. Unresolved PI does not block grant entry.

Grant record

Grant title:

Funder:

Program / portfolio name:

Grant type: (internal_grant | external_grant | seed_grant | equipment_grant | center_grant | education_grant | research_grant | fellowship | award | proposal | unknown)

Status: (active | completed | proposed | awarded | unknown)

Start year:

End year:

Amount:

Lead unit / college / department:

Evidence status (required for bulk / refactor intake)

Dimension Status
Grant evidence verified | probable | needs_review
Resource links resolved | unresolved | not_supported

People

Name person_id (if known) person_identity_status Role (pi | co_pi | collaborator | director | participant | awardee | unknown)
resolved | unresolved | ambiguous
  • resolved — assign person_id; may add person_grant_links.yaml.
  • unresolved — record person_name + role on grant only; no person_id; defer PGL.
  • ambiguous — list homonym/candidate notes; do not pick an ID without evidence.
resource_id Relationship (funds | supports | uses | develops | hosted_by | administered_by | related_topic | unclear) Evidence quote

Leave empty when resource_links_status is not_supported or unresolved. Do not infer from college or funder name alone.

Source

Source URL:

Evidence file in repo (e.g. data/Internal Grants Summary (last 4 cycles)(All).csv, resources/CDM/CDM-011.md):

Evidence text (quoted or paraphrased from source):

Confidence: (high | medium | low)

Notes (missing fields, follow-up needed):

After intake

  1. Add or update the grant in data/grants.yaml — even if PI is unresolved (use person_name without person_id).
  2. Add person links in data/person_grant_links.yaml only when person_identity_status is resolved (or run python3 scripts/build_grants_layer.py if sourced from bulk CSV with known IDs).
  3. Add resource links in data/grant_resource_links.yaml only when evidence explicitly connects the grant to a resource and resource_links_status is resolved.
  4. Regenerate exports:
python3 scripts/build_grants_layer.py   # if rebuilding from CSV
python3 scripts/export_graph_tables.py

Rules reminder

  • Do not discard evidence-backed awards because the PI is missing from people.yaml.
  • Do not invent person_id, people records, co-PIs, or facility links without evidence.
  • Do not infer collaboration from shared ORS or hub pages alone.
  • Do not link grants to UNI-001 as a facility-use edge.
  • Do not invent funders, dates, amounts, or co-PIs without evidence.

See also: Grant ingestion filter audit for bulk parser behavior.