On Apr 14, 2014, at 13:45, "Colin A. Smith" <[email protected]> wrote:
> On Apr 14, 2014, at 14:12, Christiaan Hofman <[email protected]> wrote: > >>> Perhaps there was a miscommunication. Typing “CIT=“/“REF=“ vs. >>> “CITING:”/“CITEDBY:” is a difference of 3-4 characters. I would assume that >>> the vast majority of users not using a script would copy and paste the >>> Wok-Uid, which I believe we agreed would include the “WOS:” prefix. That’s >>> why I think with either syntax, users will still have a copy/paste >>> operation, leaving the sole difference being the 3-4 characters of >>> additional typing. >> >> I still think that's far too many, because it is a repeating thing, not a >> one-time thing. It's extra work without any real functional improvement. > > 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. Even if it was rate limiting, > I don’t think the extra time is worth the loss in clarity. Speaking of creating a new search group, what about having preconfigured search groups for these options, so the user does a "WOK Cited By" search group, then just enters the UID by itself? I haven't followed what happened with databases etc., so maybe it's not tenable…but something like this would be more discoverable and self-documenting. > 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. I'm trying to keep my nose out of this debate, but I'm inclined to agree that saving keystrokes is not a useful goal in this day and age, whether it's for variable/function/method names or keywords like this. If brevity is a big deal, I'd go for something like CTB vs. CIT for cited by, but cryptic commands are only useful if you use them all the time. For occasional or new users, a GUI would be nice. Some years ago I started on an NSTokenField UI for search groups, but NSTokenField sucked so bad that I gave up. Not sure it was ever improved. Adam
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ 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
