Fees/Fines
(UXPROD-792)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | Fees/Fines |
| Affects versions: | None |
| Fix versions: | None | Parent: | Fees/Fines |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Holly Mistlebauer | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Unassigned-from-Holly, feesfines, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Epic Link: | Fees/Fines | ||||||||
| Development Team: | Vega | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R5 | ||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||
| Rank: Duke (Full Sum 2021): | R5 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||
| Description |
|
On February 13, 2020 Bjorn did a presentation to the Resource Access SIG (https://docs.google.com/presentation/d/1UVV74B6DUnlPnIlqHnQLcMy_KbtrJ1g9FhS2heOpwu4/edit?usp=sharing) asking for additional actions to be blocked. Specifically, what they are calling "Self Management", which is the updating of personal data such as contact information. We wouldn't want the patron to change their address and phone number, leaving us with no way to reach them. Note: These additional blocked actions would need to be added for both Manual and Automated Patron Blocks. |
| Comments |
| Comment by Björn Muschall [ 24/Feb/20 ] |
|
Even if I personally would like to see this function, the following question arises: This block action "Member Self Management" must either be analyzed and applied by the external Discovery System layer, which is what our library would do - or regulated by permissions etc. I have not yet deeply thought about the connection between the catalog user account and Folio. But in any event, in libraries which do not want to implement this block action in the Discovery System the presence of this functionality in Folio would only lead to confusion among staff. In the interest of the community, this block action should therefore only be developed as optional (Settings: use yes/no). As an alternative, I have explained in the SIG Meeting, that our library could also use an explicit patron block for this, which would be analyzed in the discovery system. This could be a workaround for us. We should look at the cost-benefit ratio and see how many libraries need this. |