feat: add variablemeasured facet type for schema:variableMeasured/PropertyValue search

[Copilot]

Description

Adds a variablemeasured facet type that lets users filter datasets by schema:variableMeasured → schema:PropertyValue → schema:name, using CONTAINS-based matching rather than exact IN lookups. The qlever and ecoforecast configs now expose this facet in the sidebar.

Changes

SparqlQueryBuilder.js

• buildVariableMeasuredFilter — generates the three-triple PropertyValue traversal with FILTER(CONTAINS(LCASE(STR(?name)), LCASE("value"))). Multiple selected values combine with ||. Input sanitized via existing escapeValue.
• buildVariableMeasuredPropertyPattern — binds ?value to distinct PropertyValue names; used by the facet options sidebar query.
• buildFilterFragments — dispatches variablemeasured type to the new filter builder.

SearchService.js

• buildFacetOptionsQuery — branches on facetConfig.type === 'variablemeasured' to call buildVariableMeasuredPropertyPattern instead of the generic path, so the sidebar lists actual property names.

Config YAML

• config_qlever.yaml — uncomments and activates the variableMeasured facet (type changed from commented text to variablemeasured).
• config_ecoforcast.yaml — adds variableMeasured facet for the tool scenario.

Generated SPARQL (filter active)

?subj schema:variableMeasured|sschema:variableMeasured ?variableMeasured_vm .
VALUES ?variableMeasured_pvType { schema:PropertyValue sschema:PropertyValue }
?variableMeasured_vm a ?variableMeasured_pvType .
?variableMeasured_vm schema:name|sschema:name ?variableMeasured_propName .
FILTER(CONTAINS(LCASE(STR(?variableMeasured_propName)), LCASE("datetime"))) .

Review Time Estimate

• Immediately
• Within a week
• When possible

Type of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Other (any another change that does not fall in one of the above categories.)

Checklist:

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My change requires updating the documentation.
• I have made necessary changes to the documentation.
• I have added tests related to my changes.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

• Fixes qlever variablesMeasured facet #280

[valentinedwv]

@copilot
Can we make buildVariableMeasuredFilter a generic buildPropertyValueNameFilter? we may want to different @Propertyvalue

[Copilot]

@copilot
Can we make buildVariableMeasuredFilter a generic buildPropertyValueNameFilter? we may want to different @Propertyvalue

Done in the latest commit. buildVariableMeasuredFilter is now buildPropertyValueNameFilter (and buildVariableMeasuredPropertyPattern → buildPropertyValueNamePattern). Both methods read sparql_property from the facet config, defaulting to schema:variableMeasured|sschema:variableMeasured when not set.

To use a different PropertyValue relationship, just add a facet entry in config with the desired property path, e.g.:

- field: measurementTechnique
  title: Measurement Technique
  type: propertyvalue
  sparql_property: "schema:measurementTechnique|sschema:measurementTechnique"

The canonical type is now propertyvalue; variablemeasured remains a backward-compatible alias in the dispatch switch.