Closed jrochkind closed 7 years ago
So when using EDS to retrieve catalog results, the API does not seem to include publisher, publication date, or publication place in the response at all.
Actual standard EDS UI includes these things, so they are available to EDS somehow -- but maybe not included in API response (I guess standard EDS may not use it's own API).
If they aren't in the API response, they can't be displayed in the 'bento' results getting data from the API response. I don't know if there's some configuration that can change this somehow, or if I'm missing something, or if we're just out of luck.
I can try asking on the code4lib list for other developers who may have used EDS API. And/or you could try asking EBSCO support. Thoughts, @tkaczorowski ?
I don’t see any way in EDSAdmin to affect these changes. I’ll contact ebsco.
Tom
From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Tuesday, December 06, 2016 11:30 AM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] Layout of individual catalog/articles items (#28)
So when using EDS to retrieve catalog results, the API does not seem to include publisher, publication date, or publication place in the response at all.
Actual standard EDS UI includes these things, so they are available to EDS somehow -- but maybe not included in API response (I guess standard EDS may not use it's own API).
If they aren't in the API response, they can't be displayed in the 'bento' results getting data from the API response. I don't know if there's some configuration that can change this somehow, or if I'm missing something, or if we're just out of luck.
I can try asking on the code4lib list for other developers who may have used EDS API. And/or you could try asking EBSCO support. Thoughts, @tkaczorowski https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tkaczorowski&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=p1OMc57anPELK83d4y1tQt1x48iYrQeJgBj60lDw8UA&s=3yqStLfhp1Og2xAcYh4U-NX40nD0FsgedIYUzRwjZd8&e= ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_28-23issuecomment-2D265197329&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=p1OMc57anPELK83d4y1tQt1x48iYrQeJgBj60lDw8UA&s=NplYu2l2WwwTpl8_BGpl2pojkOHj_R0rJ1wADpU5iNw&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2DfkwZwStE-5FGATSFfUmEEkKJYf5I2gks5rFY16gaJpZM4K4iic&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=p1OMc57anPELK83d4y1tQt1x48iYrQeJgBj60lDw8UA&s=8KnRUU8oadxuM7_Q9hhiipfhZsrEZA-Rt7GzVnku2vM&e= .[image: Image removed by sender.]
Hi Jonathan,
Can you set the bento search to use the catalog api so Ebsco techs can see the behavior?
Tom
Hi Jonathan,
I’m trying to view changes to the api settings for apicat using the ebsco admin:
I have to read the XML. I’ve tried changing the output type to “detailed” but I don’t think this has helped.
Is a “get search” what I should be using? Are you using this interface to test?
Thanks, Tom
I think something didn't come through in your email, so I'm not entirely sure what interface you are talking about -- I'd suggest using the github issues web interface to comment on these issues. https://github.com/Fordham-lawlib-bento/fordham-law-search/issues/28
But yes, I am using the 'GET search' api, and I tried 'detailed' too with the same experience.
Can you set the bento search to use the catalog api so Ebsco techs can see the behavior?
Sorry, not sure what you mean by 'catalog api'. Is there a separate 'catalog api' I don't know about?
The currently deployed app is using EDS, with the apicat
profile to display catalog results. But you can't really see what the API is returning by looking at the user-facing app, it does not seem like a useful way to debug this to me.
I see MIT has no publisher or year in their EDS-based catalog bento results either:
I'm guessing it's not avail from the API. I'll check with my MIT contact.
I suppose we could switch back to screen-scrapping Sierra Classic. The result counts will not match when following 'view more results' to EDS catalog, though.
Currently the bento search appears to be showing publisher and date published info, no? See:
[image: bento cat pub]
The api data seems to be there, though the formatting in the bento is different than in EDS:
I assume this is a function of the apicat vs edscatonly. Let's see what Ebsco says about publisher/date info via the API - still waiting. They've been very good at fixing/customizing.
When I asked about using the api it was because when I clicked 'see all' I was being taken to encore which made me think you weren't using the EDS API. I am now seeing EDS, so I assume everything is EDS (incl. api for search). Scraping classic won't work because we need the results to be in sync.
The github posting interface is crappy for inserting screenshots.
Tom
From: Jonathan Rochkind [mailto:notifications@github.com] Sent: Tuesday, December 06, 2016 12:54 PM To: Fordham-lawlib-bento/fordham-law-search < fordham-law-search@noreply.github.com> Cc: tkaczorowski tkaczorowski@law.fordham.edu; Mention < mention@noreply.github.com> Subject: Re: [Fordham-lawlib-bento/fordham-law-search] Layout of individual catalog/articles items (#28)
I see MIT has no publisher or year in their EDS-based catalog bento results either:
http://libproxy.mit.edu/login?url=https://search.ebscohost.com/login.aspx?direct=true&AuthType=cookie,sso,ip,uid&type=0&group=edstest&profile=edsbarton&bquery=law https://urldefense.proofpoint.com/v2/url?u=http-3A__libproxy.mit.edu_login-3Furl-3Dhttps-3A__search.ebscohost.com_login.aspx-3Fdirect-3Dtrue-26AuthType-3Dcookie-2Csso-2Cip-2Cuid-26type-3D0-26group-3Dedstest-26profile-3Dedsbarton-26bquery-3Dlaw&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=6qCclWxtwth6GTxPWv77SXXgwyCJOlxuSGcGQtZBF2M&s=xVm6obj4BDoU-ZA-EQc7E0BWmi44KYRqP-9XKBNl8d4&e=
I'm guessing it's not avail from the API. I'll check with my MIT contact.
I suppose we could switch back to screen-scrapping Sierra Classic. The result counts will not match when following 'view more results' to EDS catalog, though.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Fordham-2Dlawlib-2Dbento_fordham-2Dlaw-2Dsearch_issues_28-23issuecomment-2D265221509&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=6qCclWxtwth6GTxPWv77SXXgwyCJOlxuSGcGQtZBF2M&s=TngitgUMiynLM5tGexQOSMkfpxkml6JszYNtBmkxXRA&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AOW-2DfqVTZr2ieX2-5FQDlqnGKQ8BVU1jC0ks5rFaE3gaJpZM4K4iic&d=DgMFaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=ufwSdmS5IZPSMZUMObqD9D-VUZ9gAg0GtO2ab7PNYjU&m=6qCclWxtwth6GTxPWv77SXXgwyCJOlxuSGcGQtZBF2M&s=AHJEJU5FngsAA_eldcsiNVGp0gQU-DRtzz-FceutyMw&e= .[image: Image removed by sender.]
This is a Github issue, when you reply with email it gets automatically added to the github issue, but your attached images don't seem to make it through, so I could not see your screenshot.
You can just drag an image into the Github Images post box to attach a screenshot.
I am not seeing any publisher names in the currently deployed app on heroku. You're right, dates do seem to be there, great (although they're all displaying as Jan 1st, I can fix that).
Substantially polished off to be 'correct'.
Not really designed yet, still kind of a jumble of text.
pre-requisite: