-
Notifications
You must be signed in to change notification settings - Fork 7
Publishing GCP Survey to Schema Repo
Publishing GCP Survey to Schema Repo
Create branch on eq-questionnaire-schemas with the ticket ID at the start of the branch name (main not master on this repo)
https://github.com/ONSdigital/eq-questionnaire-schemas
Open up Author on GCP.
Open up the Settings tab. Then open Themes, IDs, form types and legal bases tab.
Check to see if Survey ID, eQ ID and Form type are set and that there is a Theme selected.
If none of these are set it may be worth cloning the Questionnaire and setting in Author.
The name of the json file should be the eqId. If this is not provided then ask the business for it. If this is an update to an existing schema then just use the existing one.
Open up the Metadata tab and make sure trad_as is set to Text (Optional) in the Type column.
https://author.eqbs.gcp.onsdigital.uk/convert/eqId
Copy the JSON
Remove the commented out code at the top of the JSON eg.
// 20220606095245
// https://author.eqbs.gcp.onsdigital.uk/convert/74a65e55-4046-42fc-ab09-0420d7c3b4b7
Go through the JSON and check the Survey ID, and Form type are set once more.
Navigate to the last few lines of the code to check that “trad_as” is set as below
{
"name": "trad_as",
"type": "string",
"optional": true
},
When you are happy with the JSON push up the code and create a PR
When all the tests are green and you have two ticks DO NOT MERGE but forward the link of the PR to the EQ team and they will merge and and send the survey to Pre Prod and Prod
A new bug was discovered when using Mutual Exclusive options. If a Percentage with an Or with a Checkbox answer is used it throws an error with the Schema. This can be fixed but removing the "options": []
in the JSON for the percentage answer and "decimal_places": 0,
in the checkbox answer.
See Martyn's commit https://github.com/ONSdigital/eq-questionnaire-schemas/pull/277/commits/fcb47956754e626183cbde835016d27e5d9ce3f8 for an example. We will raise a bug to fix this but I've put this here just in case we come across this again before a fix is made