I was the person who needed the answer. I am not the module author. I
took over maintaining it when the original author moved on to other things
and the process has been an education in writing software.
I would suggest that you change the line from AST to ALL. That will search
the PRE, AST and any other database they have configured.
best of luck,
Boyd
On 20 June 2014 14:36, Van Orsow, Doug J.[INNOVIM] via RT <
bug-Astro-ADS@rt.cpan.org> wrote:
Show quoted text> Queue: Astro-ADS
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=96573 >
>
> Hi Boyd,
>
> Thanks for the quick response. Yes, it is a funny coincidence how this
> same question came up for you recently. Maybe another "bibliographer"
> from another archive asked you about it?
>
> In any case, I also saw that one-line option of setting the db_key to
> AST, so just wondered if it could easily be changed to PRE in order to
> access the pre-print ADS archive? Does setting it to ALL actually access
> the PRE archive as well, or just other databases of AST?
>
> Glad to hear you are busy with a thesis, and planning to write a new
> module for next year. I do have a workaround for my request, by just
> plugging my monthly list of arXiv bibcodes into to the ADS search page.
> It just involves some extra editing work on my part, that the modules
> would do for me. So unless there is an easy way to change (as if it's
> ever easy) the options for db_key, I think freezing development of this
> module is fine.
>
> Cheers,
> Doug
>
>
> On 6/20/14 4:43 AM, Boyd Duffee via RT wrote:
> week.
> > It's hardcoded in on line 660 of Query.pm
> > ${$self->{OPTIONS}}{"db_key"} = "AST";
> > I believe PRE will just look at the pre-prints, whereas ALL will search
> all
> > databases (it's the one I'm using now).
> >
> > I'm a little uncertain of how I should proceed as module maintainer. The
> > API for ADS is changing and this interface will be dropped at some future
> > date. I've got a thesis to submit this year, so I'm planning on writing
> a
> > module for the new API in 2015. I was considering just freezing
> > development of this module. Do you have any opinion on the matter?
> >
> > cheers,
> > Boyd Duffee
> >
> >
> > On 20 June 2014 01:21, Van Orsow, Doug J.[INNOVIM] via RT <
> > bug-Astro-ADS@rt.cpan.org> wrote:
> >
> >> Thu Jun 19 20:21:11 2014: Request 96573 was acted upon.
> >> Transaction: Ticket created by doug.j.vanorsow@nasa.gov
> >> Queue: Astro-ADS
> >> Subject: Astro::ADS
> >> Broken in: (no value)
> >> Severity: (no value)
> >> Owner: Nobody
> >> Requestors: doug.j.vanorsow@nasa.gov
> >> Status: new
> >> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=96573 >
> >>
> >>
> >>
> >> Dear Astro::ADS author,
> >>
> >> I would like to query the PRE database (instead of the default AST
> >> database) for arXIV papers using:
> >>
> >> Astro::ADS::Query
> >> Astro::ADS::Result::Paper
> >> Astro::ADS::Result
> >>
> >> I apologize since this is not a bug, but a request.
> >>
> >> Please advise, best regards,
> >>
> >> Doug van Orsow
> >>
> >> --
> >> ------------------------------------------------------------------------
> >> Doug van Orsow (Vantage Systems, Inc.) Bldg 22 Rm 5
> >> Doug.J.vanOrsow@nasa.gov
> >> HEASARC/LHEA, Code 660.1 Tech Specialist Voice: 1 301 286-8412
> >> NASA/GSFC, Greenbelt MD 20771 HEASARC Archive Fax: 1 301 286-1215
> >> ------------------------------------------------------------------------
> >>
> >>
> >>
> >
>
>
> --
> ------------------------------------------------------------------------
> Doug van Orsow (Vantage Systems, Inc.) Bldg 22 Rm 5
> Doug.J.vanOrsow@nasa.gov
> HEASARC/LHEA, Code 660.1 Tech Specialist Voice: 1 301 286-8412
> NASA/GSFC, Greenbelt MD 20771 HEASARC Archive Fax: 1 301 286-1215
> ------------------------------------------------------------------------
>
>
>
--
Boyd Duffee
"Note that some bugs were inadvertently discovered and fixed during this
process"
- fortune(6) manual page
