Hi everyone,
Here at the LSE we'll shortly be embarking on a project to implement devolved constraints to our Reading List tenancy as this seems to be a better option than the time consuming process of issuing list publisher editing rights to academics and admin staff individually as we do currently.
I just wondered if anybody else who has already implemented this could offer any advice? We use Shibboleth as our authentication system and Alma as our LMS.
I would be particularly interested to know how long the project took you to complete and if there were any problems which you encountered along the way. Also, did you opt for tenancy-wide constraints whereby all staff can edit any of the lists on the system or scoped devolved constraints whereby academic and admin staff are only permitted to edit the lists for the courses for which they are responsible?
We're at an early stage with this project but I'm leaning towards tenancy-wide constraints for us as I think it may be difficult to get accurate information about which staff are associated with which individual courses. I think there may be a very slight risk in adopting this approach and would be very interested to know if anyone else who has gone for tenancy-wide constraints has subsequently experienced any problems.
Many thanks and best wishes,
Simon
Simon Machell
Assistant Librarian
Teaching Support Services
LSE Library
########################################################################
To unsubscribe from the LIS-TALIS-ASPIRE list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=LIS-TALIS-ASPIRE&A=1
|