Paging in views of docs with reader fields

[JimStoner]

Hello,

I have a view that contains a few thousand documents, which use reader fields to control access by account/group. For someone with access to all the documents, the Ext.nd view paging bar indicates there are 161 pages, and they can navigate them correctly.

However, someone with access to only a few hundred documents runs into trouble. The paging bar still says there are 161 pages (instead of the 10 or so pages that he actually has access to), and the next/previous buttons are therefore a little wonky. Depending on where his documents are within the overall view, he may have to hit the next page button quite a few times before it actually advances to the next set of documents, etc.

I understand the reason why this happens. I'm just curious if there is any plan to fix that in a future release, and if anyone has a workaround for the meantime. One choice is to make it a categorized view based on the username, but that will only work if the reader fields are username based rather than role based. If they are role based, and someone has multiple roles, the categorized approach becomes pretty difficult.

Thanks,
Jim

[RWaters]

This has been a long standing known bug with Domino in that the count of documents it returns does not take into account reader fields. I don't know that we've come up with a good way around this yet as it would almost take evaluating the selection criteria in code then looping through all those docs to test the readers fields.... I don't think performance would be very good. If anyone has any ideas we'll glady be open to hearing them.

[jratcliff]

We can't accurately determine the count because of Reader fields. However, the next release should be accurate in displaying what a user can see if they "page thru" the data. I think the release we last posted "calculated" what the next start position should be based on what was configured as the page count. In the next release, we page thru data like the way Domino natively does it on the web. And that is by have the start parameter equal to whatever the last position of the last row is being displayed. This way, if there were 1,000 docs and you only had access to docs 1-10, and 40-50, and 800-1,000 then page one would show docs 1-10, 40-50, and 800-810 (assuming a page count of 30 rows per page). Then when the user clicked "next", the start parameter would be set to 810 (instead of 31 like it was when it was calculated).

So again, I think the next release will solve the issue of paging thru views that have docs with reader fields, we just can't (yet) determine the total # of pages since Domino doesn't report that back correctly.

~Jack

[JimStoner]

Thanks guys!