#461: Authorpages: Interface with BibauthorID backend
------------------------+---------------------------------------------------
Reporter: hweiler | Owner: hweiler
Type: defect | Status: assigned
Priority: blocker | Milestone: v1.0
Component: WebSearch | Version:
Resolution: | Keywords: Authorpages, Bibauthorid, exact search
fallback
------------------------+---------------------------------------------------
Comment (by simko):
Replying to [comment:7 tbrooks]:
> I would not bother with this. Instead patch existing behavior
> as best as possible in short time and work on integrating AID searching.
If BibAuthorID table status indicates that these exact name variants
are safe to offer, then it is much better to offer this than to offer
record ID based Boolean expression. (Firstly, just listing Ellis's
publications via `recid:1 OR recID:2 ...` may get beyond browser's URL
length limits; secondly, clicking on such a link would mean to make
~1000 queries and ~999 set intersections on the fly, which is
unnecessarily slow.) Implementation time wise, it should be very
cheap to offer exact-name based links, since we have to do that for
non-author-ID powered sites anyway. (BibAuthorID would only suggest
which name variants to use in the inner OR.) So I would not rule this
option out as non-interesting; it should be cheap to implement.
I'd say we should rather stay away from record ID based links whenever
possible.
> This I'm not as sure about, and doesn't seem to get us out of the
> current problem, but maybe I am not understanding.
This was again a looking-into-the-future style of comment, notably so
that people searching for `John Doe` would also see `J. Doe` papers in
the results, if we know that `J` stays for `John` and not for `Jane`
in some records via author IDs. So that `J. Doe` in some records could
get string-indexed also as `John Doe`, if BibAuthorID module advices so.
--
Ticket URL: <http://invenio-software.org/ticket/461#comment:8>
Invenio <http://invenio-software.org>
