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. On Wed, Jul 17, 2013 at 4:37 AM, Lee Worden <[email protected]> wrote: > Maybe it could be done with just the Referer field on the second request, > without needing to log two different page requests and correlate them. > >> Date: Tue, 16 Jul 2013 14:14:42 -0400 >> From: David Cuenca<[email protected]> >> >> >> Good idea, it could also help to know which are the links more used in a >> disambiguation page to sort them by importance. >> >> Micru >> >> On Tue, Jul 16, 2013 at 2:03 PM, Nicolas >> Vervelle<[email protected]>wrote: >> >>> >Interesting idea... >>> > >>> > >>> >On Mon, Jul 15, 2013 at 11:41 PM, Jon Robson<[email protected]> >>> > wrote: >>> > >>>> >>>> > >I understand there is an issue that needs solving where various pages >>>> > >link to disambiguation pages. These need fixing to point at the >>>> > >appropriate thing. >>>> > > >>>> > >I had a thought on how this might be done using a variant of >>>> > >EventLogging... >>>> > > >>>> > >When a user clicks on a link that is a disambiguation page and then >>>> > >clicks on a link on that page we log an event that contains >>>> > > >>>> > >* page user was on before >>>> > >* page user is on now >>>> > > >>>> > >If we were to collect this data it would allow us to statistically >>>> > >suggest what the correct disambiguation page might be. >>>> > > >>>> > >To take a more concrete theoretical example: >>>> > >* If I am on the Wiki page for William Blake and click on London I am >>>> > >taken tohttps://en.wikipedia.org/wiki/London_(disambiguation) >>>> >>>> > >* I look through and see London (poem) and click on it >>>> > >* An event is fired that links London (poem) to William Blake. >>>> > > >>>> > >Obviously this won't always be accurate but I'd expect generally this >>>> > >would work (obviously we'd need to filter out bots) >>>> > > >>>> > >Then when editing William Blake say that disambiguation links are >>>> > >surfaced. If I go to fix one it might prompt me that 80% of visitors >>>> > >go from William Blake to London (poem). >>>> > > >>>> > > >>>> > >Have we done anything like this in the past? (Collecting data from >>>> > >readers and informing editors) >>>> > > >>>> > >I can imagine applying this sort of pattern could have various other >>>> > >uses... >>>> > > >>>> > > >>>> > > >>>> > > >>>> > >-- >>>> > >Jon Robson >>>> > >http://jonrobson.me.uk >>>> > >@rakugojon >>>> > > > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
