Requesting research resources
On this page
Use this process to request resources you cannot access. Contributors can request articles, datasets, database queries, standards, software, or other research resources that they cannot access themselves. Cole or another assigned administrator may help through university access, a library service, a provider application, or an open alternative. A request does not promise availability or grant access rights.
Start with a short request#
Post in OSRI Q&A and title the discussion Resource request: [short title]. You can copy the public request template. Include a citation or public resource link, the project or research question, and what you need. A brief request is enough to begin; the administrator helps identify any missing details. If you cannot use Discussions, use the existing issue queue.
Post only information safe for a public discussion or issue. Keep restricted files, personal data, confidential research plans, private terms, and credentials out of the post and its attachments. An agreed task can be tracked in an issue linked to the discussion. The .github forum remains the shared public entry point.
Private requests#
For private coordination, email Cole. You can contact Cole directly without opening a public discussion or issue. If you use a public post, do not name sensitive resources or projects in it. Agree on a delivery method and controlled storage before sending restricted material. After agreeing on the private method, you can use the private request template. Do not send credentials.
Administrator workflow#
Assign one human resource administrator to each request. That person records the status, next action, and next update date. They remain responsible when a librarian or provider is consulted. Public updates contain only safe metadata. Keep confidential checks and delivery details in the agreed private record.
| Status | Action and record |
|---|---|
| Submitted | Log the request and acknowledge its scope. |
| Triaged | Name the administrator; clarify the intended use, users, needed version or subset, timing, and any cost. Check for a suitable open alternative. |
| Access check | Check the actual resource terms and institutional eligibility for the requested use. Resolve unclear conditions with the library, provider, or data custodian. Record the approved users, tools, storage, transfer, analysis, and output conditions that apply. |
| Fulfilled or alternative supplied | Supply a permitted copy or extract, or arrange approved direct access. Alternatively, run an approved query or analysis and deliver permitted outputs. Record the version, provenance, delivery date, and relevant limits. Identify an alternative as an alternative. |
| Closed | Confirm receipt or record the outcome and remaining research limitation. Record any continuing retention, expiry, deletion, or reporting obligation and who owns it. |
Unclear terms remain an access check with a next action. Use denied only when applicable terms or an actual provider decision rule out the requested access or use. If the resource cannot be obtained, record unavailable and the checks made; do not describe uncertainty as a prohibition. A requester may also withdraw a request.
Match access to the intended use#
University authentication establishes a user's access route; it does not by itself authorize redistribution to OSRI collaborators. The administrator checks whether the recipient and proposed use are covered, including extracts and derived outputs. Never share credentials or bypass login controls. Do not assume a subscription permits bulk export, automated retrieval, or text mining. Do not assume it permits sending restricted material to agents or external services. Record permission for the planned tools and services before supplying material to them.
Controlled datasets may require a data-use agreement, named users, training or other approvals, secure analysis, and review of exports. The administrator arranges the applicable requirements and an approved delivery method. When files cannot move, approved analysis where the data reside can be useful. Obtain authorization before incurring a cost. Keep permitted public methods, citations, and access instructions in the project even when the underlying material remains restricted.
Terms vary by resource and institution. For example, CMU Libraries' use policy distinguishes licensed access, downloads, redistribution, mining, and AI uploads. The NIH dbGaP Data Use Certification ties controlled data to approved users, research, and security conditions. These examples do not determine another institution's permissions. Even freely readable articles have article-specific reuse terms; check the license, as the PMC copyright notice explains.
Look for a suitable licensed open dataset, author manuscript, preprint, repository copy, or author-provided material. An alternative must fit the question. Record a different article version or dataset. Institutional resources remain useful when the approved access and use fit the research.