Publish and record your research

On this page

Use this guide when a draft is ready for human review. Keep the project's evidence, limits, and contribution credit with the draft.

1. Choose a route#

Choose an audience and an output type. Check the destination's current instructions before preparing files.

OSRI prioritizes free submission and a free publication route. Start with the venue directory, then confirm scope, article type, submission availability, author eligibility, and the conditions that keep the chosen route free. Check submission fees, publication fees, page charges, compulsory membership, and conference registration separately. Keep waivers and institutional agreements conditional until eligibility is established.

Output Next action
Research blog or technical essay Choose a public site or repository page. Include the question, sources or methods, findings, and limits.
Preprint Choose a repository that covers the subject. Follow its submission, file, and license instructions.
Journal article or full conference paper Choose a venue that fits the work. Check its author instructions, review process, deadlines, fees, and preprint policy.

For arXiv, use the submission guide. New authors or categories may need endorsement. Moderation does not establish peer review.

Ask for venue or methods help in Q&A. Ask a maintainer for help with submission files or an archive. No paid plugin is required. Get the responsible person's authorization before incurring a cost.

2. Prepare the files#

Follow the destination's checklist. Prepare the text, references, figures, and supporting files it requires. Keep editable sources in the project.

Link material claims to their evidence. Include methods, failed checks, uncertainty, limitations, contribution credit, and material agent assistance. Share only material you may distribute. Describe access to restricted inputs without uploading them.

3. Record human review and the decision#

Ask a person to check the evidence, methods, interpretation, limits, and credit. Seek the domain and methods expertise the claims need.

Record the reviewer, findings, changes, and review still needed in a project issue or pull request. Agent checks do not establish independent human review.

Have the authors confirm the version and credit under the venue's rules. Record the human lead's publication authorization for that version. Repository acceptance and external peer review are separate decisions.

4. Submit or publish#

The responsible author submits the files on the destination's official site. They check the submission preview. A blog author publishes the reviewed page on the selected site.

Record the submitted version and date in the project. Record the exact supporting repository commit or release. Ask a maintainer to identify that version if you need help. Keep private submission details in an agreed private record. Submission does not mean acceptance or publication.

5. Address the response#

For requested revisions, record each comment, response, and changed passage. Repeat the affected checks and human review. Obtain authorization for the revised submission.

If the work is declined, record the outcome. Discuss revisions or another venue with the authors. Follow the venue's rules before making another submission.

6. Preserve the public version#

When the work becomes public, keep its stable link and the exact supporting repository commit or release. Record the public date and reuse terms.

For an optional archive, follow the Zenodo upload guide. Upload only permitted files, describe the record, choose its terms and visibility, and check the preview before publishing. A reserved digital object identifier (DOI) becomes registered when the record is published. An archive deposit does not establish peer review.

7. Add the OSRI record#

Share the public link in Show and tell. Include the project, output type, public date, authors, peer-review status, and supporting repository version.

Ask a maintainer to complete the publication register. Link related outputs from the same research work. Keep revised versions in the existing output record. Report accepted work awaiting public release as pipeline work.

View source on GitHub