You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The loading of a user's resources in the dashboard (here) calls CKAN's user_show API action which in turn calls package_show to fetch all user packages (here).
As has been proposed and implemented herepackage_search could be used instead of package_show to allow passing limit and offset parameters to the query.
Maybe we should implement this logic in our CKAN version as pagination is meaningless as is.
The text was updated successfully, but these errors were encountered:
The only thing we have to ensure is that the same authorization checks are performed (e.g. a proper NotAuthorized exception will be raised) in either cases (show/search).
Also, we should adapt our templates, since search results have a completely different structure than ordinary package_show results.
Another approach (but only in case the solution proposed by @smanousopoulos does not yield significant improvements), would be to bypass user_show and write our own lightweight version. This is because user_show gathers several pieces of information (such as followers and activity history) which are irrelevant to a dashboard for resources.
The loading of a user's resources in the dashboard (here) calls CKAN's user_show API action which in turn calls package_show to fetch all user packages (here).
As has been proposed and implemented here package_search could be used instead of package_show to allow passing limit and offset parameters to the query.
Maybe we should implement this logic in our CKAN version as pagination is meaningless as is.
The text was updated successfully, but these errors were encountered: