Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

resources and packages will have a set of openness key's stores in their extra properties #16

Open
KrzysztofMadejski opened this issue Mar 27, 2015 · 0 comments
Open

resources and packages will have a set of openness key's stores in their extra properties #16

KrzysztofMadejski opened this issue Mar 27, 2015 · 0 comments

Comments

@KrzysztofMadejski
Copy link
Contributor

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).

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: DanePubliczneGovPl/ckanext-danepubliczne#74
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KrzysztofMadejski