On Apr 15, 2014, at 9:50, Colin A. Smith wrote:
> On Apr 14, 2014, at 23:21, Christiaan Hofman <[email protected]> wrote:
>
>> On Apr 14, 2014, at 22:45, Colin A. Smith wrote:
>>
>>> I think typing is by far the least rate limiting step of performing the
>>> search, compared with (potentially) creating a new search group, copying
>>> the Wok-Uid, then pasting it into the search field.
>>
>> You are forgetting the very important issue of frequency.
>
> I am not forgetting about frequency. I’ve been using this feature for years
> now so at least have some idea about frequency in my own case, although I
> could imagine someone using it much more than I do. I’ve also considered
> other examples (i.e. Google) where the frequency is many time greater but
> similar length text tokens are used.
>
Well, you use a script, you don't type it. This is not typical use.
>> The whole point is that searching is the thing you do many times. Setting up
>> the search group is something you do only a limited time. Typically once,
>> ever.
>
> My external search group instances go away every time I quit BibDesk. Also,
> perhaps you assume that users only ever use a single instance for a given
> type of search group. That’s not the case, at least for me. I don’t like
> losing previous search results, so use multiple WOS instances, much like tabs
> in a web browser.
I think you did not understand what I said, as this does not bear on this at
all. I am not assuming there is a single *instance* of the search group, I am
assuming that there is a single *template*, i.e. a series of settings. So I
make the distinction between the group settings (from the setup sheet) on the
one hand, and an instance in which you type some search term. The first thing
is something you do rarely, ever, because you're supposed to save them in a
default server or bookmark when you're using it often, while the latter is
something you do often (even if you have different instances, you do it every
day.) that's why for the latter it is more important to be efficient than for
the former.
>> Quite frankly, I just used it very few times for testing. And I was very
>> quickly getting annoyed a lot by the very long text I had to type in the old
>> format.
>
> I heartily agree that the long format was too long for typing.
>
>>> It’s worth pointing out that the Google engineers had almost the exact same
>>> choice as we’re making. When they chose to use “related:” to be the syntax
>>> for finding pages similar to another page, they could have chosen “rel:”,
>>> as is currently implemented in BibDesk. In the choice between 3 vs. 7
>>> characters, 7 clearly won out. I’d guess that the “related:” Google
>>> operation is used several orders of magnitude more times every day than all
>>> of the WOK search operations will ever be performed in the lifetime of
>>> BibDesk. If there were a compelling reason to shorten the syntax anywhere,
>>> it would be there.
>>>
>>> Cheers,
>>>
>>> Colin
>>
>> The fact that they did does not mean it's the best choice. Moreover they
>> have a different context, like user base and versatility of search
>> operations.
>
> Based on my experience, I would assert that the average researcher is not
> that much more advanced or different than the average Googler. In the web
> version of WOK, they’ve totally done away with the ability to type in
> advanced queries like you can still do in BibDesk. They now require selecting
> options from a menu based interface, which I think takes at least as long as
> typing a several characters.
>
> Cheers,
>
> Colin
Anyway, I am thinking of following your recommendations anyway, it seems to
work acceptably in small caps.
Christiaan
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop