This guide explains how to register your research software in Pure. Defining software in a research context is challenging. EEMCS is working on creating clear definitions. For now, consider:

• Research Software: Software that is a primary research output itself. These are important to register as seperate items.
• Supporting Software: Software that was used as a tool to produce other research outputs. These are not quite as crucial to add to Pure as separate entries.

TODO: This section needs to be updated once official definitions are established.

Registering software is important, but there are significant challenges:

• Pure's limitations: The system is not perfectly designed for registering software as a primary output (“meer Pure onmogelijkheden”).
• Versioning and Licensing: Pure does not have robust, dedicated fields for software versioning and licensing.
• Linking: Ensuring clear links between software, the datasets it uses, the repository/archive that hosts the code, and the publications that describe it is critical but must be done manually, and these might also change over time.

TODO: The best-fit category in Pure needs to be definitively chosen. This is a placeholder for the current recommendation.

The current recommendation is to use the Dataset > Dataset category. This will probably change in the future to a more specific template. Key Fields:

TODO! make sure to include:

• The license under which it is released (e.g., MIT, GPLv3).
• link to the public repository (e.g., GitHub, GitLab).
• If you have archived the software and received a DOI (e.g., from Zenodo), add the DOI link here.
• Relations to other content: Link the software to any publications that use or describe it, and any datasets it operates on.

TODO: Add screenshot: The editor window with annotations showing where to put the software title, how to fill in the description with version license, and where to add the repository link.