Currently there is no way to directly contact the original person reporting the broken link (student/lecturer) to let them know the link has been fixed and is available. We would expect the reporter to be notified when a fix has happened, without a notification they will have no idea when a broken link is accessible, or if it can’t be fixed.

At Imperial we have one Library team who checks and fixes broken links (Acquisitions) and a different team (liaison librarians) who would contact the original person reporting the broken link (student/lecturer) to let them know the link has been fixed and is available.

More details of the reporter of the broken link in Alma and Alma analytics (possibly adding the Contact Information Pop up to the reporter in the Alma citation alert section)

1. Only the reporter’s “Primary identifier” currently displays in the Leganto Broken Links Report. This does not provide enough information to contact the reporter and triage to the relevant librarian (many different librarians cover different departments) once the link has been fixed. Could the reporter’s email address and department be displayed so contact details can be harvested more efficiently?

Broken links turned into a process that can be assigned to different members of staff at different points in the process (one to fix the broken link, another to contact the user).

1. As mentioned previously, Acquisitions fix the broken link, librarians notify the reporter the fix has happened. We would expect that this could be communicated within a task pool within Alma. For example – I would fix a broken link and then be able to reassign the task to the librarian and have either a fixed (configurable status) or add a note – link fixed, please notify student. In a similar way to invoice review there could be “Assigned to me”, “Unassigned”, “assigned to others” task lists with the ability to “Assign to” colleagues, to include notifications of different stages as to where the task is.

An automatic templated email to be sent to users to notify them that the link is repaired or cannot be repaired.

1. Ultimately to provide greater user satisfaction and make the process more efficient it would be preferable to have the ability to send an auto-generated (and configurable) email to the reporter to notify them when the link had been fixed. This message would include citation details, a URL to access the resource and reading list details. Having the choice for each reported broken link to send an email or not would also be desirable. If a straightforward fix can be deployed the student could be contacted with the auto-generated email. In a scenario which is more complex, for example where a conversation needs to take place between the librarian and the reporter to resolve the situation a direct email from librarian to reporter could be an option.

Ability to see completed broken link alerts in Analytics.

1. We want to be able to see completed broken link alerts in Analytics. In order that we can statistical know how many links have been reported and successfully resolved or not by library staff. This will help us know how successful and useful the process is for users and library staff.