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
Idea:
Expose the numberOfRecords SRU searchRetrieve field in the REST API for search results.
Why:
This would allow the frontend to better handle loading more results for single resources. I.e. resources that have already sent all their resources would not show this option to the user that in the end will only show that the endpoint can not provide more results (while this information already exists in the initial search response).
Concerns:
Endpoints might not always correctly set this field. Maybe due to not knowing how many results that can provide in total beforehand (result set might grow?).
Solution: show button to force request more results with hint that all results should already be present. For FCS 2.0 there is already a field resultCountPrecision that should help with interpreting the numberOfRecords field but once again this can still be misconfigured.
The text was updated successfully, but these errors were encountered:
Idea:
Expose the
numberOfRecords
SRUsearchRetrieve
field in the REST API for search results.Why:
This would allow the frontend to better handle loading more results for single resources. I.e. resources that have already sent all their resources would not show this option to the user that in the end will only show that the endpoint can not provide more results (while this information already exists in the initial search response).
Concerns:
Solution: show button to force request more results with hint that all results should already be present. For FCS 2.0 there is already a field
resultCountPrecision
that should help with interpreting thenumberOfRecords
field but once again this can still be misconfigured.The text was updated successfully, but these errors were encountered: