Skip to content

Publication data intake template

Use this template when adding a publication that evidences DePaul hard-tech resources, labs, instrumentation, or cross-unit technical work. Copy the block below, fill in known fields, and leave unknowns blank.

See also: publication-intake-rules.md · publications-layer-plan.md

Publication record

Title:

Year:

Publication type: (journal_article | conference_paper | preprint | proceedings | book_chapter | technical_report | thesis | poster | presentation | dataset | software | unknown)

Venue / journal / conference:

DOI:

URL:

Abstract (optional; only if already in repo evidence):

Authors

| Name | person_id (if in people.yaml) | Role (author | coauthor | corresponding_author | advisor | student_author | unknown) | DePaul author? (yes/no/unclear) | | --- | --- | --- | --- | | | | | |

Intake decision

candidate_status: (include | maybe | exclude)

pre_depaul_work: (true | false)

author_identity_evidence: (e.g., DePaul affiliation on Crossref author list; faculty profile lists paper; ORCID match; homonym risk and mitigation)

person_publication_confidence: (high | medium | low)

graph_inclusion_reason: (why include_in_graph: true or false on the person–publication link — e.g., verified authorship + hard-tech relevance; or registry-only weak fit)

Resource map connection (required for inclusion)

Relevance to resource map (1–2 sentences: why this publication belongs in the hard-tech map):

Related resource_id (if any):

Relationship (uses | acknowledges | produced_by | documents | demonstrates_capability | related_topic | unclear):

resource_link_allowed: (true | false)

resource_link_evidence_level: (explicit_in_publication | explicit_on_lab_page | explicit_in_news | none | needs_review)

reason_resource_link_not_added: (required when resource_link_allowed: false — e.g., no facility acknowledgment in abstract/methods; authorship only; topical similarity only)

Evidence text (quote or paraphrase tying the publication to the resource — methods, acknowledgments, data availability, facility name):

Evidence file in repo (e.g. lab page PDF path, grant export, resource markdown):

Evidence URL (official DePaul or publisher link already cited in repo):

Topics

Quality / ambiguity

Confidence: (high | medium | low)

Author-name ambiguity notes (homonyms, name changes, missing middle initial):

Affiliation notes (pre-DePaul work, external lab, student graduated):

Coauthorship vs collaboration notes (coauthors do not imply shared facility use):

After intake

  1. Add the publication to data/publications.yaml (PUB-###).
  2. Add rows to data/person_publication_links.yaml for each DePaul author with explicit authorship evidence.
  3. Add rows to data/publication_resource_links.yaml only when resource_link_allowed: true and evidence meets publication-intake-rules.md § Allowed publication–resource evidence.
  4. Regenerate graph exports:
python3 scripts/refresh_all.py

Rules reminder

  • Do not add publications for general bibliography completeness.
  • Do not link resources on topical similarity alone.
  • Do not treat coauthorship as facility collaboration.
  • Do not infer resource use from authorship, center membership, or profile method lists.
  • Grant abstracts may guide searches but are not resource-use evidence unless explicit.
  • Publication–resource links should be rare and high-confidence; default is person–publication only.
  • Do not scrape external indexes in manual intake without recording the evidence source.