Restrict patron opt-in ... setting should be more restrictive
Bug #1757507 reported by
Jason Boyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
The OUS org.restrict_
description: | updated |
description: | updated |
tags: | added: orgunitsettings patron |
Changed in evergreen: | |
milestone: | 3.next → none |
To post a comment you must log in.
Here it is: git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jboyer/ lp1757507- restrict- opt-in- for-real
http://
It's simply a reordering of the existing tests but here's a simple way to test.
pre-patch opt_to_ depth to any level you like at a specific system level (or below) OU other than the one your workstation is in.
Set org.patron_boundary to 0 at the top of your consortium.
Set org.restrict_
Search for a patron that should be at a restricted location.
Open user account and receive no notice of opt-in restriction.
post-patch:
Same as above but at final step you will be denied access to the patron's information because they can't be opted-in at your location.
Search for any user outside of the restricted area of the aou tree.
Open user account and receive no mention of opt-in.