Propose a paper for the atlas.

These are the fields most records in the index lack. If you are an author, you know them and the paper's readers do not.

Bills of materials, build instructions and design files often sit in the supplementary information rather than the article. List each item here; a curator reads them when validating the record. Link to a deposit or the publisher's page where you can. Files you hold only locally can be dragged into the Supplementary files box of the GitHub issue once it opens (25 MB per file, and they become public with the issue).

1. What it holds…Bill of materialsCAD or design filesBuild instructionsProtocolSoftware or firmwareSupplementary figures and methodsDataOther×

The five measurements a laboratory needs before adopting a build. Give the value the paper states and where it states it; leave a row blank if the paper does not report it. Only 8 of the 60 records report against a written standard, so name the standard if one was used.

Every record is scored 1–5 on the same ten criteria by a curator reading the paper. You can propose scores here; they are filed as submitter proposals and appear on the site only after a curator has checked them against the paper. Pick the anchor that fits and say what in the paper supports it.

1. ResolutionHow small or precise can this technology achieve?
   12345Clear

   Choose a score to see its anchor.

2. ThroughputHow scalable is the method from low device production to high-throughput biofabrication?
   12345Clear

   Choose a score to see its anchor.

3. Parts sourcingHow many components are off-the-shelf versus custom-made, and how complex is it to source and build them?
   12345Clear

   Choose a score to see its anchor.

4. Skill neededHow broad or specialized are the skills needed to build and use the technology?
   12345Clear

   Choose a score to see its anchor.

5. Equipment accessHow accessible are the equipment, consumables, technology, and facilities required to build and use this tool?
   12345Clear

   Choose a score to see its anchor.

6. Application rangeIs the technology general-purpose for many applications in the space, or was it designed for a narrow use case? Not shown on the site yet: the corpus has too few scores to compare.
   12345Clear

   Choose a score to see its anchor.

7. DocumentationHow complete is the documentation for building and using the tool?
   12345Clear

   Choose a score to see its anchor.

8. Validation effortHow well validated is the technology, and how easy is it to validate once built?
   12345Clear

   Choose a score to see its anchor.

9. Cycle timeHow fast does the method generate usable parts or the intended outcome once built, compared with traditional or alternative tools?
   12345Clear

   Choose a score to see its anchor.

10. Build timeHow quickly can the device or method be set up? This category contributes to scalability, although fast setup does not necessarily imply scalable large-batch manufacturing. Not shown on the site yet: the corpus has too few scores to compare.
    12345Clear

    Choose a score to see its anchor.

This is the text the GitHub issue will carry. Go back to any step to change it.

Opening the issue sends the draft above to GitHub. Until then it is kept only in this browser tab, so a reload does not lose it.