LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  December 2017

CODE4LIB December 2017

Subject:

Re: `APIs for Librarians` -- A thing I've been doing that I'd like to share with you all

From:

Brad Coffield <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 20 Dec 2017 14:03:29 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (213 lines)

That's a great point Joel, thanks for that.

Also, if you wanted (and think it would be helpful to others), I'd love to
add your project to the site (and give you credit of course). Let me know
if you're interested!

Brad

On Wed, Dec 20, 2017 at 10:48 AM, Joel Marchesoni <[log in to unmask]>
wrote:

> One would need to be careful in LibApps (LibGuides, LibCal, etc) when
> setting the scope for the "application" that gives you the client id and
> secret. You could easily set it to have write access, in which case that
> id/secret pair will let anyone change your data.
>
> I just finished (to beta at least) a project using the LibCal API, and
> decided to keep my id and secret in a PHP file that returns an OAuth token.
> Here's a Stack Overflow answer showing the basic PHP code that can be used
> to make the request:
>
> https://stackoverflow.com/questions/2138527/php-curl-
> http-post-sample-code#2138534
>
> Joel Marchesoni
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Tom Keays
> Sent: Friday, December 15, 2017 14:28
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] `APIs for Librarians` -- A thing I've been doing
> that I'd like to share with you all
>
> If I'm building an app using an API that allows the full range of CRUD
> operators to be performed, there's going to be some authentication needed
> to allow that. I'd enclose all that in, say, a PHP wrapper so the calls and
> authentication details are safely hidden.
>
> If the API is just read-only, like the LibApps APIs, then there is less
> concern about exposing the keys. With LibApps, the "keys" are just
> identifiers so you know what library, what service, etc.
>
>
> On Fri, Dec 15, 2017 at 9:50 AM, Cynthia Harper <[log in to unmask]> wrote:
>
> > Would I be correct in my understanding that if you require hiding the
> > data in POSTs, you cannot do that in straight browser Javascript, but
> > would require some server-side coding?
> >
> > Cindy
> >
> > -----Original Message-----
> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> > Brad Coffield
> > Sent: Friday, December 15, 2017 9:33 AM
> > To: [log in to unmask]
> > Subject: Re: [CODE4LIB] `APIs for Librarians` -- A thing I've been
> > doing that I'd like to share with you all
> >
> > Hi Randy,
> >
> > Good question. In this case, it does seem to be acceptable to use it
> > in such a public way. They do seem to be rolling out changes to
> > authentication for certain portions of their APIs. For instance, in
> > LibGuides, if you want to work with AZ resources (typically your
> > database list) you need to use oauth. "The LibApps v1.2 API uses oAuth
> > 2.0 for authentication and supports the Client Credentials grant
> > type." It supports GET and POST. Their other endpoints are all GET,
> > and working with them in the above way is acceptable. My guess is
> because they are all GET, but I don't know.
> >
> > Have a good one!
> >
> > Brad
> >
> > On Fri, Dec 15, 2017 at 9:12 AM, Stern, Randy
> > <[log in to unmask]>
> > wrote:
> >
> > > Hi Brad,
> > >
> > > This looks like a useful resource. I do have a question. Not knowing
> > > much about Springshare APIs, I see that your example includes a line
> > > of code
> > >
> > > $.getJSON('https://lgapi-us.libapps.com/1.1/guides?site_
> > > id=foo1&key=foo2&status=1', function (result) {
> > >
> > > that seems to expose a key (foo2) to public viewing. Is that key
> > > supposed to be a secret key that is not made public? Or is it OK to
> > > have it publicly exposed?
> > >
> > > - Randy
> > >
> > >
> > >
> > > Date:    Thu, 14 Dec 2017 08:46:40 -0500
> > > From:    Brad Coffield <[log in to unmask]<mailto:
> > > [log in to unmask]>>
> > > Subject: Re: `APIs for Librarians` -- A thing I've been doing that
> > > I'd like to share with you all
> > >
> > > Happy to hear it! If I can help at all, feel free to email me directly.
> > >
> > > Brad
> > >
> > > On Thu, Dec 14, 2017 at 2:03 AM, Patricia Farnan <
> > > [log in to unmask]<mailto:[log in to unmask]>>
> > > wrote:
> > >
> > > Hi,
> > >
> > > This looks like a great resource for someone like me who isn't a
> > > developer but wants to learn more about making use of APIs. Thanks
> > > for
> > sharing!
> > >
> > > Patricia Farnan  | Application Administrator, Discovery Services
> > > University Library  | St Teresa’s Library
> > >
> > > Telephone: +61 8 9433 0707 | Email: [log in to unmask]<mailto:
> > > [log in to unmask]>
> > >
> > > -----Original Message-----
> > > From: Code for Libraries [mailto:[log in to unmask]] On Behalf
> > > Of Brad Coffield
> > > Sent: Tuesday, 12 December 2017 3:53 AM
> > > To: [log in to unmask]<mailto:[log in to unmask]>
> > > Subject: [CODE4LIB] `APIs for Librarians` -- A thing I've been doing
> > > that I'd like to share with you all
> > >
> > > Hi everyone,
> > >
> > > I want to help people easily use web APIs to enhance their library
> > > websites and/or research guides. So, I made a site that has
> > > copy/pasteable code along with instructions on how to implement it
> > > (like what exactly to change in the code to make it work with their
> > > libguides system, for example).
> > >
> > > It's a project in ongoing development and I wanted to share it with
> > > you all
> > > because:
> > >       * You're nifty
> > >       * Some (hopefully many!) of you might be interested in using
> > > some of my code
> > >       * Some of you might be interested in contributing new pieces
> > > to the site
> > >
> > > Currently I have implementations for various Springshare products,
> > > Quotes.net, and a variety of collections from the Internet Archive.
> > > I have plans on making things for the New York Times, Wordnik, OCLC,
> > > and Chronicling America (from LOC).
> > >
> > > Would love to hear comments. I hope you like it.
> > >
> > > https://www.bradcoffield.com/APIs-for-librarians/
> > >
> > >
> > > Brad
> > >
> > >
> > > --
> > > Brad Coffield, MLIS
> > > Assistant Information and Web Services Librarian Saint Francis
> > > University
> > > 814-472-3315 <(814)%20472-3315>
> > > [log in to unmask]<mailto:[log in to unmask]>
> > > IMPORTANT: This e-mail and any attachments may be confidential. If
> > > you are not the intended recipient you should not disclose, copy,
> > > disseminate or otherwise use the information contained in it. If you
> > > have received this e-mail in error, please notify us immediately by
> > > return e-mail and delete or destroy the document. Confidential and
> > > legal privilege are not waived or lost by reason of mistaken
> > > delivery to you. The University of Notre Dame Australia is not
> > > responsible for any changes made to a document other than those made
> > > by the University. Before opening or using attachments please check
> > > them for viruses and defects. Our liability is limited to
> > > re-supplying any
> > affected attachments.
> > >
> > >
> > >
> > >
> > > --
> > > Brad Coffield, MLIS
> > > Assistant Information and Web Services Librarian Saint Francis
> > > University
> > > 814-472-3315
> > > [log in to unmask]<mailto:[log in to unmask]>
> > >
> > > ------------------------------
> > >
> > >
> >
> >
> > --
> > Brad Coffield, MLIS
> > Assistant Information and Web Services Librarian Saint Francis
> > University
> > 814-472-3315
> > [log in to unmask]
> >
>



-- 
Brad Coffield, MLIS
Assistant Information and Web Services Librarian
Saint Francis University
814-472-3315
[log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager