Badges
The OSCR badge, in the README of a paper's code, on its Hugging Face card or on a lab's page, says what the registry knows of the paper and takes its readers to it: the paper beside the code, its tracing map, its citation. Give a DOI or a repository's address; the badge stays true by itself, since the registry draws it from its own records every night. The guide explains every option.
This repository is the code of several papers
The badge
Copy it
Its addresses
The paper's code
Each repository the registry links to the paper, and whether its README carries the badge already, read now from the forge by your browser. A link opens the README in the forge's own editor: paste the snippet under the title, and the forge offers to commit it, or to open a pull request when you cannot write to the repository. OSCR never writes to a repository and never asks for that permission.
Every repository at once
- A GitLab group (or a whole instance): one group badge reaches every project of the group. In the group's Settings, General, Badges, add a badge with these two addresses; GitLab fills in each project's path, and a project the registry does not know shows nothing.
- Link
https://openscicode.org/badge/repo/gitlab.com/%{project_path}- Badge image URL
https://openscicode.org/badge/repo/gitlab.com/%{project_path}.svg?missing=hide
- Your own clones: the researchers' command line writes the badge into a README and keeps it up to date, between two marks, without adding it twice:
oscr badge --writein the clone (the guide). - All your papers: signed in with your ORCID iD, your account page lists the papers you are a verified author of, each with its badge and the repositories that still lack it.
Without the registry's server
Where an SVG drawn on demand cannot go, the static images never change and need nothing from the server: /badge.svg and, for LaTeX, a word processor or an email, /badge.png. Link them to the paper's page yourself.
[](https://openscicode.org/badge/doi/10.1234/abcd)