Product package standard

An Artefact paper or a Reproduction report is submitted with a product package: the files another researcher needs to build, run or print the product and test it. The package is reviewed with the article, archived with it and cited with its own DOI.

ProductFilesPreview and archive
3D objectFiles: 3MF (primary) or STL; source file (STEP, FreeCAD, Blender, OpenSCAD); print note (material, layer height, infill, supports, time, cost)Preview and archive: GLB preview
3D scan and photogrammetryFiles: PLY or OBJ, photo list and metadataPreview and archive: GLB or a 3D scene
App and softwareFiles: Source code with a version tag, installation note, licence; APK or web address where availablePreview and archive: Zenodo archive of the code; screenshots and a short video
Game and VR sceneFiles: Project files (e.g. Unity, Godot), a built version, hardware requirementsPreview and archive: Gameplay video; a browser version where possible
Teaching and counselling materialFiles: Editable source (DOCX, ODT, PPTX) and PDF; guide for usePreview and archive: PDF preview
AI prompt set and toolchainFiles: Prompts, model name and version, settings, sample outputsPreview and archive: Zenodo archive

Product review

Besides the double-anonymized review of the text, a product reviewer opens, installs, runs or prints the product and completes this checklist:

  • The files open; the runnable or printable version and the source give the same product.
  • With the stated settings it runs or prints on ordinary hardware (a desktop printer, a school computer, a mid-range phone).
  • Dimensions, time, cost and requirements match the article.
  • For products for children, safety and data privacy are discussed (for toys, EN 71-1; for apps, the data collected).
  • The adaptation guide is enough for another researcher to reproduce the product.

Rules

  • For anonymized review, author names, software accounts, institution names and file paths are removed from the files (3MF, CAD and project files, code repositories); the real metadata is restored at publication. A code repository is shared through an anonymous copy during review.
  • Text and files are published under CC BY 4.0; software code may also be released under MIT or Apache-2.0.
  • The reviewed version of the product is archived on Zenodo and linked to the article; the product is citable even if an outside repository disappears.