#561: Extreme compound surname has problems
------------------------+----------------------------
Reporter: hoc | Owner: valkyrie
Type: defect | Status: assigned
Priority: minor | Milestone:
Component: WebSearch | Version:
Resolution: | Keywords: INSPIRE syntax
------------------------+----------------------------
Changes (by jblayloc):
* owner: => valkyrie
* priority: major => minor
* status: new => assigned
Comment:
You want your mind blown?
Try:
fin a do Couto e Silva,
[works]
The easiest thing may be to train the users to behave differently. But
there may be something we can do with the syntax parsing; I haven't looked
into it yet. But predicting which components of the name are firstname,
which are lastname, and which are middle names, deciding which middle
names to use as names and which middle names to use as initials, is
complicated. I think the current behavior may be the natural result of
tradeoffs we've chosen to make in other areas.
The safest most conservative thing is always lastname-first, (firstname
optional). The comma signals to the search interpreter that everything up
to the comma is a lastname and should all be taken together. So, to users
Heath you can say that this is not unexpected behavior, because of the
significant differences in the way that SPIRES and INSPIRE handle data (I
can elaborate but bet you'd rather I didn't.)
However, I'll leave this ticket open because Valkyrie is smarter than me
and maybe she can think of some clever way to make this behave properly.
--
Ticket URL: <https://invenio-software.org/ticket/561#comment:1>
Invenio <http://invenio-software.org>
