Tom,

Wasn't aware of the Reading Radar portal - thanks for sharing that.

I've put an example of the php file (extension changed to .txt), along with
the stylesheet I'm using in the following directory on our webserver:

http://nc.ccrls.org/code4lib/

I was going to build a caching strategy into the php script itself, but
recently discovered that our webserver can do output caching.  So I'm
exploring that right now and want it working before this little project goes
live.  I think it will improve performance, since these pages don't have to
be up-to-the-minute current, and keep us well away from the NYT api limits.

My only lingering question is whether or not this setup compromises my
developer key.  I don't think it does, since that key is included in the php
file itself and isn't visible in the output.  However, if others detect an
issue here, I'd be grateful to hear about it.

Regards,

Doug


On Thu, Sep 29, 2011 at 4:27 PM, Tom Keays <[log in to unmask]> wrote:

> On Wed, Sep 28, 2011 at 5:38 PM, Doug Yancey <[log in to unmask]> wrote:
> >I just got this set up on our site, using php to parse the json response.
> > You should be able to see the result on our staging port at:
> >
> >http://catalog.ccrls.org:2082
> >
> >...under the 'Bestsellers' menu in the top nav bar.
>
> Nice. It reminds me of the Reading Radar portal, written using the
> Maintainable PHP Framework.
>
> http://readingradar.com/
> https://github.com/maintainable/framework
>
> >     would be happy to share that code with you, if you think it would
> >help.
>
> The author of Reading Radar described the structure of his mashup, but
> didn't follow up with any code. It would be great to see yours.
>
>
> http://jhherren.wordpress.com/2009/02/03/mashing-up-the-new-york-times-best-sellers-readingradarcom/
>
>
> On Wed, Sep 28, 2011 at 5:36 PM, Godmar Back <[log in to unmask]> wrote:
> >NYTimes could allow JSONP, but then developers would need to embed their
> API
> >key in their web pages, which means the API key would simply be a token
> used
> >for statistics, rather than for authentication. It's their choice that
> they
> >don't allow that.
>
> I saw several threads in the NY Times developer forum, one as far back as
> 2009, where a JSONP option had been promised by NY Times staff. It may not
> be coming.
>
> However, given that the API is read-only, I don't see the real consequence
> of using keys in the open.
>
>
> Tom
>



-- 
Doug Yancey
Chemeketa Cooperative Regional Library Service
Web Services Librarian
503.315.4268
Need support from CCRLS? Open a ticket at http://swhelpdesk.ccrls.org/portal