On Apr 13, 2014, at 17:08, Colin A. Smith wrote:

> On Apr 13, 2014, at 10:30, Christiaan Hofman <[email protected]> wrote:
> 
>> On Apr 13, 2014, at 10:24, Colin A. Smith wrote:
>> 
>>> On Apr 12, 2014, at 17:09, Christiaan Hofman <[email protected]> wrote:
>>> 
>>>> On Apr 12, 2014, at 15:38, Colin A. Smith wrote:
>>>> 
>>>>>> On Apr 12, 2014, at 14:46, Christiaan Hofman <[email protected]> wrote:
>>>>>> 
>>>>>> As for the alternate operations, I am not completely sure about it, 
>>>>>> though I guess something like citations can be useful. I hate the syntax 
>>>>>> as it now is: the prefixes are far too long, and the syntax is 
>>>>>> inconsistent, and using ":" is wrong IMHO because that character also 
>>>>>> occurs in the UID. I propose to use something that looks more like the 
>>>>>> search syntax, by devising some alternate "search fields", for instance 
>>>>>> CITED=, CITING=, REL=, and UID=. Those are all unused.
>>>>> 
>>>>> I don't have any strong preferences about the syntax. I think CITEDBY is 
>>>>> less ambiguous than CITED, though two characters longer. I think CITING 
>>>>> is good, and that's the only one I really care about.
>>>>> 
>>>>> Cheers,
>>>>> 
>>>>> Colin
>>>> 
>>>> What about REF= and CIT= for references (citedReferences) and citations 
>>>> (citingArticles)?
>>> 
>>> I think those are even more ambiguous. For something that would in most 
>>> cases be generated by a script, I think it's more important to be self 
>>> explanatory than concise.
>>> 
>>> Cheers,
>>> 
>>> Colin
>> 
>> 
>> I think that is a bit contradictory. Especially when they would be generated 
>> by a script it really would not matter much what they are, including 
>> ambiguous, because the user doesn't need to remember them. On the other 
>> hand, you seem to be too much looking at your own individual use rather than 
>> the general use, as I doubt this would in most cases come from a script. I 
>> think it is more important to be concise and consistent.
>> 
>> Christiaan
> 
> 
> If I have two scripts next to each other in a menu that do each operation, 
> and I happen to run both (or I slip and am not sure which one I ran), I’d 
> like it to be clear and unambiguous which one was run, without having to 
> remember what each means.
> 
> I have thought about use cases that don’t involve scripts. If you have two 
> search terms, “REF” and “CIT”, and you’re trying to remember which means look 
> up papers that cite a given Wok-Uid, and which one means look up papers that 
> are cited by a given Wok-Uid, then I don’t see an obvious way of knowing 
> which is which, beyond memorization.   At least to me, “reference” and “cite” 
> (or “referencing” or “citing”) are fairly, perhaps not exactly, synonymous. 
> Using abbreviations of reasonably synonymous words to represent very 
> different things seems like a recipe for confusion to me, and not very 
> consistent.
> 
> Cheers,
> 
> Colin

The problem with that is that this applies to all terms. All terms can be 
interpreted always ambiguously two ways (from the point of view of the items 
you search for the items from which you search). So this cannot be avoided. So 
you always have to somehow remember. Also, all the search terms in WOK searches 
are not clear, they are all very short (usually two letters) that you just 
should know. So if you just remember what they stand for, like "references" and 
"citations" (for the item), I think it really makes sense. The thing is, as 
soon as I try to think of any action term (like citing or cited-by) I get 
confused, as I don't know from which POV I should interpret that (items citing 
this item or items that this item are citing?) I don't get this confusion when 
I think of it in terms of "references" and "citations". And "ref" and "cit" are 
actually very common shorthands for those terms.

Christiaan

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

Reply via email to