So is this something that ADS should/could fix? Admittedly, I know very little about how this works, but it seems from the ADS record syntax, that they support several different return formats including SUTRS and some form of XML. Now if the XML they're returning is nonsensical, then maybe it's something ADS could fix. Or maybe they could add a syntax which more closely matches something the parser in BibDesk is used too.
I'll be happy to contact them to see if they could help out from their end. Cheers, Andy from the Server Config Outline: Record Syntax Supported Value Description Databases -------------------------- --------------- --------- 1.2.840.10003.5.101 SUTRS Records All 1.2.840.10003.5.109.3 HTML Records All 1.2.840.10003.5.109.10 XML Records All 1.2.840.10003.5.1000.147.1 ADS Tagged Records All On 8/11/2007, at 12:11 PM, Adam R. Maxwell wrote: > > On Wednesday, November 07, 2007, at 04:44PM, "Adam R. Maxwell" > <[EMAIL PROTECTED]> wrote: >> >> On Wednesday, November 07, 2007, at 04:01PM, "Christiaan Hofman" >> <[EMAIL PROTECTED]> wrote: >>> It's not returning any format BibDesk can parse. Either it returns >>> SUTRS, which is a another word for junk, or it returns a sort of >>> hybrid Dublin Core XML, but not in a form we can recognize. >> >> I can't even get it to work with the test app; have you? I've >> tried various encoding, syntax, and database combinations without >> success. If the thing actually returns XML there's chance we can >> parse it, or use the yaz XML conversion. > > Never mind...our list archives reveal that you can use au=someone > to get results back. Anyway, it's returning is DC XML as > Christiaan said, but it's only returning XML fragments, so our > current DC XML parser would choke on it. If we strip the dc: > namespace and tidy the XML, it's parseable, but we'd have no way to > recognize the format. > > I wrote the current DC XML parser as a special case to deal with > COPAC, but as far as I know it's no longer used since COPAC > switched to MODS. Hence we could conceivably turn it into a > special-case parser for ADS instead, and not really lose anything. > It's annoying that the journal, volume, issue, and page range are > all part of the <source>. > > -- > adam > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
