History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-376
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Dale W. Visser
Reporter: Henry Story
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sesame

Explore option in web client should use LIMIT (with next and previous buttons)

Created: 04/Apr/07 12:31 PM   Updated: 01/Oct/12 05:15 PM
Component/s: Web interface
Affects Version/s: None
Fix Version/s: 2.7.0

Issue Links:
Related
 
This issue is related to:
SES-1101 Need to retain a predictable query re... Minor Open


 Description   
The current explorer interface in Sesame 2's web client show all results in a single page, which can get way too large to handle. An improvement would be to have it set to a limit in the number of rows it shows, and have (next|previous) buttons to see 'the rest'.

 All   Comments   Change History      Sort Order:
Comment by Dale W. Visser [07/Sep/12 05:44 PM]
My team has expressed a desire for this feature, and asked my to try my hand at an implementation.

Comment by Jeen Broekstra [12/Sep/12 01:41 AM]
Dale is taking up this item, marking issue for 2.7 release (haven't added Dale as a developer yet in JIRA, hence issue is assigned to me for now).

Comment by Dale W. Visser [12/Sep/12 03:40 PM]
I am continuing to work on this. At present, my changes only address the Query tab, not the Explore tab, and have presentation bugs in some corner cases (going close to the end of results, and "prior" to the start of results.

Comment by Dale W. Visser [13/Sep/12 05:44 PM]
At present, code is checked in that fixes the presentation issue mentioned in my prior comment. In e-mail with Jeen, we have agreed that I will now modify the servlet code to modify the user's query with LIMIT and OFFSET clauses, rather than manually pruning full result set into the subset that is returned in XML, as it currently does. This should be more efficient and future-proof, i.e., be able to take advantage of future improvements in the query engine.

After that is done, the final step to resolve this issue will be to put a similar Next X/Previous X functionality into the Explore view.

Comment by Dale W. Visser [18/Sep/12 02:22 PM]
Code ready with the servlet modifications described in my last comment. Before checking in, going ahead with a further modification, one that will display "Results X to Y of Z" at the top of each page when only a subset of the full results is being returned.

Comment by Dale W. Visser [01/Oct/12 05:15 PM]
Final check in which expands this feature to the Explore page as well: revision 11976.