Help
Guides to every part of OSCR: finding papers and their code, reading them side by side, and, for authors and maintainers, correcting, validating and citing their records. No account is needed to read anything; signing in is only for contributing, and asks for no email address.
Authors and maintainers: add your paper's badge to its code's README in one line. Make it, or read the badge's guide.
Finding and reading
- How the code is found and verified
- Where a paper's code links come from, how each is classified as code, data or a tool, the visit at the source, and what "code verified" means.
- Searching and the DOI lookup
- The search form, its fields and filters, the query language, exports, the daily quota; and the DOI lookup.
- Reading a paper's page
- Its sections, the statuses and verdicts in words, the levels of evidence, and what an older paper's page leaves out.
- The Code ↔ Paper reader
- The paper and its authors' code side by side: matches, colours, weak matches, hiding the paper, the file tools.
- Tracing maps
- What a map holds, how it is proposed, and what changes once an author validates it.
Your account
- Signing in and your account
- ORCID, GitHub or Google, no email address; roles; sessions; the account page and its notifications.
Contributing
- Submitting a paper
- A DOI and its code links: the checks, the draft, and publication.
- Correcting a record's links
- Adding, removing or re-labelling a paper's code and data links, as a verified author or a maintainer.
- Claiming authorship
- When your ORCID iD is on the paper, and when it is not.
- Validating a map and its DOI
- What a validation checks, the deposit on Zenodo, and what the DOI covers.
- The badge
- Add a paper's badge to a README, a Hugging Face card, GitLab, a web page or a poster: every snippet, every option, every repository at once.
- Requesting a removal
- What can be removed, who may ask, how the rules decide a request, and when a decision takes effect.
Data, tools and questions
- Accessing the data
- The datasets on Hugging Face, their licences, and what stays private.
- The public API
- The free, keyless read API: every endpoint with an example in curl, Python and R, bulk downloads, rates and citation.
- The command line (oscr)
- The free oscr tool for researchers: install, sign in, check, cite and trace your code, and work with its GitHub repository from the terminal.
- Frequently asked questions
- Short answers to the questions readers and authors ask most.
Where to start
- Looking for a paper's code? Type its DOI, title or a word into the search box at the top of every page, or use the DOI lookup, which answers for every paper OSCR has read.
- Browsing? The home page lists the latest papers with code; every paper by date, the categories and the lists of authors, journals, institutions, tools and datasets list the rest.
- An author? Sign in with ORCID on your account page: the papers that list your ORCID iD appear there, and each one's page lets you correct it, validate its map and add the badge.
- Something wrong or unwanted? Correct it from the paper's page, or ask for its removal.