Problem Report Links when 360 API Non-Responsive

[varnum]

Should report a "report a problem" link appear in the interface when the API times out and there are no full-text or other links to report a problem with? Seems like a tweak to the rules is in order next week.

Email chain (from Pam MacKintosh to Karen R-S) is below.

Ken
---------- Forwarded message ---------
From: Karen Reiman-Sendi karsendi@umich.edu
Date: Fri, Dec 16, 2016 at 5:15 PM
Subject: Issues with M Get It linking?
To: Ken Varnum varnum@umich.edu
Cc: Harold Tuckett htuckett@umich.edu

Hi there Ken (and Harold)! I'm forwarding along an issue we seem to be seeing in the Ask a Librarian email service, related to ArticlePlus linking issues. I'm wondering if there is anything that can be tweaked on the backend to eliminate the need for a user to report a bad link where there is none. Thanks for thinking about this! Karen

Hi, Karen,

I mentioned this morning about the ArticlesPlus error: "MGet It is temporarily unavailable. Please try back later". Below is a message from Kenyon in EAU explaining this. He says:

"The patron mentioned they got a message indicating "MGet It is temporarily unavailable. Please try back later" That sometimes happens with the new MGet It where the MGet It menu has that message and no full text links are showing. According to Design & Discover this happens because the 360 Link API used to generate the information for the menu times out. Usually waiting a few seconds then running the Permalink in another tab or window will result in a MGet It menu with the full text links."

I have seen several ArticlesPlus problem reports with this message lately.

Pam

[bertrama]

It's not clear to me what's being requested.

Are we being asked to automatically report these links to Ask a Librarian when they occur?

Or are we being asked to remove the links so patrons can't report them?

[varnum]

Sorry for not being clearer: When the API times out and there are no full text links to display, don't show the "Report a Problem" link.

[bertrama]

It's that word need that threw me off:

I'm wondering if there is anything that can be tweaked on the backend to eliminate the need for a user to report a bad link where there is none.

So we are in fact removing the ability to report problems.

[varnum]

Yes, when the reason for no results is the API having timed out.

…

-- Ken Varnum Senior Program Manager for Discovery, Delivery, and Library Analytics Library Information Technology | University of Michigan Library varnum@umich.edu | @varnum | 734-615-3287 http://www.lib.umich.edu/users/varnum

On Mon, Dec 19, 2016 at 1:59 PM, Albert Bertram ***@***.***> wrote: It's that word *need* that threw me off: I'm wondering if there is anything that can be tweaked on the backend to eliminate the need for a user to report a bad link where there is none. So we are in fact removing the ability to report problems. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#71 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ7bL0FWQZE9lKchIWgVkpUgwCmAwjWcks5rJtP8gaJpZM4LQyUZ> .

[bertrama]

Done.