Skip to content

Commit

Permalink
Minor bug fixes at SMP (#213)
Browse files Browse the repository at this point in the history
* Update SMP readme

* Repaired broken link for MPI-M policy
  • Loading branch information
yvgrossmann authored and Giacomo Lanza committed Oct 20, 2023
1 parent 5d23113 commit 5826010
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
4 changes: 2 additions & 2 deletions rdmorganiser/questions/SMP-Questions.xml
Original file line number Diff line number Diff line change
Expand Up @@ -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, &lt;a href=&quot;https://doi.org/10.5281/zenodo.4629662&quot; target=&quot;_blank&quot;&gt;https://doi.org/10.5281/zenodo.4629662&lt;/a&gt;.</help>
<text lang="en">Are there institutional requirements for software development?</text>
Expand All @@ -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 &amp; Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, &lt;a href=&quot;https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf&quot; target=&quot;_blank&quot;&gt;https://mpimet.mpg.de/fileadmin/02_Forschung/08_Gute_wissenschaftliche_Praxis/MPI-M-SW-Policy.pdf&lt;/a&gt;.
* Budich &amp; Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, &lt;a href=&quot;https://hdl.handle.net/21.11116/0000-000C-80B1-A&quot; target=&quot;_blank&quot;&gt;https://hdl.handle.net/21.11116/0000-000C-80B1-A&lt;/a&gt;.
* European Space Agency: ESA Open Source Policy, &lt;a href=&quot;https://essr.esa.int/esa-open-source-policy&quot; target=&quot;_blank&quot;&gt;https://essr.esa.int/esa-open-source-policy&lt;/a&gt;.
* Akhmerov et al. (2021): TU Delft Research Software Policy, &lt;a href=&quot;https://doi.org/10.5281/zenodo.4629662&quot; target=&quot;_blank&quot;&gt;https://doi.org/10.5281/zenodo.4629662&lt;/a&gt;.</help>
<text lang="de">Gibt es institutionelle Anforderungen an die Softwareentwicklung?</text>
Expand Down
3 changes: 1 addition & 2 deletions rdmorganiser/questions/SMP_Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 5826010

Please sign in to comment.