There's two scenarios for Brock's library staff who do not have/ use/ need the Ares Client -- they both just want view-only access for all live courses in Ares on the user side.

Front-line staff at the desk: when users come to the desk and want to borrow a book for their course (say EDUC 3P90), staff used to be able to look up by course and view the list of items in order to retrieve what they need. With Ares, the student has to log in, which is clunky and not a good service model.

Liaison librarians who interact with instructors and support them: They are frustrated that they cannot help instructors and peek in when they are asked about things that may or may not be showing in Ares.

Edited for posting by Kerry - ZD #18326

What we’d like to see are more granular staff permissions, that allow us to do the following:
• Provide view-only access to the client for a staff member
• Restrict the parts of the client that can be viewed by individual staff users (e.g. items and courses are viewable, but not enrolled users, or copyright permission processing, or user information). Ideally it should be as granular as possible, so that the ‘view’ permissions can be customized for individual users based on their need/role.
• Restrict the type of data that can be modified by individual staff users; again, a toggle off/on for the ability to update certain item fields but not others would be ideal – same thing for user records, course records, web alerts, etc.

Circulation staff need to be able to search by instructor's name and course name, besides just item information.