| 2018-03-21 19:00:26 |
Jason Boyer |
description |
The OUS org.restrict_opt_to_depth is intended to restrict the ability for patrons to opt-in to locations outside of the specified depth at the OU where it's set. However, if org.patron_opt_default is set to a depth above those excluded OUs the restriction is ignored. This makes it extremely difficult to define the patron opt-in default to the whole consortium while also restricting opt-in from specific locations. |
The OUS org.restrict_opt_to_depth is intended to restrict the ability for patrons to opt-in to locations outside of the specified depth at the OU where it's set. However, if org.patron_opt_boundry is set to a depth above those excluded OUs the restriction is ignored. This makes it extremely difficult to define the patron opt-in boundry at the consortium level while also restricting opt-in from specific locations. As a more practical example, you can't restrict sibling branches from opt-in to each other but only at one system while using the system level as the boundry everywhere else. |
|
| 2018-03-21 19:03:55 |
Jason Boyer |
description |
The OUS org.restrict_opt_to_depth is intended to restrict the ability for patrons to opt-in to locations outside of the specified depth at the OU where it's set. However, if org.patron_opt_boundry is set to a depth above those excluded OUs the restriction is ignored. This makes it extremely difficult to define the patron opt-in boundry at the consortium level while also restricting opt-in from specific locations. As a more practical example, you can't restrict sibling branches from opt-in to each other but only at one system while using the system level as the boundry everywhere else. |
The OUS org.restrict_opt_to_depth is intended to restrict the ability for patrons to opt-in to locations outside of the specified depth at the OU where it's set. However, if org.patron_opt_boundary is set to a depth above those excluded OUs the restriction is ignored. This makes it extremely difficult to define the patron opt-in boundary at the consortium level while also restricting opt-in from specific locations. As a more practical example, you can't restrict sibling branches from opt-in to each other but only at one system while using the system level as the boundary everywhere else. |
|
