Interpretation limit
A current file can differ from the earlier method. Registration alone does not establish adherence to the plan.
Public sources / INT
Consult OSF projects, preregistrations and preprints, identifying resource type and version. The announced Projects transition starts on 16 November 2026; see the documented schedule in the profile.

AI-generated illustration
Read this source in practice
OSF distinguishes Projects from Registrations. The announced Projects transition does not replace the registered plan or the history of declared updates: read these objects separately.
Schedule announced by the service, consulted on the stated date. It is not an observation that the changes have been implemented.
On a small screen, scroll the table horizontally to read all columns.
| Announced date | Announced change | Scope |
|---|---|---|
| 2026-11-16 | No new Projects or Components. | Registrations and Preprints keep their separate workflows. |
| 2027-02-19 | Projects and Components become read-only. | Existing content remains accessible under its permissions, according to the announcement. |
A current file can differ from the earlier method. Registration alone does not establish adherence to the plan.
Dated plan, chronology, versions, declared changes and examined analysis.
Consulted reference : OSF — Projects Transition · OSF — Registrations and preregistrations · OSF — Registration Questions and Use Cases · Consulted on
Updated on :
Compare files, version, licence and depositor. A deposit does not establish peer review or reproducibility.
Consult OSF projects, preregistrations and preprints, identifying resource type and version. The announced Projects transition starts on 16 November 2026; see the documented schedule in the profile.
Distinguish a project file from a Registration. Announced preservation of content and identifiers establishes neither protocol adherence nor result quality.
Project or registration identifier, type, date, files and consulted version.
Separate planned protocol from execution; record deviations reported in the published result.
Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.
Identify the relevant registration, record its date and compare objectives, criteria and population with the results document.
Not every study uses these registries; an unsuccessful search is not universal evidence of absence.
Compare sourcesInspect the exact resource and its terms. Being viewable does not authorise redistribution; retain the resource licence and restrictions instead of inferring them from the portal.
Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.
The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.
No. A DOI identifies an object. Check document type, journal, version and editorial process; datasets, preprints and reports can also have DOIs.
Retain record identifier, version, file and access date. Check links to other repositories; several hosts of one work do not become independent works.
Read a data catalogue record and choose the right resourceDEEPER READING / PRACTICE
A list indicates where to look for and what limits to keep in mind. It helps to prepare a consultation but does not replace the reading of the obtained document.
Updated on .
Select a precise question, open the source and raise the request, result and date. Compare the possibilities announced with the information actually available at the time of the consultation.
The availability of a service and its content may vary. The directory does not turn an absent, partial or ambiguous result into a definitive response.
The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.