resources and packages will have a set of openness key's stores in their extra properties
That's what said in the doc but internally this plugin is using model.TaskStatus which seems quite suboptimal (having to query three times task_status_show in each resource view).
That's what said in the doc but internally this plugin is using
model.TaskStatus
which seems quite suboptimal (having to query three timestask_status_show
in each resource view).I wonder why did you take this path?
I'm planning to put those score in resource extra fields to be able to filter datasets based on openess: https://github.com/DanePubliczneGovPl/ckanext-danepubliczne/issues/74