-
Notifications
You must be signed in to change notification settings - Fork 172
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.
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
Filter datasets included in data.json #2103
Comments
We have some working code for this in another repo that would fufill the first option described above (organic groups-based filtering). For now we're going to clean that up and move it into DKAN repo to complete this story - we may revisit later if we see a need for finer-grained filtering. |
(Filtering on data.json schema presents a number of problems as well, might require rendering all datasets and then removing filtered ones, which would not be very efficient) |
Here is a gist that sort of anonymizes the custom code we did for a client: https://gist.github.com/dafeder/a4f036e717a63a05cb5a05787db31d14 |
This ticket will be used to re-build DKAN once open_data_schema_map module is updated, ticket: https://waffle.io/NuCivic/dkan_management/cards/59ce9dfa45643200124b88a1 @kimwdavidson |
CIVIC-3430
User Story
As a site manager, I need to filter the datasets included in data.json, so that I can have dataset content on my site that does not get federated to data.gov
Desctiption
Many data portals publish datasets harvested from multiple state and city organizations. However, these datasets should not be included in the data.json feed that gets reported to data.gov.
Add a page to the admin UI that lets a site manager toggle groups from appearing in the data.json. If a dataset is not in the list of groups defined in the settings, do not add it to the data.json file.
An alternate strategy would be to filter or exclude by arbitrary POD value pairs (for instance, to include only datasets with a certain
bureauCode
orpublisher.name
).The available filtering options should allow for an easy way to QA that the correct datasets are being included in the data.json
Acceptance Criteria
group/publisher
the total number of datasets on the site
the number of datasets marked to be included in the data.json feed
The text was updated successfully, but these errors were encountered: