Library and references

Personal library and project references

Your Library is private: papers you collect across projects. A project's References tab lists the works that belong to that project. Adding a paper to a project from your library links the same canonical record; nothing is copied.

Adding papers

• Import RIS, BibTeX, NBIB, EndNote XML or CSV; duplicates are merged by DOI, PMID and title.
• Paste DOIs or PubMed IDs; metadata is fetched from the backbone sources.
• Add manually when a record has no identifier (grey literature, reports).
• Search on the Sources tab and add results to the project directly.

Tags, collections and smart collections

Tag freely; group into collections; smart collections update themselves from a saved filter (for example “tag = pending AND year ≥ 2020”). Notes attach to a work and travel with it into every project.

Reading and annotating

Open a PDF in the reader to highlight, comment and extract evidence anchored to the page. Annotations belong to you or to the project depending on where you opened the paper.

Export

Export any selection as RIS, BibTeX or CSV, or a formatted bibliography in Vancouver, AMA, APA, NEJM, Lancet, BMJ, Nature or Chicago.

Retractions and corrections

Hikma re-asks Crossref, OpenAlex and PubMed about your papers on a schedule (daily by default) and records four kinds of notice separately: retracted, superseded by another version, an expression of concern, and a published correction. Each one is stored with the source that said so, the DOI of the notice, and the time it was read — so a work with no badge is one that was checked, not one nobody looked at. The project's Sources tab lists both, including how many works have never been checked.

A notice propagates. Evidence units taken from that work become superseded: they no longer bind a number in any manuscript, the claims resting on them are marked, and cached readings of the paper drop out of the packets the assistant writes from. A bound number whose source was retracted or superseded is the error NUM_RETRACTED_SOURCE; a concern or a correction is the warning NUM_CONCERN_SOURCE; a citation to such a work is CIT_RETRACTED or CIT_CONCERN. Any release candidate built on the work goes stale and must be rebuilt.

Files you have already exported and packages you have already sent are never changed or resubmitted. Instead the affected version is recorded and named — the candidate, the filename and its sha256, the journal and the manuscript number — together with the action you have to take: contact the journal, issue a correction to whoever received the file, or rebuild the candidate. You are notified, and the record stays in the submission's timeline.