Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#348 closed defect (fixed)

author dropdown vs author:

Reported by: tbrooks Owned by: simko
Priority: critical Milestone:
Component: WebSearch Version:
Keywords: syntax Cc:

Description

Change History (10)

comment:1 Changed 3 years ago by jblayloc

  • Milestone set to v1.0

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.

comment:2 Changed 3 years ago by simko

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

comment:3 Changed 3 years ago by tbrooks

  • Priority changed from major to critical

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.

comment:4 Changed 3 years ago by simko

`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.

comment:5 Changed 3 years ago by simko

  • Owner set to simko
  • Status changed from new to assigned

comment:6 Changed 3 years ago by simko

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

comment:7 Changed 3 years ago by simko

  • Status changed from assigned to in_work

comment:8 Changed 3 years ago by simko

  • Status changed from in_work to in_merge

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.

comment:9 Changed 3 years ago by simko

  • Resolution set to fixed
  • Status changed from in_merge to closed

comment:10 Changed 2 years ago by simko

  • Milestone v1.0 deleted

Milestone v1.0 deleted

Note: See TracTickets for help on using tickets.