bad link reporter
Bad Link Reporter
This tool would work while librarians are searching Primo. An addon tool for Primo that looks at results when the following condition exists: a link is clicked and user gets an error, (no full text available or other Primo error messages) there would be a popup or message asking “report this bad link?”. You click on the button, it goes away allowing librarian to continue their work but clicking the button reports the permalink, search details and bad link error message including eresource used. This option only occurs for library staff. Ordinary users would not see it.
The popup button reports these results to the local library IT Primo support for further investigation and correction. Librarian user type would have to be logged in and have a “reporter” check box in their profile that lets them see a pop up any time one of these conditions exist. This could be set by default for various levels of errors for all library staff or have an opt in or out choice. If librarian clicks Yes, report goes to local IT support. If librarian clicks No, a simple log is recorded when using eResource that was clicked on.
1. Instead of a popup, error is reported automatically behind the scenes. Local IT can turn feature off if they are overwhelmed and turn back on later as needed.
Librarian could request a “screen capture” that would document error after clicking on link. Then screen capture is automatically linked to the logged error.
Tool keeps track of eResource titles reported and if librarian has already reported this specific title, would tell them, you have already reported this error for this title.
Give troubleshooter a "quick link" to the problem portfolio in Alma to suppress a portfolio if you have a meta data mismatch or cataloging problem that resulted in bad link or bad result. This would give local library some control over these types of problems.
Helps librarians report bad link results
Informs local troubleshooter of the problem with accurate details.
Improves Primo search experience.
May result in fewer cases submitted to ExLibris or at least better documentation.
Dean Lingley commented
I think this idea is related to this idea too: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/18636772-create-link-for-patron-to-report-issue-with-primo
The thought of the idea above is for Primo Central records with direct links embedded, where the local library has no control over fixing. Have those problem reports go straight from the patron to ExLibris so they can possibly have a gauge on problem importance based on number of reports per record.
Dean Lingley commented
I think this idea is also related to this idea: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/37969432-portfolio-link-checker
Let's proactively try and find dead links before the user does if possible.
I agree with the other comments about not limiting the feature to librarians - our users would love this on Primo
I think this feature should be default, but on the PUBLIC facing side of Primo so users could report problems with linking. I agree with Patt.
m schwendener commented
It says VE in the title, but according to the author (in a mailing list) it's not VE specific.
Patt Leonard commented
I would not limit this feature to librarians--it's much more likely that our users will be searching Primo and encounter the bad links. Because there is no simple or obvious reporting mechanism, they don't inform us. I would make “Report this bad link?” an option for anyone who is browsing the catalog.