Suggestion made, maybe made twice.
email written, it is in working not visible on main roadmap yet.
Research hardware documentation are complex including text, software and specific binary files (CAD, PCB,..). They are currently not well accepted as a research output, and there is no good ways to publish hardware. In the objective to produce FAIR hardware, the use of a specific resource type in datacite would be helpful.
In addition, this would make it easier for users to distinguish the "instrument" type (PID for the physical object) and the "hardware design" type (PID for the documentation necessary to build the physical object).
Our goal is to allow specific publication of hardware using a workflow similar to software and dataset, that is: independent of the scientific journals by the end of next year. The RDA IG on FAIR for research hardware (https://www.rd-alliance.org/groups/fair-principles-research-hardware) is particularly interested in developing the ecosystem that would make that possible. A pilot solution will be developed inside the open.make project in Berlin. Other players like the OHO foundation and the internet of production are involved, as they are working on metadata for hardware documentation and discovery mechanisms.
The use of a specific resourceTypeGeneral would make it much easier to retrieve hardware design, and show some recognition for this type of research output. Accomplishing this goal will allow the recognition of hardware documentation as a research output, fostering the development of collaborative development of hardware in academia.
Adding a manifest.yaml file will make the documentation discoverable by some bots, one can also manually include information in some index for hardware. to our knowledge, there is no "hardware design" that was archived via datacite.
Suggestion made, maybe made twice. email written, it is in working not visible on main roadmap yet.
Research hardware documentation are complex including text, software and specific binary files (CAD, PCB,..). They are currently not well accepted as a research output, and there is no good ways to publish hardware. In the objective to produce FAIR hardware, the use of a specific resource type in datacite would be helpful. In addition, this would make it easier for users to distinguish the "instrument" type (PID for the physical object) and the "hardware design" type (PID for the documentation necessary to build the physical object).
Our goal is to allow specific publication of hardware using a workflow similar to software and dataset, that is: independent of the scientific journals by the end of next year. The RDA IG on FAIR for research hardware (https://www.rd-alliance.org/groups/fair-principles-research-hardware) is particularly interested in developing the ecosystem that would make that possible. A pilot solution will be developed inside the open.make project in Berlin. Other players like the OHO foundation and the internet of production are involved, as they are working on metadata for hardware documentation and discovery mechanisms.
The use of a specific resourceTypeGeneral would make it much easier to retrieve hardware design, and show some recognition for this type of research output. Accomplishing this goal will allow the recognition of hardware documentation as a research output, fostering the development of collaborative development of hardware in academia.
Adding a manifest.yaml file will make the documentation discoverable by some bots, one can also manually include information in some index for hardware. to our knowledge, there is no "hardware design" that was archived via datacite.