Merge pull request #49 from HDRUK/cam/remove-is-optional

Cam/remove is optional
HDRUK · Jul 24, 2024 · f483e72 · f483e72
2 parents 56472b6 + b444209
commit f483e72
Show file tree

Hide file tree

Showing 6 changed files with 308 additions and 311 deletions.
diff --git a/docs/HDRUK/3.0.0.form.json b/docs/HDRUK/3.0.0.form.json
@@ -24,7 +24,7 @@
                   "required": true,
                   "title": "Dataset Version",
                   "description": "Dataset metadata version.",
-                  "guidance": "Dataset metadata version should follow standard SEMVER naming conventions(https://semver.org). For example: 1.1.0 major.minor.patch.<br> Major: Significant/breaking changes.<br> Minor: New features and bug fixes.<br> Patch: Minor fixes without new features.\n",
+                  "guidance": "Dataset metadata version should follow standard SEMVER naming conventions(https://semver.org). For example: 1.1.0 major.minor.patch.\\nMajor: Significant/breaking changes.\\nMinor: New features and bug fixes.\\nPatch: Minor fixes without new features.",
                   "examples": [
                         "1.1.0"
                   ],
@@ -98,7 +98,7 @@
                   "required": true,
                   "title": "Title",
                   "description": "Title of the dataset limited to 150 characters. It should provide a short description of the dataset and be unique across the gateway. If your title is not unique, please add a prefix with your organisation name or identifier to differentiate it from other datasets within the Gateway. Please avoid acronyms wherever possible. Good titles should summarise the content of the dataset and if relevant, the region the dataset covers.",
-                  "guidance": "- The **title** should provide a short description of the dataset and be **unique** across the gateway.\\n- If your title is not unique, please **add a prefix with your organisation name or identifier** to differentiate it from other datasets within the Gateway.\\n- If the dataset is a **\u201clinked dataset\u201d**, please indicate this using the prefix **\u201cLinked\u201d**.\\n- Please **avoid acronyms** wherever possible.\\n- Good titles should summarise the content of the dataset and if relevant, **the region the dataset covers**.\\n- **Example**: North West London COVID-19 Patient Level Situation Report',",
+                  "guidance": "- The **title** should provide a short description of the dataset and be **unique** across the gateway.\\n- If your title is not unique, please **add a prefix with your organisation name or identifier** to differentiate it from other datasets within the Gateway.\\n- If the dataset is a **\u201clinked dataset\u201d**, please indicate this using the prefix **\u201cLinked\u201d**.\\n- Please **avoid acronyms** wherever possible.\\n- Good titles should summarise the content of the dataset and if relevant, **the region the dataset covers**.\\n- **Example**: North West London COVID-19 Patient Level Situation Report",
                   "examples": [
                         "North West London COVID-19 Patient Level Situation Report"
                   ],