Grouping - Versionsgeschichte

Billig am 5. Mai 2026 um 12:34 Uhr

2026-05-05T12:34:09Z

2025-09-08T16:45:00Z

‎Structure

2025-09-08T16:42:25Z

‎Structure

2025-09-08T16:41:15Z

‎Structure

2025-09-02T12:06:27Z

‎Structure

2025-09-02T12:01:56Z

‎Structure

2025-07-23T12:07:10Z

‎Structure

2022-11-09T09:08:11Z

‎Structure

2022-10-16T13:03:33Z

‎Resource Identifier Regex

2022-10-16T12:52:36Z

‎Structure

@@ Zeile 9: / Zeile 9: @@
 The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). For code systems ("_id": "csvGroups"), the hierarchy is limited to two levels, namely the top level and its children level. For value sets ("_id": "vsGroups"), only one level ("children") is allowed.
-Within the 'children'-arrays there have to be at least two childrens.
+Within the 'children'-array at the second level (for code systems) there have to be at least two childrens.
 <syntaxhighlight lang="JSON" line>

@@ Zeile 52: / Zeile 52: @@
 </syntaxhighlight>
-* The ''group'' names in line 16 have to be referenced in the resource at uploading. Every code system or value set that has this group name is uploaded
+* The ''group'' names in line 16 have to be referenced in the resource at uploading. Every code system or value set that has this group name is displayed.
 === Resource Identifier Regex ===

← Nächstältere Version		Version vom 8. September 2025, 16:41 Uhr
Zeile 8:		Zeile 8:

	The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). For code systems ("_id": "csvGroups"), the hierarchy is limited to two levels, namely the top level and its children level. For value sets ("_id": "vsGroups"), only one level ("children") is allowed.		The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). For code systems ("_id": "csvGroups"), the hierarchy is limited to two levels, namely the top level and its children level. For value sets ("_id": "vsGroups"), only one level ("children") is allowed.
		+
		+	Within the 'children'-arrays there have to be at least two childrens.

	<syntaxhighlight lang="JSON" line>		<syntaxhighlight lang="JSON" line>

@@ Zeile 7: / Zeile 7: @@
 == Structure ==
-The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). The hierarchy is limited to two levels, namely the top level and its children level.
+The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). For code systems ("_id": "csvGroups"), the hierarchy is limited to two levels, namely the top level and its children level. For value sets ("_id": "vsGroups"), only one level ("children") is allowed.
 <syntaxhighlight lang="JSON" line>

@@ Zeile 7: / Zeile 7: @@
 == Structure ==
-The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). The hierarchy is limited to two levels, namely the top level and the children level.
+The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). The hierarchy is limited to two levels, namely the top level and its children level.
 <syntaxhighlight lang="JSON" line>

@@ Zeile 7: / Zeile 7: @@
 == Structure ==
-The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading''').
+The content hierarchy is defined by the following json structure ('''comments below (//) are only for documentary purposes, do not use them at uploading'''). The hierarchy is limited to two levels, namely the top level and the children level.
 <syntaxhighlight lang="JSON" line>
@@ Zeile 24: / Zeile 24: @@
                // tree node name displayed in the frontend
                "name": "Codesystems",
-               // group names for related resources or 'children'-property (recursively) - used at upload
+               // group names for related resources - used at upload
                "relGroup": ["ICD", "OPS"]
              },

@@ Zeile 54: / Zeile 54: @@
 === Resource Identifier Regex ===
-The resources referenced by group name above are provided in alphabetical order over the resource identifiers. Alternatively, the referenced resources can be defined by giving a list of regular expressions. For instance, line 19 ff. references all code systems whose resource identifier starts with 'snomed-' or 'mesh-' in the given order.
+The resources referenced by group name above (line 16) are provided in alphabetical order over the resource identifiers. Alternatively, the referenced resources can be defined by giving a list of regular expressions. For instance, line 19 ff. references all code systems whose resource identifier starts with 'snomed-' or 'mesh-' in the given order.
 == REST calls ==

@@ Zeile 30: / Zeile 30: @@
                "name": "Codesystems by regex",
                // list of regular expressions for resource id's
-               "resourceIds": ["snomed-.*", "mesh-.*"]
+               "resourceIdRegex": ["snomed-.*", "mesh-.*"]
+             }
+           ]