ckan / ckan/ckanext-mapviews

Get only the fields we need

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
27
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Depending on the data, it might be quite wasteful to get all fields using the
DataStore API. We can optimize a lot by simply getting what we need.

We'll need to change Recline's CKAN API to fix this.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the Recline CKAN API integration and tracing how DataStore requests are built for map and choropleth views. Identify where the requested fields are determined and confirm the expected behavior for each data shape. Done means the API requests only the fields needed by the view rather than retrieving every field.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.