Broken link/problem files resolution inside NUI
I see there is consultation arising from NERS results about the broken link report emails (to library, an alert that a report has been made and to users, a resolution notice).
It made me think there is an opportunity in the new UI to streamline the link/file fixing process.
- When a library team member is signed in to Leganto could broken links/problem file reports be indicated in the notifications area to identify affected lists - not just the assigned librarian, but any library team member with course reserves roles?
- Could an affected citation have a indicator appear to identify which citation and which link/file is the culprit - in the list view, and in the Links/Availability tab?
- Could we fix it from within Leganto (edit the metadata or upload a new file) without forcing us to hunt around in Alma for it too. We almost inevitably will check it in Leganto anyway and not just rely on how it looks on the Alma side. Afterall, the broken link report was made from in Leganto and maybe there is additional context for why the user reported it as broken, that is not obvious in Alma. We should be able to dismiss the alert from within Leganto thereby triggering the proposed email to the user who reported the problem.
It would cut down the jumping between interfaces and minimise the risk of neglecting to remove the alert which can only be done on the Alma side.
Our faculty librarians fix links in Leganto, but they only work on course reserves in Alma sporadically - like after rollovers.
They like being able to "Set Complete" in Leganto - I think they would also like "Remove problem file/link alert" to be there.
Screenshot attached of how it might look in the new UI.
Peta Hopkins
shared this idea
-
@Ronnie - I hear what you say about not seeing an alert in Leganto until you were already there. This idea is following on from the NERS proposal where an alert email is sent.
I imagine that having received such an alert I could go to Leganto and then deal with any number of broken link/problem files by using the notifications area. And of course also deal with any that are there if I arrive for some other reason.Or starting in Alma with a citation alert on the task list, I then deal with that one, plus any others from within leganto and not need to go back to Alma for each one.
``````
We currently use LibAnswers for reporting back - we have to manually create the ticket, and use macros in the responses for the usual scenarios.
1. we have fixed it, let us know if you still have problems
2. can you provide some more information to help us diagnose
3. it's a Proquest ebook you just need to refresh the page (I think the most common broken link report we get - it would be nice if this UX could be handled on the proquest side. Our users just don't see the tiny message about refreshing) -
Ronnie Broadfoot
commented
I agree that having both the alerts in Broken Link Reports and the ability to remove them in Leganto as well as in Alma would be helpful, even though I only log in to Leganto through Alma or through our LTI (Canvas) and would not see an alert in Leganto unless I'm already there working on reserves.
Regarding the removal of a Broken Link Report in Alma triggering a message to the patron who reported the problem, I would prefer that we be able to contact that patron from the Broken Link Report itself, possibly as an option when we click on their ID number, so that in cases where we have not been able to fix it right away, we may still contact them more easily to let them know we are on the case. Also, we need to be able to attach files/screenshots in these messages. It saves the patron time if we have tested a link all the way through downloading material if we can attach that downloaded material. Seeing how much time they've lost waiting to do their homework, we should be able to share the think they were trying to read. I do that in my emails to them already.
I also think it would be good if a link that has already been reported as broken would have some sort of alert letting students and staff know in Leganto that a problem has already been reported. They might still want to add their own report if there is reason to expect they will be contacted if and when it is fixed, but I am sure students would like to know if they are not the only ones having problems and instructors really need to know, too.
Ronnie Broadfoot
Access Services, Harvard Library
Harvard Univeristy