What ORS and Purchasing Data Would Unlock
Action-oriented ask for a bounded pilot export. Extended field notes: internal-data-wishlist (full report).
The ask
A pilot data export from ORS and purchasing for a bounded subset—enough to strengthen grant–resource links, equipment visibility, and proposal-support answers without exposing restricted fields on the public site.
ORS data needed
- Proposal title
- PI/co-PIs
- Units
- Funder/program
- Status
- Dates
- Abstract
- Facilities/resources section
- Equipment/instrumentation section
- Collaborators
- Display permission: public / internal / restricted
Purchasing data needed
- Item description
- Vendor
- Purchase date
- Cost or cost range
- Unit/account/project
- Responsible person or PI
- Funding source
- Building/room if available
- Display permission
Suggested pilot
- 2 to 3 years of records
- Proposals mentioning facilities, labs, studios, makerspaces, equipment, sensors, imaging, computing, visualization, fabrication, or production technology
- Equipment purchases above a reasonable threshold
- Internal-only graph analysis first
Why it matters
- Better proposal support
- Better facility discovery
- Better equipment visibility
- Better collaboration discovery
- Less dependence on individual memory
- Stronger evidence for shared infrastructure
Demo: Ask the Map · Connection Examples · Update Workflow · Internal Data Wishlist
Last generated: 2026-06-01 17:38 UTC