From 5826010f7616721e9e96c7352e2d911b58bf64b3 Mon Sep 17 00:00:00 2001 From: Yves Vincent Grossmann <89014209+yvgrossmann@users.noreply.github.com> Date: Fri, 13 Oct 2023 14:36:11 +0200 Subject: [PATCH] Minor bug fixes at SMP (#213) * Update SMP readme * Repaired broken link for MPI-M policy --- rdmorganiser/questions/SMP-Questions.xml | 4 ++-- rdmorganiser/questions/SMP_Readme.md | 3 +-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/rdmorganiser/questions/SMP-Questions.xml b/rdmorganiser/questions/SMP-Questions.xml index d9fbd24f..950ad0ef 100644 --- a/rdmorganiser/questions/SMP-Questions.xml +++ b/rdmorganiser/questions/SMP-Questions.xml @@ -547,7 +547,7 @@ At the same time, individual institutes, working groups, etc. can also impose ru Below you will find a collection of examples of institutional regulations related to software: -* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf" target="_blank">https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf</a>. +* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://hdl.handle.net/21.11116/0000-000C-80B1-A" target="_blank">https://hdl.handle.net/21.11116/0000-000C-80B1-A</a>. * European Space Agency: ESA Open Source Policy, <a href="https://essr.esa.int/esa-open-source-policy" target="_blank">https://essr.esa.int/esa-open-source-policy</a>. * Akhmerov et al. (2021): TU Delft Research Software Policy, <a href="https://doi.org/10.5281/zenodo.4629662" target="_blank">https://doi.org/10.5281/zenodo.4629662</a>. Are there institutional requirements for software development? @@ -560,7 +560,7 @@ Gleichzeitig können sich auch einzelne Institute, Arbeitsgruppen etc. Regeln zu Im Folgenden finden Sie eine Beispielsammlung für institutionelle Regelwerke mit Bezug zu Software: -* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf" target="_blank">https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf</a>. +* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://hdl.handle.net/21.11116/0000-000C-80B1-A" target="_blank">https://hdl.handle.net/21.11116/0000-000C-80B1-A</a>. * European Space Agency: ESA Open Source Policy, <a href="https://essr.esa.int/esa-open-source-policy" target="_blank">https://essr.esa.int/esa-open-source-policy</a>. * Akhmerov et al. (2021): TU Delft Research Software Policy, <a href="https://doi.org/10.5281/zenodo.4629662" target="_blank">https://doi.org/10.5281/zenodo.4629662</a>. Gibt es institutionelle Anforderungen an die Softwareentwicklung? diff --git a/rdmorganiser/questions/SMP_Readme.md b/rdmorganiser/questions/SMP_Readme.md index 03bfeab8..ff885d38 100644 --- a/rdmorganiser/questions/SMP_Readme.md +++ b/rdmorganiser/questions/SMP_Readme.md @@ -24,8 +24,7 @@ Furthermore, this SMP template was inspired by some documentations, specially: | 2.0 | 18th August 2023 | a) Addition of a question regarding Qualifty References (reference to FAIR4RS I2 and R2); b) adjustments to questions and help texts for the FAIR4RS viewer; c) minor adjustments to help texts thanks to feedback; d) broken links repair + Thanks a lot for the feedback by the RDMO Community!| # Implementing -The catalogue uses some of the generic elements from RDMO. Therefore, all generic elements from "Conditions", "Domain", "Options" and "Questions" must already be implemented in advance. -To use this SMP, the additional SMP elements "Condition", "Domain" and "Questions" must then be imported into the own RDMO system. The respective order is documented in the [generic Readme file of the RDMO content](https://github.com/rdmorganiser/rdmo-catalog/tree/master/rdmorganiser#readme) and must be observed. +The catalogue uses the generic elements from RDMO. Therefore, all generic elements from "Conditions", "Domain", "Options" and "Questions" must already be implemented in advance. # Transferability This catalogue introduces many custom attributes, as the generic RDMO attributes do not always cover the specific aspects of software. For this reason, the existing views in RDMO cannot be used for this catalogue, or only to a very limited extent.