Skip to content
Published studies are shown for demonstration purposes, not because they are good or bad research. Demonstrator · items marked Example are invented · what exists today
Search

Publish your research

Your files stay where they are, on your computer or in your GitHub repository. Publishing adds a public page that says what the research is, who made it, what it builds on and what e2er checked.

This page publishes in the browser. From the command line, e2er publish --to https://e2er.org does the same; Get started describes it, from the run to the published study.

Web publishing runs on e2er.orgChecks and publishing work from the command lineThis walk-through is an example
  1. 1 · Sign in

    With GitHub, where your research files live, or with ORCID, your researcher iD. You can link both to one profile.

  2. 2 · Choose your research

    Pick the folder that e2er export wrote after your run. It holds the paper, results, code and a list of every file with its fingerprint.

  3. 3 · e2er checks it

    e2er opens every file and compares it with the fingerprint recorded when the research was produced. Anything changed afterwards shows up here.

  4. 4 · Add details

    Templates, specialists, skills and datasets the run used are filled in from its records, so their authors are credited automatically.

  5. 5 · Published

    ✓ Your research has a public page

    In the real flow it would appear at e2er.org/…. See how the published showcase looks.

For developers: what happens behind the page

e2er publish verifies the exported folder and writes its description, e2er.json, and the dossier. This page and e2er publish --to send the same request: the description, the dossier and the fingerprint of every file. Format of e2er.json.