Sorry, my "second e-mail" never reached you, since I sent it from the wrong address... It said:
> More on this: > > I don't think anything has to be done in BibDesk but waiting for the > PubMed to repair itself. It seems that the problem is with some of > the newest entries in PubMed. For example, if you go for PMID > 19120484 in the NCBI site you get: > > id: 19120484 Error occurred: The following PMID is not available: > 19120484 > Recent Activity > > This corresponds to a paper published very recently (this year). If > the first entry in a search includes a reference to a cite affected > by this problem (very likely unless nothing related to the search > was published since the beginning of the year), then BibDesk fails > to import anything. I guess it isn't easy to ask BibDesk to simply > ignore those entries and go for the rest, so we can better wait to > see if PubMed gets cured. Cheers, Miguel Le 6 janv. 09 à 12:21, Christiaan Hofman a écrit : > I have no problem searching pubmed with the latest release, so it's > almost certainly a connection problem on your side. Is there anything > in the console logs? > > Christiaan > > On 6 Jan 2009, at 11:20 AM, Miguel Ortiz Lombardia wrote: > >> Hi, >> >> First of all, thank you to all of you for your efforts in making >> BibDesk such a useful application. I wish I could do more programming >> myself to help. >> >> Now, yet a new problem with PubMed... Today searches on PubMed from >> within BibDesk are failing with the error: >> >> Incorrect result type >> >> If you stubbornly repeat the search, then you can see in the status >> bar (well, the bottom bar, sorry not sure how you call it) that the >> correct number of matches were found, but 'Some results could not be >> parsed'. Since I can see these results properly in my web browser >> if I >> search directly in the PubMed site, I presume that, as the first >> error >> message said, this is probably a problem with the server, they may >> have changed again their formats... My question is: could you please >> tell me how to debug this problem? I would like to help with any >> information you may find useful. >> >> This problem happens with both BD 1.3.19 and the latest available >> nightly build (from 2008-12-23, the nightlies built after that date >> seem to have failed) >> >> Best regards, >> >> >> Miguel >> >> Le 6 janv. 09 à 03:41, Gregory Jefferis a écrit : >> >>> On 2009-01-05 10:50, "Christiaan Hofman" <cmhof...@gmail.com> wrote: >>> >>>> No, those unit tests are far out of date, and I'm pretty sure they >>>> won't even compile. >>> >>> Yes indeed the first ones that I tried (TestBibItem) don't compile. >>> >>>>> I see that there are some Unit Tests in the BibDesk project that >>>>> have been >>>>> untouched since about Jan 2005. They currently use the UnitKit >>>>> framework >>>>> that is no longer being developed. It looks like Mike McCracken >>>>> had >>>>> a go at >>>>> switching to the SenTestingKit (aka OCUnit) framework that is now >>>>> bundled >>>>> with Developer Tools. >>>>> >>>>> http://bibdesk.svn.sourceforge.net/viewvc/bibdesk/trunk/? >>>>> pathrev=1264 >>>>> >>>>> With commit message: >>>>> >>>>> Tried to rewrite Test stuff, failed for now due to dependencies >>>>> >>>>> Does anyone know what the problem here was? >>> >>> I have tried translating the first part of the TestBibItem to the >>> new >>> SenTesting framework without any issues. I have also started >>> writing some >>> test cases for the PubMed parser. I think that the use of test >>> cases for >>> the various parsers would really reduce the amount of time spent >>> tracking >>> down/fixing bugs like the PubMed -> BibTex year bug that I have >>> recently >>> written about. That would surely be good news for everyone. >>> >>>> I'm not gonna bother with them anyway. I'm seriously building down >>>> development efforts for BD, and there's nobody to take over. So >>>> it's >>>> perhaps a bit academic. >>> >>> I'm sorry to hear that, but I can understand that the time >>> commitment could >>> get too heavy - I count 4764 svn commits in my checkout. I wonder >>> though if >>> you could scale back your efforts to concentrate on core issues >>> while >>> leaving fixes for stuff you don't use to others - it might make the >>> work >>> that you do more enjoyable. And I think there are a few people out >>> there >>> like myself capable of making small contributions to the areas that >>> we care >>> about. >>> >>> Incidentally, re the discussion about Unit tests, it seems to me >>> that adding >>> more unit tests would have the additional benefit of making it a bit >>> safer >>> for new people to make code modifications. >>> >>> Best wishes, >>> >>> Greg. >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Bibdesk-develop mailing list >>> Bibdesk-develop@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Bibdesk-develop mailing list >> Bibdesk-develop@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bibdesk-develop mailing list > Bibdesk-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop