On Tue, 22 Jun 2010, Roman Chyla wrote: > I shall have numbers later, but the lucene autocomplete is > *definitely* on the safe side concerning scalability and speed.
That is good to hear. However we should have in mind that it may be needed for the auto-suggest framework to also work with the real DB content, e.g. to give a hint as to how many results are to be expected. Hence my musings about cross-linking semantic suggestions with DB-content-driven suggestions two weeks ago (and in previous meetings). Having two DB systems around (Lucene, Invenio) makes this type of cross-suggestions a bit harder infrastructure-wise. A concrete use case for DB-driven-suggestions are inputters needs, when the query can be as convoluted as: the cataloger starts typing Geneva in the address field, the system looks up in the Institutes database how many different institutions we have with the address town Geneva, then looks up how many papers we have in the system coming from these institutions, and then rank final institution name propositions accordingly (e.g. CERN would come before University of Geneva). This example is what Marko was working on via KBDs. Best regards -- Tibor Simko
