Skip to content

Commit

Permalink
Removed <br>, replaced with \n as they are not rendering correctly on…
Browse files Browse the repository at this point in the history
… the GW FE
  • Loading branch information
camilner-hdr committed Jul 23, 2024
1 parent 1e73c6a commit a244b6d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/HDRUK/3.0.0.form.json
Original file line number Diff line number Diff line change
Expand Up @@ -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"
],
Expand Down Expand Up @@ -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.<br>- 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.<br>- If the dataset is a **\u201clinked dataset\u201d**, please indicate this using the prefix **\u201cLinked\u201d**.<br>- Please **avoid acronyms** wherever possible.<br>- Good titles should summarise the content of the dataset and if relevant, **the region the dataset covers**.<br>- **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"
],
Expand Down

0 comments on commit a244b6d

Please sign in to comment.