#506: Provide PS, type and field code searching
------------------------+----------------------
Reporter: tbrooks | Owner: valkyrie
Type: defect | Status: assigned
Priority: major | Milestone:
Component: WebSearch | Version:
Resolution: | Keywords: INSPIRE
------------------------+----------------------
Changes (by simko):
* status: in_merge => assigned
Comment:
1) You can make indexes by inserting proper configuration statements
to the top-level `Makefile`; see for example what I did earlier for
the "firstauthor" index. (INSPIRE repo, commit 2146ab19)
2) The journal index is already made, so you can test the journal
synonym searching (including volume and pages) even without creating
the other indexes. In the journal index synonym configuration, the
branch currently uses the massaging function `leading_to_number`, but
I think you should rather use `leading_to_comma`, because INSPIRE
convention for journal index is to separate //journal,volume,page//
values by commas. So with `leading_to_number`, journal searches
including volume and page would not work. For the two other indexes,
the `exact` massaging function seems appropriate.
3) For the two other classification/doctype indexes, we may perhaps
consider using the index-time synonyms instead of search-time
synonyms, especially if people are used to values like `E` from SPIRES
times.
4) But I'd like to clarify the terminology regarding
classification/doctype indexes first.
WRT "classification" KB, it generates values for 65017 field which is
called "subject" in cataloguing tools. How do we want to call the new
index in the user facing parts of INSPIRE, "classification" or
"subject" or "fc" or something else? Consider that people may be
typing and/or seeing query terms like `classification:E` or
`classification:"Experiment-HEP"`, so we'd better choose something
nice. Maybe stick to "subject" like in cataloguing tools, maybe stick
to "fc" if we choose this to be the user-facing canonical index name
and not only an alias, etc.
WRT "doctype", there is a similar naming mismatch. Moreover, here the
word doctype has a very concrete meaning in Invenio, namely the type
of a document attached to a record. So it may be misleading to call
it that. (BTW, see also somewhat related filetype/doctype index issue
in ticket:473.)
5) When updating KB/index names, we may want to amend the following
description `TALKTYPEDESC='Mapping of... something?'` a bit. :)
6) You should also document in the commit log the weblinks/oalinks fix
done alongside the process. Ideally, we should perhaps separate this
fix into a commit of its own, since it is unrelated to synonym KBs.
--
Ticket URL: <http://invenio-software.org/ticket/506#comment:3>
Invenio <http://invenio-software.org>
