fix for software identifier optionsets

rdmorganiser/options/rdmo_options_new_SMP_for_RDMO-2.0

@@ -122,7 +122,7 @@
 	</option>
 	<option dc:uri="https://rdmorganiser.github.io/terms/options/software_identifier/url">
 		<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
-		<uri_path>software_identifier_url</uri_path>
+		<uri_path>software_identifier/url</uri_path>
 		<dc:comment/>
 		<text lang="en">URL</text>
 		<text lang="de">URL</text>

rdmorganiser/questions/SMP-Questions.xml

@@ -1968,7 +1968,7 @@ Beispielsweise mit einer <a href="https://citation-file-format.github.io
 		<uri_path>smp/release-and-publish/metadata/software-pid</uri_path>
 		<dc:comment/>
 		<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/software-pid"/>
-		<is_collection>False</is_collection>
+		<is_collection>True</is_collection>
 		<is_optional>False</is_optional>
 		<help lang="en">For long-term availability and clear allocation, it is recommended to publish the software (version) with a persistent identifier. This recommendation goes hand in hand with &lt;a href=&quot;https://doi.org/10.15497/RDA00068&quot; target=&quot;_blank&quot;&gt;FAIR4RS&lt;/a&gt; F3 and &lt;a href=&quot;https://wissenschaftliche-integritaet.de/en/code-of-conduct/cross-phase-quality-assurance/&quot; target=&quot;_blank&quot;&gt;guideline 7 in the DFG Code &quot;Guidelines for Safeguarding Good Scientific Practice&quot;&lt;/a&gt;. After &lt;a href=&quot;https://doi.org/10.15497/RDA00068&quot; target=&quot;_blank&quot;&gt;FAIR4RS&lt;/a&gt; F1.1, it may also be useful to place a separate identifier on the individual software versions or components. An example of a persistent identifier is the Digital Object Identifier (DOI). In terms of research software, for example, a GitHub/GitLab Zenodo integration can generate a citable object including DOI.</help>
 		<text lang="en">Do you give a persistent identifier for you software?</text>