Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

author dropdown vs author: #348

Closed
traviscb opened this Issue · 6 comments

3 participants

@traviscb
Collaborator

Originally on 2010-11-13

Two seemingly equivalent methods of searching yield different results:

http://inspirebeta.net/search?ln=en&p=el-khadra&f=author

http://inspirebeta.net/search?ln=en&p=author%3Ael-khadra

@jrbl
Collaborator

Originally on 2010-11-16

Recently discussed in the "Dropdown annoyances" thread on project-cdsware-developers (which is apparently not archived to the web. If you didn't read it the first time, sorry 'bout your luck.)

The current zeitgeist seems to be:

Personally I think I would prefer the any field and the author field
dropdown values to behave exactly the same here, as you also seem to
suggest. That is, if people search for P1 P2 P3 in F, then send P1 P2
P3 to F unless there is some Pi of the form Fi:Xi in which case this
unit will be rather dispatched to Fi instead. This is a kind of rather
visible change in Invenio's search behaviour, so we'd better hurry
implementing it before v1.0.0-rc0 is out, if we like this change.

Since this ticket already existed, I thought I'd save Tibor the trouble of ticketizing his solution.

@tiborsimko
Owner

Originally on 2010-11-16

This is actually a different issue than the one discussed in the "dropdown annoyances" thread...

@traviscb
Collaborator

Originally on 2010-11-16

Yes, very different, and in my view quite critical, hence my bumping this ticket priority, since there are in fact different results for seemingly equivalent searches.

@tiborsimko
Owner

Originally on 2010-11-16

`Fixed' by apache graceful. This is a problem related to long-running Invenio WSGI daemon processes and the search cache invalidation. We saw another example a few weeks ago. I'll fix that properly in the codebase.

@tiborsimko
Owner

Originally on 2010-11-16

Temporarily inactivated search cache on PROD, see https://inspirert.cern.ch/Ticket/Display.html?id=103880.

@tiborsimko
Owner

Originally on 2010-11-16

I have fixed this particular case by re-indexing concerned records. It seems some/many records have not been fully author-re-indexed after putting some fuzzy author name tokenizer update into production. Anyway, we wanted to get rid of the first names, which will require full re-indexing of author names, see #219. So complete re-indexing will be done as part of that.

Therefore I'm closing this ticket here due to #219 and #354.

@tiborsimko tiborsimko closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.