When performing search queries in Fess web app, results are built with href links that look like this (example values):
<a class="link" href="/go/?rt=1491302202658&docId=c684b94fac6b42c4b01dbfa7e1c046e2&queryId=be33a1e17ced43c1b236d1d37e8c59a7&order=0" data-uri="..." data-id="c684b94fac6b42c4b01dbfa7e1c046e2" data-order="0">...</a>
These values can be obtained from the response object when performing json queries:
docId queryId data-order
These are not part of the response object:
In order to increase scoring when building custom views which are not part of the Fess user interface, one would have to construct build links using the same scheme, right? Clicking on those links would take the user to the Fess server, then immediately redirect to the requested page, while other bits of the business logic such as increasing the score value for the clicked link are performed by Fess. If this is correct, how can the ‘rt’ field, which seems to be obligatory, be obtained when working with json?
Alternatively, is there another way of programmatically updating the backend with the number of clicks, or the number of likes, so that clicks on interfaces which are independent of the Fess web app are also accounted for?