>>
>> My workflow is:
>>
>> go to journal e.g. Phys. Rev. B, find article. Download pdf.  
>> Meanwhile, at the button marked article options, select "view  
>> bibtex". (Other journals do this differently, but get yourself to  
>> the same state.) This goes to a new browser page with the bibtex  
>> entry for the paper. Shade the bibtex.
>>
>> Go to apple menu, top left, scroll down to Services. First entry is  
>> BibDesk, across to "add to Bibliography." Selected bibtex from  
>> webpage is parsed, and added to currently open Bibdesk archive.  
>> Drag and drop pdf from downloads folder to sidebar of Bibdesk item  
>> window, which has automatically opened on import, which then  
>> autofiles the pdf to your preferred pdfs folder. This is then  
>> searchable in Spotlight, and a link to the journal webpage is then  
>> available, via the URL or the DOI from the bibtex.
>>
>>
>> However, for some reason, BibDesk is no longer putting the contents  
>> of the doi: field into the Doi: field in my bibtex archive.  It  
>> used to, before 1.3.15. is there some problem with case  
>> sensitivity? If I added a "doi" field as well as a "Doi" field,  
>> would that work? It seems to know that it is a DOI, as when I paste  
>> in the DOI, a link appears in the sidebar to dx.doi.org/<DOI>.
>>
>> James
>
> That question has been answered several times on this list,  
> including very recently.

No, I don't think it has. This is not about the long discussion of  
pasting a DOI into the sidepane. It is simply a question about the  
import triggered by the BibDesk Service "Add to Bibliography" as in  
the workflow mentioned earlier. In the past, the BibTeX field
doi = {10.1063/1.1884596} would appear in the imported item. Today, I  
noticed that it no longer did.

e.g. looking at the raw BibTeX from the journal webpage,
@article{wang:164706,
author = {Yun Wang and Gyeong S. Hwang},
collaboration = {},
title = {Origin of nonlocal interactions in adsorption of polar  
molecules on Si(001)-2 x 1},
publisher = {AIP},
year = {2005},
journal = {The Journal of Chemical Physics},
volume = {122},
number = {16},
eid = {164706},
numpages = {9},
pages = {164706},
keywords = {silicon; adsorbed layers; water; ammonia; organic  
compounds; adsorption; density functional theory; hydrogen bonds;  
surface phase transformations; surface chemistry; dissociation},
url = {http://link.aip.org/link/?JCP/122/164706/1},
doi = {10.1063/1.1884596}
}

after import, this has become:

@article{wang:164706,
        Author = {Wang, Yun and Hwang, Gyeong S.},
        Date-Added = {2008-05-09 09:02:03 +0200},
        Date-Modified = {2008-05-09 09:02:03 +0200},
        Eid = {164706},
        Journal = {The Journal of Chemical Physics},
        Keywords = {silicon; adsorbed layers; water; ammonia; organic  
compounds; adsorption; density functional theory; hydrogen bonds;  
surface phase transformations; surface chemistry; dissociation},
        Number = {16},
        Numpages = {9},
        Pages = {164706},
        Publisher = {AIP},
        Title = {Origin of nonlocal interactions in adsorption of polar  
molecules on Si(001)-2 x 1},
        Volume = {122},
        Year = {2005},
        Bdsk-Url-1 = {http://link.aip.org/link/?JCP/122/164706/1},
        Bdsk-Url-2 = {http://dx.doi.org/10.1063/1.1884596}}


So the doi field (and the url field), which can in principle be parsed  
by any bibtex program, e.g. Jabref, has now been converted into the  
Bdsk-URL-2 field, which is not a standard field name as far as I know.  
It is particular to BibDesk, and thus a step away from maintaining  
standard bibtex as the file structure. "Embrace and Extend" one might  
say.

Also this screws up my html templates for producing webpages.
One line in the template is:
        <$fields.Doi?> <span class="url"><a href="http://dx.doi.org/< 
$fields.Doi/>"><$fields.Doi/></a></span> </$fields.Doi?>

which produces the DOI (without the http://dx/doi.org/ and thus much  
more compact) as a clickable link. I would have to find some way, such  
as the Applescript mentioned somewhere earlier, to get back to what I  
used to have.

In the mailing list, recently, Adam Maxwell says:
 >> If you consider Doi and Url as legacy fields, it might make more
 >> sense; in general, you should only use Url if it's part of the  
BibTeX
 >> type. Doi is an ugly special case; the Doi field does some magic to
 >> convert it to a resolvable URL.

I interpret this to mean that just as the remote-URL field has become  
deprecated in favour of links appearing in the sidebar, so now the  
same has happened to the DOI field. I think this is a retrograde step.

While it is nice that BibDesk does some magic to create a resolvable  
URL in the sidebar from the Doi field, that should not come at the  
expense of deleting the Doi field altogether from the raw BibTeX. It  
is unnecessary, and reduces interoperability with colleagues, who may  
not be using BibDesk. Now I have no problem with BibDesk adding  
fields, in order to give extra functionality, but I don't like that  
BibDesk is actually deleting fields from imported bibtex, even if they  
are considered legacy fields. Far better to leave them there in the  
raw BibTeX, but ignore them.

Yours,

James
















-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to