Am 20.06.2011 14:20, schrieb Tibor Simko:
Hi!
On Mon, 20 Jun 2011, Christopher Dickinson wrote:
Also, the MySQL query looks for "='Ellis'" if you have "Ellis" in the
Author field, "LIKE 'Elli%'" if you have "Elli%" in the Author
field. I'm not sure if that's what we want...
When the user is located in the 100__a box in BibEdit and types `elli'
followed by `C-S-a' hot key combination,
I know your're all die hard EMACsers, but maybe one could come up with
something easier to type and remember. I guess for our end-cataloguers
GUI wise a button to click is also convenient besides the shortcut. It
could e.g. show the shotcut as tooltip.
then the auto-suggest facility
should look for `elli%' from the SQL point of view. (`%' is the wild
card, so `elli%' means auto-completion at the end.) However, there are
other auto-suggestion use cases where it would *not* be desirable to do
this, e.g. auto-completion of institutions happens by matching words in
any field anywhere (e.g. I type `geneva' and system replies `cern'). So
this must be made configurable depending on the concrete auto-suggest
use case. E.g. 100__a -> autosuggest_via_phrase_endings(), 245__a ->
autosuggest_via_word_anywhere(), 65017a -> autosuggest_via_authority(),
etc. That is, CFG_BIBEDIT_AUTOSUGGEST_TAGS should be extended to say
also how we auto-suggest for various tags.
Additionally, I may mention that you shouldn't have John Ellis in mind
for autocomplete. He is trivial.
Think more in the direction of John Smith, Hans Müller or the like, that
is your autosuggest list looks like:
Smith <C-S-a>
Smith, John
Smith, John
Smith, John
How to disambiguate them? I think therefore you have to return more than
one field. And it has to populate more than one field. E.g.
100 $a Smith<C-S-a>
has to result in
100 $a Smith, John
$0 PER:12345
where the $0-field to be populated is imperative.
From our discussion at OAI7 for our local use case one could
disambiguate the Smiths above by the email-field or the phone number
e.g. the authority record in question may well look like:
<some other fields>
024 7_ $2 PER $0PER:17710
024 7_ $2 PND $0PND:1234567X
100 __ $a Smith, John
371 __ $m [email protected]
$a Building 7.13, R-123
$v LDAP
$s 01.01.2000
980 __ PER
<some other fields>
<some other fields>
024 7_ $2 PER $0PER:15510
024 7_ $2 PND $0PND:1200123
100 __ $a Smith, John
371 __ $m [email protected]
$a Building 7.13, R-123
$v LDAP
$s 01.01.1990
$t 01.01.1998
980 __ PER
<some other fields>
and one could use 371 $m for the disambiguation. The above would then
look like
Smith <C-S-a>
Smith, John ([email protected] : 01.01.2000--)
Smith, John ([email protected] : 01.01.1990--01.01.1998)
Smith, John ([email protected] : 01.01.2000--)
BTW: it makes sense at some point to extend dup checking to 024 fields
as they accumulate a number of identifiers. Putting them all to 035
isn't good compared with regard to the Marc Standard and repeating them
isn't either.
--
Kind regards,
Alexander Wagner
Subject Specialist
Central Library
52425 Juelich
mail : [email protected]
phone: +49 2461 61-1586
Fax : +49 2461 61-6103
http://www.fz-juelich.de/zb/mitarbeiter/fachinformation#wagner
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDirig Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Besuchen Sie uns auf unserem neuen Webauftritt unter www.fz-juelich.de
