As per #21 (closed), queries are also in an incomplete state as were pulled from NRP's partial coverage to begin with.

We need a good set of user stories linked to this epic describing the types of UI bindings and reporting queries that we need from the system.

We also need to decide on the information architecture of the query API. My choice would be that all parameters are logical 'AND's and are available on every all* query endpoint that necessitates them. We should thus delete filteredEconomicEvents and move those parameters to allEconomicEvents for consistency (which is fine, nobody is using that code yet). Basically, a search with no args = an "all" query.

The goal is to end up with the smallest number of most generic parameters possible, because every parameter added needs to be implemented in every system that wants to provide ValueFlows data in order to be compliant; and that takes time & effort.