DePaul Hardware Technology Resource Map

679 public map objects — 102 facilities/programs/partners/services, 454 catalog courses, 123 people.

Grant records (922) are maintained in the internal registry and graph but are not counted in public Resource Map totals.

By ownership prefix

Prefix	Unit	Count
CDM	Jarvis CDM	31
CSH	College of Science and Health	21
COM	College of Communication	2
UNI	University & engagement	16
EXT	External partners	20
ART	Art School	5
MUS	School of Music	4
TTS	Theatre School	3
CUR	Curriculum (courses)	454
PER	People (registry)	123
Total		679

By content type

Content type	Count
course	454
infrastructure	29
center	31
partnership	22
curriculum	7
service	3
program	1
unknown	123
clinic	1
laboratory	8
Total	679

Catalog cross-links

Documented course ↔ facility links: 186
Documented facility ↔ facility links: 3
Equipment categories in use (non-course YAML): 74

Ownership Files

units/cdm.md - Jarvis College of Computing and Digital Media
units/csh.md - College of Science and Health
units/music.md - School of Music
units/theatre-school.md - The Theatre School
units/art-school.md - Art School (in LAS)
units/communication.md - College of Communication
units/university-and-external-engagement.md - University-level and cross-unit innovation/engagement entities
units/external-partners.md - External organizations (research, community, venture, and national-lab partners)
resources/<PREFIX>/<RESOURCE_ID>.md - Detail pages per resource (full metadata + linked relationship IDs)
equipment-index.md - Equipment-first catalog (categories → resources); generated from data/resource_equipment.yaml
curriculum-index.md - Hardware-related coursework by academic unit; generated from data/resource_courses.yaml
people-index.md - Named faculty, staff, and research contacts; generated from data/people.yaml and link registries
grants-index.md - Grant and award catalog; generated from data/grants.yaml and link registries
resources/CUR/*.md - Course resource pages (resource_type: course)
resources/PER/*.md - Person hub pages (person_id from data/people.yaml)
resources/GRA/*.md - Grant detail pages (grant_id from data/grants.yaml)
data/resource_courses.yaml - Course catalog metadata (source of truth)
data/course_resource_links.yaml - Documented course↔facility links only (with source URLs)
data/equipment_taxonomy.yaml - Broad categories and search synonyms
data/resource_equipment.yaml - Equipment lists per resource (source of truth)
data/resource_access.yaml - Access classification per resource (source of truth)
data/resource_verification.yaml - Activity verification estimate per resource (source of truth)
docs/reports/access-status-review.md - Generated review of unknown/weak access records
docs/reports/verification-review.md - Generated review of low-confidence or stale resources
docs/reports/curriculum-review.md - Included/excluded courses and ambiguous candidates from catalog harvest
scripts/generate_home_stats.py - Refreshes the resource tally on this Home page

Reference documents (local `data/`)

Grant proposals and similar working sources used for verification may be stored under data/ alongside the YAML catalogs. These files are local only (not committed to GitHub) and are not copied into docs/ or published with the MkDocs site.

Field Standard

All split files use the same table fields:

Field	Purpose
Resource ID	Stable identifier for tracking, dedupe, and database-style updates
Resource	Resource/program/facility name
Owner Unit	Canonical administrative owner (unit-level; no person names)
Sub-unit	Department/office/program under owner unit
Content Type	`infrastructure`, `laboratory`, `center`, `clinic`, `curriculum`, `program`, `service`, `partnership` (see Content type definitions below)
Campus/Location	Loop, Lincoln Park, Cinespace, Off-campus, Multi-campus
Description & capabilities	What it does and key capabilities
Contacts (resource-level)	Office email, contact page, or individual resource contacts if public and useful
Equipment	Broad category (searchable) and specific sub-types; see `equipment-index.md` and each resource’s Equipment section
Access status	`green` / `yellow` / `red` / `unknown` with rationale, access URL, contacts, and source URLs (see `data/resource_access.yaml`)
Verification	`confirmed` / `likely` / `needs_review` / `archived` with confidence score, evidence list, and rationale (see `data/resource_verification.yaml`)
URL	Official source page
Last Verified	Last verification date in this project
Documented Relationships	Explicit, evidence-backed relationships
Notes	Distinction notes, caveats, and verification flags

Content type definitions

Use the narrowest type the evidence supports:

Content type	Use for
`laboratory`	A faculty-led or research-group lab (a specific PI's or small team's research lab).
`center`	A broader organizational unit — center, institute, or multi-project / multi-lab hub.
`clinic`	A service-learning, public-service, or client-facing applied unit.
`infrastructure`	A shared technical platform, facility, space, equipment-support resource, or access platform.
`curriculum`	Academic program or coursework grouping (see also the `CUR` course prefix).
`program`	A standing programmatic initiative that is not primarily a physical facility.
`service`	A support service offered to users.
`partnership`	An external or cross-institution partnership entry (typical for `EXT`).

Legacy classifications: Earlier entries may use a broader type (for example, a single-PI lab classified as center) than these definitions would now suggest. These legacy classifications are intentional history and should not be silently changed during ordinary intake. Reclassification should happen only in a separate, evidence-backed refactor that is recorded in a report — not as a side effect of unrelated edits.

Naming and Contact Policy

Use unit and role names for ownership metadata where possible; named individuals are encouraged in the people registry (data/people.yaml) when publicly documented.
Individual names are allowed as resource-level contacts, principal investigators (PIs), lab/center directors, and documented collaborators where operationally useful and publicly listed.
The people registry may cite official DePaul pages, resource websites, grant records, and targeted web search when a resource site does not list a contact name.
Prefer office or unit contact channels over individuals for day-to-day access on resource pages when both are available; still record named PIs and directors in data/people.yaml when identified.
Site display: named contacts from the registry appear on resource pages when people_contacts.enabled is true in data/site_display.yaml; set to false to hide them for a public release build. Explicit person–resource edges for graph export live in data/person_resource_links.yaml. Person hub pages (resources/PER/*.md, browsable via people-index.md) list linked resources, grants, courses, and publications for each named individual.
Interdisciplinary centers/institutes default to units/university-and-external-engagement.md, with academic-unit cross-references in Documented Relationships and Notes.
External organizations (not DePaul-owned) default to units/external-partners.md with the EXT prefix. List collaborative documents (MOUs, agreements, contracts, user-facility allocations) when publicly documented; mark undocumented agreements explicitly.

External partner page standard

Partner detail pages (resources/EXT/*.md) include:

Section	Purpose
Organization	What the external entity is
Relationship to DePaul	How DePaul connects (user facility, funder, incubator member, community partner, etc.)
Known collaborations & connections	Projects, units, and resource IDs
Collaborative documents	Table of MOUs, agreements, grants, or access mechanisms with public source or “not publicly documented”

Resource ID Governance

Prefix by ownership file: CDM, CSH, COM, MUS, TTS, ART, UNI, EXT, plus catalog prefixes CUR (courses), PER (people), GRA (grants).
COM — College of Communication (units/communication.md).
CUR — catalog courses (curriculum-index.md); not listed in ownership unit tables.
PER — people hub pages (people-index.md); generated from data/people.yaml.
GRA — grant pages (grants-index.md); generated from data/grants.yaml.
Curriculum prefix: CUR — one resource per catalog course (see data/resource_courses.yaml); not listed in ownership unit tables.
Format: <PREFIX>-<3 digit number> (example: CSH-008).
Create IDs sequentially: assign the next highest number within that ownership file.
Never reuse IDs: once assigned, an ID is permanent, even if the resource is removed.
Retired resources: keep the ID in history/logs with status removed or archived; do not reassign.
Cross-references: use the canonical ID from the owning file when mentioned elsewhere.
Moves between owners: keep the original ID in notes/history and assign a new ID in the new owner file, with cross-reference to prior ID.

New Entry Checklist

Determine the owning file by administrative unit (or UNI for interdisciplinary/unspecified ownership).
Assign the next sequential resource_id for that file prefix.
Complete all required columns, especially URL, Last Verified, and Documented Relationships.
Apply naming policy (no leadership person names in ownership metadata; resource-level contacts only).
Add any needed cross-references in related unit files using the canonical resource_id.