Skip to content

DePaul Resource Map — ORS demo (one page)

Date: June 2026 · Contact: Resource map maintainers · Detail: ors-demo-readiness.md

Purpose

Give Research Services and college partners a shared, evidence-backed view of DePaul’s hard-tech facilities, equipment, and the people, grants, and outputs that connect to them — without over-interpreting affiliation or co-authorship as facility use.

Current prototype status
Resources 265 total (78 facilities/programs/partners + 187 catalog courses)
People 115 named individuals with cited roles
Grants 33 seed records (internal CSV + documented programs)
Publications / outputs 34 / 18 evidence objects (conservative resource links)
Equipment 345 line items on 51 resources
Public site Unit indexes, resource pages, equipment & curriculum catalogs — no public People/Grants/Pubs/Outputs directories
Graph CSV exports; Neo4j import not started

Pipeline: editable YAML registries → python3 scripts/refresh_all.py → MkDocs + graph CSVs.

Why this matters for research & innovation

  • Surfaces cross-college capacity (CDM, CSH, Music, Theatre, university centers, external partners) in one ID system.
  • Supports ORS, college research offices, and cores answering “who uses our space/instrument?” with citations.
  • Separates facilities inventory from evidence of use (grants, papers, productions, installations).
  • Builds discipline for a future institutional graph — with explicit rules against false hubs and affiliation-only edges.

Current data layers

  1. Resources — access, verification, equipment, documented relationships
  2. People — directors, PIs, faculty/staff links to resources
  3. Grants — awards with person links; sparse grant–resource edges today
  4. Publications — peer-reviewed layer; facility links rare by design
  5. Outputs — games, films, SPARK/IRL projects, theatre-tech targets (still sparse)
  6. Equipment — taxonomy-tagged lists per resource

Why internal data matters

Public websites and a partial grants CSV cannot supply:

  • Proposal facilities / instrumentation narratives
  • Co-PIs, award dates, amounts, and status
  • Purchasing history tied to grants and rooms

ORS + purchasing exports would turn the map from a curated snapshot into a maintainable research-infrastructure graph with governance flags for public display.

Proposed next step

Pilot: One ORS export cycle + facilities-text excerpts + permission flags; optional purchasing slice for 3 PI accounts. Joint review of 10–15 grant–resource edges, then automated refresh. See internal-data-wishlist.md.

Demo: ors-demo-script.md (~6 min).