Skip to content

ORS demo script (5–7 minutes)

Live-demo outline for the DePaul Hardware Technology Resource Map.
Pre-read: ors-demo-one-page-summary.md · Backup detail: ors-demo-readiness.md

Suggested path: MkDocs site home → unit index → one resource page → mention data layers → full-refresh-report or local CSV exports.

1. Opening — what problem this solves (~45 sec)

Say:

DePaul’s hard-tech capacity is spread across colleges — makerspaces, cores, studios, theatres, partner labs — but it is hard to see who actually uses what and what evidence we have. This map is a conservative, citation-backed inventory plus relationship layers for grants, publications, and practice-based outputs. It is a prototype for research administration and innovation planning, not a finished enterprise system.

Do not claim: completeness, real-time ORS sync, or Neo4j production today.

2. Show resource inventory (~60 sec)

Navigate: Home (docs/index.md) → stats block (265 resources, 78 non-course) → one unit index (e.g., CDM or CSH).

Point out:

  • Stable IDs (CDM-001, CSH-001, …)
  • Access status (green / yellow / red)
  • Verification confidence
  • Equipment section on a detail page (e.g., Idea Realization Lab or Chemistry Core Instrumentation)

3. Show people / resource connections (~60 sec)

Navigate: Same resource page → People & contacts (if enabled).

Say:

Names come from official pages and documented grants — not scraped social profiles. Many edges are direct (director, faculty_lead); weaker affiliation edges are flagged. Grant PIs are often hidden on the public site but kept internally for audit.

Optional: Mention data/person_resource_links.yaml and include_in_graph for graph vs public display.

4. Grants, publications, outputs as evidence objects (~75 sec)

Say (no public tabs required):

Layer Count (approx.) Role
Grants 33 Seed awards; 8 graph-included grant–resource links where facilities text exists
Publications 34 Scholarly evidence; only 4 graph-included publication–resource links (high bar)
Outputs 18 Films, games, SPARK projects, IRL builds — 12 output–resource links

Examples to name:

  • Cinespace / Project Bluelight — explicit production facility text
  • SPARK civic viz — partner pages name SPARK Center
  • Publication–resource — e.g., APS beamline acknowledgment, Karver lab assay paper

Quality point: One person–output link excluded from graph (Plant digital twin / Wagner) while the SPARK output–resource edge remains — evidence evaluated separately.

5. Show equipment layer (~45 sec)

Navigate: Equipment Catalog (equipment-index.md).

Say:

345 line items across 51 resources — searchable by category (3D printers, NMR, sound reinforcement, etc.). Sourced from public facility pages today; purchasing data would add purchase date, grant linkage, and room.

6. Graph-readiness / edge safety (~60 sec)

Reference: graph-readiness-review.md or refresh report §6–§8.

Highlight:

  • 174 person–resource edges in graph vs 35 excluded
  • 25 grant PI links to UNI-001 — not a collaboration cluster (include_in_graph: false)
  • Hub monitoring: CDM-016 (Bluelight), CDM-001 (IRL), UNI-003 (SPARK)
  • Validation warnings are intentional (e.g., outputs without named people for IRL team projects)

7. Limitations of public data (~45 sec)

Say:

We built this from official web pages, a partial internal grants CSV, and manual review — not from full ORS or purchasing feeds. Most grants have no resource edge because abstracts in the export do not name labs. Theatre and music practice outputs are underrepresented because season pages do not name faculty on specific shows. We would rather leave gaps than invent edges from affiliation.

8. What ORS and purchasing would unlock (~60 sec)

Navigate or hand out: internal-data-wishlist.md

Top three unlocks:

  1. Facilities / equipment sections on proposals → grant–resource edges with quoted evidence
  2. PI / co-PI / dates / amounts → accurate person–grant graph and timelines
  3. Purchasing lines tied to grant codes → verify equipment on resource pages and close award→asset loop

9. Closing ask (~30 sec)

Ask:

Can ORS support a pilot export for one award cycle — proposal IDs, PI/co-PIs, statuses, dates, and facilities narrative excerpts with a display-permission flag? In parallel, could purchasing share a small equipment slice keyed by PI account and grant ID? We will review every edge before anything goes public.

Leave behind: ors-demo-one-page-summary.md

Demo checklist

  • [ ] Site builds locally (mkdocs serve from docs/)
  • [ ] Pick 2–3 resource pages rehearsed (CDM-001, UNI-003, CSH-001)
  • [ ] Latest full-refresh-report.md open for counts
  • [ ] Do not open unpublished proposal PDFs from data/ on screen unless cleared