You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SearchWorks feedback from Amy Hodge reveals confusion when a user places a mediated request, and fills in the "I plan to visit on" field in the REQ app. Then checks MyAccount in the brief period of time after the request is approved by staff (and the hold is created in Symphony, but not yet available) but before it arrives on campus (and the SYM hold is made available.)
During that brief period, we are not displaying the "I plan to visit on" date from the REQ app (we ran out of time in the initial sprint to incorporate data from REQ.) Instead we display the "fill by date". I think we input a default value in the hold record when the hold is created in SYM.
(I'll drop a screenshot here when I can get one...)
As soon as the hold becomes available, we show other values about the hold - including a pickup by date. (Currently problematic because the staff don't modify this date based on conversations that they have with users. Though they could...)
Here's a snapshot of the problem when the hold is available.
The text was updated successfully, but these errors were encountered:
saseestone
changed the title
Users confused by "I plan to visit on" in Request app vs. "Not needed after" label showing in Requests tab in MyAccount
Users confused by "I plan to visit on" label and date in REQ app vs. "Not needed after" label showing in Requests tab in MyAccount
Sep 16, 2019
SearchWorks feedback from Amy Hodge reveals confusion when a user places a mediated request, and fills in the "I plan to visit on" field in the REQ app. Then checks MyAccount in the brief period of time after the request is approved by staff (and the hold is created in Symphony, but not yet available) but before it arrives on campus (and the SYM hold is made available.)
During that brief period, we are not displaying the "I plan to visit on" date from the REQ app (we ran out of time in the initial sprint to incorporate data from REQ.) Instead we display the "fill by date". I think we input a default value in the hold record when the hold is created in SYM.
(I'll drop a screenshot here when I can get one...)
As soon as the hold becomes available, we show other values about the hold - including a pickup by date. (Currently problematic because the staff don't modify this date based on conversations that they have with users. Though they could...)
Here's a snapshot of the problem when the hold is available.
The text was updated successfully, but these errors were encountered: