The act of testing an object according to its specifications. For instance, testing a software with a particular testType using a specific testInput and getting a specific testOutput (aka result).
If the running was done by a direct execution (rather than via a container), indicate the operating system.
If the running was done by a direct execution (rather than via a container), indicate the processor specification.
If the running was done by a direct execution (rather than via a container), indicate the runtime platform.
If the running was done using a container, such container should be pointed to here.
Actual input used by this action to run a software.
Software executed by this running action.
Link to the software tested by this action.
Input used to performed the test. Some tests may not require any input, some may require multiple ones. If order or grouping is important in the case of multiple inputs, a ListItem could help.
The type of test that it is performed on the object.
Considerations wrt ethical, legal and social aspects
Purpose and intended use stated to enable users to make a decision as to the suitability of this creative work (e.g., lab protocol, machine learning model, software) to their experimental problem or own use case.
An input required to use the computational workflow (eg. Excel spreadsheet, BAM file).
An output produced by the computational workflow (or software).
Link to installation instructions/documentation.
Link to software bug reporting or issue tracking system.
Link to this software Readme file. Property defined in the Codemeta terms.
An academic publication related to the software. Property defined in the Codemeta terms.
Text or link to deployment instructions/documentation.
Documentation about this software directed to developers who will use or reuse (e.g., extend) this software
Text or link to installation instructions/documentation. It should not be confused with the installUrl which points to a place where the installation package (e.g., .exe) can be found.
Any LearningResource that can provide orientation towards learning, education, skill acquisition, and other educational purposes about this research software.
Text or link to testing instructions/documentation.
Testing actions (e.g., continuous integration, end-to-end, etc.) performed on this software.
Documentation about this software directed to users who will use this software as it is.
Version control system used for this source code, to keep track of all commits, branches and so.
Management plans (e.g., data, software, other research output/outcomes/artifacts) are a tool for researchers and research stewards to organize and plan around research artifacts, from initial ideas to publication. This type builds on top of DataCite Metadata Schema 4.4 and maps it mandatory elements to schema.org to represent research artifact management plans. This type could be extended to cover particularities wrt management plans for specific research outcomes, e.g., data management plans or software management plans.
Link to the research project this mng plan belongs to
Link to other management plans associated to this one, e.g., an SMP associated to the DMP on the datasets used by the software
Questions asked in this management plan. If the order is important ItemList can be used, otherwise an array of Question would work.
SoftwareSourceCode handled by this software mng plan. Software applications, tools and releases from the source code should be linked directly to the source code.