Editing records and advancing forward page by page- how the list refreshes and displays the records

[GoogleCodeExporter]

An annoying behavior when editing lots of records, page by ascending page;

1. Load the attached .tsv file into refine.
2. For this demonstration, make sure your page view is 10 records per 
page(default view).
3. facet > Facet > Text facet.
4. On the Facet, click 'include' for the 'facetCriteria(30)' item.
5. Click 'next' to go to second page.
6. At this point, record #11 should show 'start of new page' record, and record 
#20 should show 'end of page' record, as is seen in the 'notes' column.
7. in the column names 'facet', remove the 'facetCriteria' text from records 
12, 14, 16 and 18.
8. Click the 'next' link to go to page 3 which should display records 21 to 30.
9. You will now notice on this page, there is no record that says 'start of new 
page', and the reason for this is because it is now on the previous page, a 
result of those 4 records(12, 14, 16, and 18) being edited, and thus no longer 
being bound to the respective Facet.  And herein is the problem.

When editing hundreds of pages of data, this is a real pain, because instead of 
the user being able to simply click 'next' and have all un-revised/un-edited 
records be displayed, the user instead must first click the 'back' link to 
commit the changes, and then click the 'next' link so that those 4 records that 
took the place of the above modified 4 records, can be reviewed and edited if 
need-be prior to moving on to the new page.  If any of those 4 records are 
edited, then the problem occurs again, and is further compounded, which is to 
say, the user has to click the 'back' link again for a measly <4 records.

The correct behavior should allow the user to click the 'next' link without 
having to worry about un-revised records ending up on the previous page.  This 
should be accomplished by taking the last edited record on the page(e.g.- #18), 
and using the next record up(e.g.- #19) as the record that will display FIRST 
on the refreshed 'next' page, accounting for any/all records that dropped out 
of the Facet as a result of the edits.

So, in the above example, when the 4 records(12, 14, 16, and 18) are edited 
wherein their edits result in their exclusion from/within the Facet, the list, 
upon clicking the 'next' link, subsequently consolidates downward, wherein #13 
goes down to the #12 row, #15 goes down to the #14 row, #17 goes down to the 
#16 row, and #19 goes down to the #18 row.  This means that records #21, 22, 
23, and 24 that are on the next/un-seen and un-revised page, end up 
consolidating down accordingly, ending up on the second page(records 21-30) 
when the user has clicked through to the 3rd page, hence, the user misses those 
records as a result.  Ideally, Refine should not allow any records that are on 
the subsequent page to end up on the previous page... the adjustment should be 
made based on the next page, not based on consolidating downward imo.  Or, at 
minimum, the user should be able to toggle the option, or have a 'next-fixed' 
link to choose from.

Thanks,

Eric Jarvies

Original issue reported on code.google.com by ericjarv...@gmail.com on 5 May 2012 at 5:33

Attachments:

• example.tsv