'options' keyword added to various properties

[duncandewhurst]

In the 0.3-dev schema, an options keyword has been added to several properties:

• vulnerability.functions.vulnerability
• vulnerability.functions.fragility
• vulnerability.functions.damage_to_loss
• vulnerability.functions.engineering_demand
• vulnerability.socio_economic

For example:

rdl-standard/schema/rdls_schema.json

Lines 380 to 393 in da41d19

	"socio_economic": {
	"title": "Socio-economic indices",
	"type": "array",
	"description": "Array of socio-economic indices vulnerable to the hazard.",
	"items": {
	"$ref": "#/$defs/SocioEconomicIndex"
	},
	"minItems": 1,
	"uniqueItems": true,
	"options": {
	"button_group": "socio_economic",
	"button_label": "Add Socio-Economic Index"
	}
	}

@matamadio @stufraser1 I can't see this discussed anywhere, but I'm guessing it is to do with the behaviour of the metadata editor. Please could you clarify the purpose of the keyword?

[matamadio]

This was introduced with the refactoring of V schema being functionally split as Vulnerability functions (with their own set of attributes) and Socio-Economic indices (with a different set of attributes).

Options are used by the editor. There might be a way to do it without adding those additional variable to the schema.

[duncandewhurst]

Thanks for the clarification.

Options are used by the editor. There might be a way to do it without adding those additional variable to the schema.

Yes, I think it would be preferable to keep that kind of UI config separate from the schema. Could it be moved to a config/mapping file in the metadata editor repository?

[matamadio]

Those options attributes have now been removed from schema, MDE still works as expected.
See latest release: https://github.com/GFDRR/CCDR-tools/blob/main/_static/rdls_schema_v0.3.json

[duncandewhurst]

Great. I'll leave this issue open until that change has been made in this repo.