Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't query the BorrowDirect API for patrons that aren't eligible to request material from them #326

Open
cbeer opened this issue Jul 29, 2019 · 6 comments
Labels
blocked Dev work cannot move forward

Comments

@cbeer
Copy link
Member

cbeer commented Jul 29, 2019

We're currently excluding proxy borrowers, but should we exclude e.g. fee borrowers as well?

@saseestone
Copy link

Yes, we should exclude Fee Borrowers. They are not eligible for BorrowDirect requests. (You have to have a SUNet ID and be in the stanford:stanford or stanford:acad priv group.)

@saseestone saseestone removed the question Further information is requested label Jul 30, 2019
@cbeer cbeer self-assigned this Jul 30, 2019
@cbeer
Copy link
Member Author

cbeer commented Jul 30, 2019

Can you check out a borrowdirect request on behalf of a research group? Or, more specifically, should a proxy be able to see other proxies borrow direct requests on behalf of the group (if such a thing is even possible?)

@saseestone
Copy link

saseestone commented Jul 30, 2019

Yes, you can checkout a borrowdirect item as a proxy. (You can't request it via SearchWorks because SUNet ID is required, but we do have users that request using their SUNet ID and then when they come to the library and checkout the item - the use their proxy account for the checkout)

Yes, a group should be able to see borrowdirect items checked out to related proxies.

PROXY22 currently has a borrowdirect checkout.

@cbeer
Copy link
Member Author

cbeer commented Jul 30, 2019

Ok -- but you can't request a borrowdirect item as a proxy?

@saseestone
Copy link

You have to webauth to complete the request...so no.

So the scenario is a grad student - doing work on behalf of their faculty PO on a grant. They are webauthed individually, and can create the request in SW. REQ uses the BD API and then the request is in BD land (Relais). So grad student will see the BD request on their individual "Requests" tab in MyLibrary. Item arrives at Stanford and is processed (item is created in Symphony; Hold is placed in Symphony), so item appears on their "Ready for pickup" list and they get a pickup notice generated from Symphony. Grad student shows up at the pickup library and asks the staff to charge the item to their proxy account. Circulation staff checkout the item to their proxy account (using an override to override the hold block) and the item will appear on the Proxy checkout list. (And be completely gone from the grad students individual account...)

@cbeer cbeer removed their assignment Jul 31, 2019
@cbeer cbeer changed the title Who is eligible to make BorrowDirect requests? Don't query the BorrowDirect API for patrons that aren't eligible to request material from them Jul 31, 2019
@camillevilla camillevilla added the blocked Dev work cannot move forward label Aug 27, 2019
@camillevilla
Copy link
Contributor

Blocked by #336 - sorting out our LDAP permissions.

@camillevilla camillevilla added enhancement New feature or request and removed enhancement New feature or request labels Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Dev work cannot move forward
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants