Improve pagination functionality in statement table

[mbrush]

It is very hard to get a sense of the overall breadth of statements with the current pagination approach, where the user has to scroll to the bottom to add new statements. And if a filter is set, the new statements get sorted as they are added so it is not clear which are new. Overall it is a very cumbersome workflow. Two suggested improvements:

First, I would like the option of loading all results at once.

Second, I would like to see a count of the total number of results displayed, that gets updated when a user selects a filter.

[RichardBruskiewich]

Hi Matt,

Loading all the results at once is a serious challenge due to timeout issues. Some beacons may have a huge number of matches to the given search criteria especially for very general keyword searching and concepts which have a large number of statements. This problem compounds as the number of beacons will increase.

One of the principles guiding us here may be "most relevant hits" to rank the hits on the table. I don't know how well this is embraced by the beacons (I'll have to recheck if this principle is adequately documented in the API) but it may help us deal with a huge amount of knowledge.

We'll see what we can do to improve the user experience with the statement table without hitting serious bottlenecks in (timeout) performance.