eastasian$ql Holding Location should allow request to either the Firestone or East Asian Library Delivery Locations

[kevinreiss]

Expected behavior

All active public delivery locations for a holding location should display on the request form. The pickup locations are configured in bibdata. Eastasian$ql current has two public pickup locations configured that fit this description.

Actual behavior

See this example record from the location.

Steps to replicate

1. Pull up any eastasian$ql item available for loan.
2. Open the request form. Only East Asian Library is available as a choice.

Impact of this bug

Users cannot send items in this location to the Firsetone Library when they want to.

Acceptance Criteria

• Items in eastasian$ql have both Firestone Library and East Asian Library as pick-up choices.

Notes

See: _requestable_delivery_option_in_library_use.html.erb
requestable_decorator.rb.

[christinach]

@kevinreiss Eastasian$ql has pickup locations: true the following:
Technical Services 693
East Asian Library GFA Pickup: PL
Firestone Library GFA Pickup PF
Firestone Library, Resource Sharing
Technical Services HMT

which attribute defines that it's a public pickup location?Is it GFA Pickup PL and PF or is it the staff_only that we are looking to say that a location is a public pickup?

[kevinreiss]

staff_only indicates a non-public pick-up location

[kevinreiss]

If that isn't set it is for the public

[christinach]

Ok I found another reference. I should be looking staff_only false

[kevinreiss]

This issue needs further review with the circulation/holdings managers. This location presents a number of edge cases. Will put it on the agenda for the next upcoming meeting for review.

1. It's a remote location part of a specific library.
2. It's comprised on items marked noCirc
3. It's wants non-circ items to be delivered to multiple campus libraries.

[mzelesky]

Blocked by https://github.com/PrincetonUniversityLibrary/alma-config/issues/1385

[maxkadel]

@kevinreiss will rewrite this ticket and put back in backlog

[kevinreiss]

We can move forward with this now.