By "developer tools" i just meant your browser tools for looking at the DOM, JS console etc, which differ by browser but generally you can get to via F12.
As for working with the API, EBSCO has some info up at the EDS Wiki and you can also contact their support for more help. i believe they're created some videos showing how to get started but not sure where those are housed. It's not clear to me from your context if you could get away with doing something very simple, in which case you can use EBSCO's "gateway" site that makes things very easy such that if you are comfortable working with JSON responses you can actually do everything in javascript, or if you need to do something more full-blown with server-side processing. EBSCO has a sort of EDS API test site you can get to straight from EBSCOadmin where you can look at the JSON (or, if you prefer, XML) responses to get an idea of what you'll be working with. I think if I were you I'd probably just have results displayed in a new window, if that works, and save hours and hours of my time. --Jeff ________________________________________ From: Code for Libraries [[email protected]] on behalf of Kyle Breneman [[email protected]] Sent: Thursday, May 18, 2017 6:00 AM To: [email protected] Subject: Re: [CODE4LIB] EBSCO Discovery Service, HTTPS, and mixed content Jeff, thanks for your response. How do you get to "developer tools"? Also, how can I learn more about working with the API? I'd like to pursue the last solution that you suggested, but I've never worked with API calls before. Kyle On Wed, May 17, 2017 at 4:40 PM, Karlsen, Jeffrey <[email protected]> wrote: > There's an EBSCO service issue about this, SI 154875, that you can ask to > be added to. I actually checked up on this the other day but there was no > update. Ridiculous, right? If you look in developer tools, you see that the > jackets come in with http:// explicitly declared. > > Will Sakai allow the search box to open results in a new window? Otherwise > I don't see any solutions unless you were to use the API instead of > EBSCOhost - if you did that you could change the protocol in the image url > before it loaded. > > -- > Jeff Karlsen > Librarian & Library Dept Chair > Sacramento City College > (916) 558-2583 > www.scc.losrios.edu/library > > > > -----Original Message----- > From: Code for Libraries [mailto:[email protected]] On Behalf Of > Kyle Breneman > Sent: Wednesday, May 17, 2017 1:18 PM > To: [email protected] > Subject: [CODE4LIB] EBSCO Discovery Service, HTTPS, and mixed content > > My library uses EDS and we've enabled HTTPS for our main EDS profile. > Apparently EBSCO is using unsecured content to provide book cover images > within EDS. This is a problem for us because we have a customized EDS > search box within our LMS, but Sakai, which prefers secure content, will > not load search results from EDS. Sakai says that there is mixed content. > > Has anyone else encountered this mixed content in EDS and been frustrated > by it? Elegant solutions? > > Regards, > Kyle > > P.S. I'm aware that some browsers still allow you to disable protections > and view unsecured content, but that process is far from intuitive for most > of our users. >
