add pickupServicePointId to the the request object
Description
Environment
Potential Workaround
blocks
is blocked by
Checklist
hideTestRail: Results
Activity
Cate Boerema October 23, 2018 at 9:42 AM
Just so that I fully understand, this is something we need to extend the storage model to track, right?
I assume so. We need to do whatever is needed to support the requirements in https://folio-org.atlassian.net/browse/UIREQ-131#icft=UIREQ-131 which, in turn, will enable a bunch of other functionality such as that specified in https://folio-org.atlassian.net/browse/UIREQ-114#icft=UIREQ-114 and https://folio-org.atlassian.net/browse/UIREQ-140#icft=UIREQ-140,
Do we need to create an issue in mod-circulation-storage, or should we just move this one?
No idea.
Kurt Nordstrom October 22, 2018 at 7:15 PM
@Jakub Skoczen @Cate Boerema Just so that I fully understand, this is something we need to extend the storage model to track, right? Do we need to create an issue in mod-circulation-storage, or should we just move this one?
Jakub Skoczen October 18, 2018 at 11:51 AM
@William Welling @Jeremy Huff @Kurt Nordstrom can one of you guys take care of this item?
Based on the work in https://folio-org.atlassian.net/browse/UIREQ-131#icft=UIREQ-131 we need to be able to store the pickupServicePointId for a given request. It looks like this is currently missing:
https://s3.amazonaws.com/foliodocs/api/mod-circulation/2/circulation.html#POST/circulation/requests
and the schema needs to be extended.