University & Institutional Research Exchange
Bring a research question with a defined scope and an honest account of what is not yet known. This exchange accepts proposals and source-linked work for review, not instant publication or an implied institutional partnership.
Possible project shapes
Dataset review can document units, coverage, missing fields, reuse rights, and definitions. Public-record verification can connect a claim to an issuer, version, date, and procedural status. Source discovery can identify the record still needed to answer a question.
Methods and data documentation can explain a transformation or comparison. Local and regional research can test whether a general statement applies to a named place. Research translation can make a narrow finding understandable without removing its limits. These are proposal categories, not currently funded or staffed projects.
A proposal another team can evaluate
Include the question, geography, timeframe, source plan, proposed methods, anticipated output, contributor roles, relevant interests, and limitations. For student or capstone work, identify supervision and what the institution has actually authorized.
For community-engaged research, describe who helped define the question and what participation or reuse consent exists. Do not assume consent, shared priorities, data access, or authority to speak for another institution. This intake does not replace institutional review.
Where reviewed work goes
Proposals enter the contribution queue under the research type. A reviewer can ask for clarification before approving a source record. Approved organizations can then propose regional associations or collections of already-public resources.
The dashboard shows workflow status and reviewer feedback. A public collection preserves source-level attribution and evidence labels. No research proposal, contribution approval, or organization membership grants article publication rights.
What approval does and does not mean
Participation is not endorsement of this project, any organization, or data-center development. Institutions may submit evidence and context, but they cannot execute or publish Team_Compute articles. Article publishing remains owner-only.
Applications, source submissions, regional associations, events, and resource collections have separate review states. A received request is not an approved relationship. An approved workflow state is not a measure of evidence quality. Public material retains its issuer, date, geography, limitations, review context, and a correction route.