Home / Science / Research toolkit / Data management / Dataset README builderTool #819

Dataset README builder: write a FAIR README for research data, with licence, files and variables, as Markdown or text

Fill in a form and get a README for your dataset: authors, description, licence, citation, a file list (pick the files to add their names and sizes), methods and a table of variables. Live preview, a checklist of what is missing, and Markdown or plain-text downloads.

Keep it one tap away for everyday use.

Bookmark Dataset README builder?

Press Ctrl + D now. Your browser opens its own bookmark box, where you choose the name and folder.

  1. Fill in
  2. Files
  3. Preview
  4. README
Nothing is uploadedWorks offline once open

Your dataset

What you type stays on this page and is not saved; download the README before you leave. The example is made up.

General information

Name; ORCID iD; affiliation; email. Leave a part empty with nothing between the semicolons.

Sharing and access

Files

Only the names and sizes of the files you pick are used; the files are not opened or uploaded. Lines become "name | size in bytes | description"; write each description after the last bar.

Methods

Variables

Checklist

      README

      Markdown shows as formatted text on GitHub, GitLab, Zenodo and most repositories. The plain text version opens anywhere.

      What it does

      A README is the first file people open in a dataset. A good one lets someone who has never met you understand the data, use it correctly and cite it, years from now. That is what the FAIR principles ask for: data that are Findable, Accessible, Interoperable and Reusable. This page builds that README from a form:

      • General information: title, authors with ORCID iDs and affiliations, a contact, a description, when and where the data were collected, keywords and funding.
      • Sharing and access: a licence chosen from the common open licences (with a one-line explanation of each), restrictions, DOI, version and a recommended citation written for you.
      • Files: a table of file names, sizes and descriptions. Pick the files from your device to add their names and sizes; only those two facts are read.
      • Methods: how the data were collected and processed, instruments and software, and quality checks.
      • Variables: a table of column names, descriptions, units and missing-value codes.

      How to use it

      1. Fill in what you can. Every part is optional, and empty parts are left out of the README.
      2. Authors go one per line as Name; ORCID iD; affiliation; email.
      3. Under Files, press Add files from your device or Add a folder. Each file becomes a line name | size | with room for a description after the last bar. Picking again keeps the descriptions you wrote.
      4. Variables go one per line as name | description | unit | missing value code.
      5. Watch the Checklist: it counts the 12 parts a reader most needs (title, authors, ORCID iDs, contact, description, dates, licence, identifier or citation, file list, methods, variables and missing-value codes) and lists mistakes such as an ORCID iD with a wrong check digit, a date that is not YYYY-MM-DD, or an end date before the start.
      6. Switch between Preview, Markdown and Plain text, then download README.md or README.txt, or copy it.

      Worked example

      The page opens with a made-up example: three temperature loggers in a stream. The checklist reads 11 of 12 parts filled in: the second author has no ORCID iD. The file table lists site-a.csv at 41.3 kB (41,250 bytes), and below it “3 files, 122 kB in all”. With no citation typed, the page writes one from the fields:

      Rivera, A. & Okafor, C. (2026). Stream temperature at three sites, spring 2026 (example) (Version 1.0) [Data set]. Example Data Repository. https://doi.org/10.5555/example.2026

      Type a wrong last digit into Ana Rivera’s ORCID iD, and the checklist adds “1 to fix” with the reason.

      Tips

      • Put the README next to your data files, and send it with every copy. Markdown shows as formatted text on GitHub, GitLab, Zenodo and many repositories; plain text opens everywhere.
      • Name the unit of every numeric column, and say what an empty cell or a code such as -999 means.
      • Pair it with a checksum manifest (from the checksum checker) and a metadata record (from the metadata builder) when you deposit data.

      FAQ

      Is anything uploaded or saved? No. The form stays on this page, and picked files are not opened: only their names and sizes are read. Nothing is kept after you close the page, so download the README first.

      Which licence should I choose? Many funders and repositories ask for CC BY 4.0 or CC0 for research data. Each choice shows one line on what it allows. When in doubt, ask your repository or library.

      Can I edit the README afterwards? Yes, it is a plain text file. Open it in any text editor.

      Where the numbers come from

      • The section order follows the widely used readme-style metadata layout for research data (general information, sharing and access, data and file overview, methods, data-specific information), as recommended by university research data services. Wording is fibub's own.
      • Licences are named by their SPDX identifiers; the citation follows the order DataCite recommends (creator, year, title, version, publisher, identifier).
      • Markdown output checked in the tests with markdown-it-py (CommonMark with tables).
      • The example is made up. Picked files give only their names and sizes; they are not opened, uploaded or stored.

      Standard scientific values, such as constants, atomic weights and melting points, are facts found in every textbook; we name where ours were checked. If you are an author or publisher and want a value, a credit or a table changed or removed, tell us and we will act quickly.

      Last updated 2026-11-09.

      Related tools

      Science file converter #815 Open a NetCDF classic or 64-bit offset file, a FITS image or table, or a CSV or Excel sheet, see every dimension, variable and attribute, and export one variable or table to CSV or JSON. Scale factors and fill values are handled. The file stays in your browser. Metadata builder #816 Fill in a form for DataCite 4.5, Dublin Core or a Darwin Core occurrence, and get a checked record: required fields, ISO 8601 dates, ORCID iD check digits, DOI form and coordinate ranges. Download it as XML, JSON or CSV. Checksum checker #818 Make SHA-256, SHA-512, SHA-1, MD5 or CRC32 checksums for a whole folder of files, save them as a sha256sum, BSD or BagIt manifest, and check files against a manifest you were given: match, does not match, missing or extra. Nothing is uploaded. Data dictionary generator #817 Open a CSV or Excel file and get a data dictionary: each column's type, missing values, distinct values, range, mean, SD and median, examples and allowed values. Add titles, descriptions and units, then export Markdown, CSV or a Frictionless Table Schema (JSON). The file stays in your browser. 1D Schrödinger solver #923 Choose a textbook potential, type a formula or draw your own, and get the lowest energy levels and wavefunctions of the one-dimensional Schrödinger equation by the matrix (finite-difference) method, with the exact levels alongside for the box, harmonic oscillator, finite well, Morse, linear and Pöschl–Teller potentials. Adduct and neutral loss calculator #984 Type a formula or a neutral monoisotopic mass and get the m/z of 25 common electrospray adducts in positive and negative mode, the ions left after common neutral losses (water, ammonia, CO2, sugars, phosphate and your own), and match a list of observed m/z values within a ppm tolerance. With no molecule, it turns observed m/z values into candidate neutral masses.