Only update rpd
value if patron requested access via Open Library
#11289
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follows #10899
Background Information
Our
/admin/pd
stats tell us that ~10 patrons have had their special access requests fulfilled (meaning theirrpd
preference has a value of2
). However, there are over 1,000 patrons who have anrpd: 2
, but nopda
authority in the store.Why is this happening?
Whenever any patron logs in, we check the
xauthn
response to see if they have special access. If they do, we update theirrpd
status to fulfilled. This is done even if the patron did not request special access via Open Library. Such patrons can be identified by having a fulfilledrpd
value, but nopda
value in their preferences (this stores the patron's chosen print disability qualifying authority).How does this branch help?
This branch will prevent an
rpd
value from being saved to a patron's preference object if they do not already have apda
value.Technical
Testing
Screenshot
Stakeholders