Le 20 déc. 09 à 23:04, Adam R. Maxwell a écrit :
>
> On Dec 20, 2009, at 1:09 PM, Miguel Ortiz Lombardia wrote:
>
>> Perhaps I would like to include some of the Mesh terms, but
>> definitely, not all or not in all cases, I will explore XML
>> processing for those as you suggest.
>
> Mesh term
On Dec 20, 2009, at 1:09 PM, Miguel Ortiz Lombardia wrote:
> Perhaps I would like to include some of the Mesh terms, but definitely, not
> all or not in all cases, I will explore XML processing for those as you
> suggest.
Mesh terms from MeshHeadingList are included by default, and the example
Le 20 déc. 09 à 21:50, Adam R. Maxwell a écrit :
On Dec 20, 2009, at 12:18 PM, Miguel Ortiz Lombardia wrote:
Hi Adam,
Le 20 déc. 09 à 20:57, Adam R. Maxwell a écrit :
These used to be mapped to 'Pst', which is still in use in the
MEDLINE format. That would be all right.
OK, done for th
On Dec 20, 2009, at 12:18 PM, Miguel Ortiz Lombardia wrote:
> Hi Adam,
>
> Le 20 déc. 09 à 20:57, Adam R. Maxwell a écrit :
>
> These used to be mapped to 'Pst', which is still in use in the MEDLINE
> format. That would be all right.
OK, done for the next nightly build. Thanks for the test c
Hi Adam,
Le 20 déc. 09 à 20:57, Adam R. Maxwell a écrit :
On Dec 20, 2009, at 11:48 AM, Miguel Ortiz Lombardia wrote:
Could I request the field that follows to be imported?
VALUE
where VALUE can be:
aheadofprint --> in press
ppublish --> printed
epublish --> electronic publi
On Dec 20, 2009, at 11:53 AM, Miguel Ortiz Lombardia wrote:
> It doesn't work for me. Even if I remove 'Pst' from the bogus list, it gets
> not imported. I presume that all those are simply ignored because in XML
> format they are already absent (with those names)
>
> I presume that a modified
On Dec 20, 2009, at 11:48 AM, Miguel Ortiz Lombardia wrote:
> Could I request the field that follows to be imported?
>
>
>
>
>VALUE
>
>
>
> where VALUE can be:
>
> aheadofprint --> in press
> ppublish --> printed
> epublish --> electronic publication (no paper version)
Do yo
Le 20 déc. 09 à 16:24, Mark Moll a écrit :
I wrote a little AppleScript that removes some of the bogus fields
that get imported from PubMed. I think I wrote this before the
switch to XML, so maybe it needs some minor changes. It still seems
to work just fine for me, though.
Paste this in
Hi Christiaan,
Le 20 déc. 09 à 15:52, Christiaan Hofman a écrit :
On Dec 20, 2009, at 14:15, Miguel Ortiz Lombardia wrote:
Hi everyone,
I wonder if something has changed in BibDesk 1.4 (or in PubMed, in
which case, of course you need not to know) with respect to the
import of publicatio
I wrote a little AppleScript that removes some of the bogus fields that get
imported from PubMed. I think I wrote this before the switch to XML, so maybe
it needs some minor changes. It still seems to work just fine for me, though.
Paste this in Applescript editor, save as, say, CleanPubMed.scpt
On Dec 20, 2009, at 14:15, Miguel Ortiz Lombardia wrote:
> Hi everyone,
>
> I wonder if something has changed in BibDesk 1.4 (or in PubMed, in which
> case, of course you need not to know) with respect to the import of
> publications found after a PubMed Search (within BibDesk). It seems that
Hi everyone,
I wonder if something has changed in BibDesk 1.4 (or in PubMed, in
which case, of course you need not to know) with respect to the import
of publications found after a PubMed Search (within BibDesk). It seems
that a lesser number of fields is imported now. One such field that i
12 matches
Mail list logo
