Skip to content

Output data intake template

Use this template when adding a non-publication output that evidences DePaul hard-tech resources, labs, production infrastructure, fabrication, games, exhibitions, software, datasets, or deployed systems.

See also: outputs-layer-plan.md · output-intake-rules.md

Output record

Title:

Year:

Output type: (production_credit | theatrical_production | media_production | sound_recording | game | interactive_media | ar_vr_experience | exhibition | installation | software | dataset | hardware_prototype | instrument | technical_report | conference_presentation | professional_proceeding | public_documentation | community_project | curricular_project | deployed_system | portfolio | workshop | unknown)

Venue / context: (festival, theatre season, Project Bluelight, lab showcase, course, deployment site, etc.)

URL: (official DePaul or project page already cited in repo)

Description (1–3 sentences; what was produced):

People and roles

| Name | person_id | Role (creator | designer | developer | director | producer | technical_director | faculty_lead | student_lead | collaborator | contributor | advisor | curator | performer | researcher | unknown) | | --- | --- | --- | | | | |

person_role_evidence: (quote or cite where this person is named for this specific output — production page, press release, faculty bio for this artifact)

person_link_allowed: (true | false)

reason_person_link_not_added: (required when person_link_allowed: false — e.g., center directorship only; person not named on output page; grant PI without output page connection)

Resource map connection

Relevance to resource map (why this output belongs in the hard-tech map):

Related resource_id (if any):

Relationship (produced_by | uses | documents | demonstrates_capability | developed_in | hosted_by | supported_by | taught_in | related_topic | unclear):

resource_link_evidence: (quote tying the output to the resource — production location, facility name, instrument, deployed system; separate from person role evidence)

resource_link_allowed: (true | false)

reason_resource_link_not_added: (required when resource_link_allowed: false — e.g., topical similarity only; affiliation only; same school/center only)

Evidence file in repo:

Evidence URL:

hub_risk_note: (optional — e.g., third edge to UNI-003; CDM-016 Bluelight cluster; monitor weak inference)

| grant_id | relationship (funded_by | supported_by | developed_under | related_topic | unclear) | evidence text | | --- | --- | --- | | | | |

Intake decision

candidate_status: (include | maybe | exclude)

include_in_graph: (true | false on output record and link rows)

graph_inclusion_reason: (explicit documented role / explicit facility text / registry-only weak fit / person link excluded but output retained)

Why this is not a publication: (required — e.g., film production credit, game release, exhibition, software repo, no peer review)

Confidence: (high | medium | low)

Ambiguity notes (homonyms, unclear role, pre-DePaul work, student vs faculty credit):

Co-credit vs collaboration notes (production credits do not imply shared facility use or person–person collaboration edges):

After intake

  1. Add the output to data/outputs.yaml (OUT-###).
  2. Add rows to data/person_output_links.yaml for each DePaul person with explicit role evidence (person_link_allowed: true).
  3. Add rows to data/output_resource_links.yaml only when resource_link_allowed: true and evidence meets output-intake-rules.md § Allowed output–resource evidence.
  4. Regenerate:
python3 scripts/refresh_all.py

Rules reminder

  • Outputs are evidence objects, not publicity blurbs.
  • Do not infer resource use from affiliation, center membership, or co-presence in a program.
  • Do not infer person contribution from center or lab leadership alone.
  • Do not treat production credits as publications.
  • Do not move existing publications into outputs without documented review.
  • Output–resource links require explicit evidence (same bar as publication–resource links).
  • Evaluate person–output and output–resource evidence separately (Plant digital twin lesson).
  • When in doubt, include_in_graph: false and note needs_review.