On Wed, Jul 17, 2013 at 4:26 AM, John Erling Blad jeblad@gmail.com wrote:
Send out a "mw-previous-referrer" on the disambiguation page and echo it back from the browser. It could be done through a cookie. On next page it must be removed, either in the server or in the browser. The server can simply rip off any incoming cookie, but not sure if this will work in the squids or if it is simple to implement. The echoed back mw-previous-referrer can then be logged somehow for the landing page. Analysis of the log will then identify missing or failed linkage.
The same could be done for search pages, as much of the same problem exist there.
Instead of using cookies javascript can do this by remembering specific pages by using the session storage. That could imply a logging facility with some kind of api access.
This is an even worse solution. Not only does it have the same problem I mentioned, but also what if the person just browses to another page by URL? Then the server thinks the user got there from the disambiguation page.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerromeo@gmail.com