Improve handling of expired user accounts for course owners during rollovers
For rollovers we copy the collaborators from the original list and usually this is OK, however we then start getting bounce back emails for Leganto notifications being sent to email addresses that are no longer active.
A couple of options that would be helpful...
1. Provide option in the integration parameters to prevent an expired collaborator being copied on rollover
2. Job report to provide a warning that a course owner/collaborator has an expired user account
Peta Hopkins
shared this idea
-
And if you don't use rollovers, but still need to deal with expired users in courses then there is this new idea -- https://ideas.exlibrisgroup.com/forums/395697-leganto/suggestions/48457352-bulk-job-options-to-remove-expired-alma-user-accou
-
Patricia Farnan
commented
This is a great idea. Ideally #1 would be possible as it's less manual work to remove expired accounts then.
-
Deborah Fitchett
commented
This (especially #1) would be really useful for us too, since if a course changes hands frequently (some courses are particular hot potatoes) the list of course owners just keeps building up year on year. Lots of our courses have long lists of owners, many of whom have left the university.
When we purge user data, eventually they're only represented in the list by their old staff ID number so at least they no longer get emailed - but then we've got no way to remove all their courses in bulk (since they no longer have a user record), and instead have to go individually into each course.