...
Using data filters relies on “user attributes” and requires two parts to setup. User attributes are a concept in Weave where custom attributes can be associated with a user and then referenced in configuration files, allowing for per-user customisation. By adding the ability for the client to set custom user attributes and ensuring the appropriate Weave configuration items can make use of those attribute to perform filtering Weave 2.6.10 make it possible for the administrator to provide the user with the ability to perform dynamic filtering.
The XML examples shown below are presented as complete individual XML configuration files that would each need to be included into Weave to create a working configuration, the XML configurations themselves could all be included in a single configuration file if required.
Also, there has been no attempt made to present the XML and examples of valid XML files, that is the normal rules for XML files apply and you’re expected to know them or look up the relevant section in this wiki. That’s not to say the XML examples are expected to be invalid, just that when creating your own versions of the XML this page is not intended as an exhaustive XML tutorial and standard XML editing rules will need to be followed for your configuration files, e.g. the use of CDATA tags or escape sequences for special XML characters.
Defining a filter
For an end user to be able to enter the information required to apply a filter a filter definition must be created. The filter definition specifies what values can be used to filter the underlying data, in the example below we are just filtering on the inspection date, but the filter can contain multiple unrelated (unrelated to each other, not unrelated to the trees) parameters to filter on things other than inspection date, for example on the tree species.
...