259 documents Mink's behavior when encountering a URI-R that specifies its own TimeGate. This behavior resembles a sort-of implicit precedence and short-circuiting, i.e., the TimeGate is first queried and due to Mink's current behavior, a request is never sent to the aggregator.

We want to improve this behavior to give the user more control over the requests sent from their browser using Mink. This should consist of a means (interface elements) of:

[ ] Controlling the ordering of requests where applicable (e.g., 1. own TimeGate, 2. aggregator)
[ ] Provide control of user-specified precedence (e.g., allow aggregator to be queried first)
[ ] Provide conditional short-circuiting (e.g., only go to aggregator if nothing is found at own TG and vise-versa)

Further, the behavior exhibited ought to be represented somehow in the Mink interface. Some indicator to allow a user to obtain more information on the procedure performed (e.g., TG-only-when-present) and how to customize it would be useful and explain, for example, why so few mementos are numerically displayed for a URI-R that has many captures in IA.

machawk1 / Mink

Provide a UI to inform and change query precedence and short-circuiting behavior #264

259 documents Mink's behavior when encountering a URI-R that specifies its own TimeGate. This behavior resembles a sort-of implicit precedence and short-circuiting, i.e., the TimeGate is first queried and due to Mink's current behavior, a request is never sent to the aggregator.