Private GeoJSON resources aren't shown on the dropdown, even if the user can read them
Open
- Dominant language
- Python
- Stars
- 27
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
The problem is that `resource_search` disconsiders the user when searching for resources. This depends on https://github.com/ckan/ckan/issues/1718 being fixed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the resource_search path named in the issue and review CKAN issue #1718, which the report identifies as a dependency. Confirm how the current search handles the user context and define done as showing private GeoJSON resources in the dropdown when that user can read them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100