The goal of the spike is to define the necessary steps to introduce Request Preferences per User in mod-circulation.

Spike results:

1. Storing request preferences in mod-circulation-storage:

We will add table user_request_preferences to mod-circulation-storage. user_request_preferences will store user preference fields in json format. 

...

3. Attributes of user request preference:

id

...

-

...

Unique

...

request

...

preference

...

ID
userId

...

-

...

UUID

...

of

...

user

...

associated

...

with

...

this

...

request

...

preference
holdShelf

...

-

...

Whether

...

'Hold

...

shelf'

...

option

...

is

...

available

...

to

...

the

...

user.
delivery

...

-

...

Whether

...

'Delivery'

...

option

...

is

...

available

...

to

...

the

...

user.
defaultServicePointId

...

-

...

UUID

...

of

...

default

...

service

...

point

...

for

...

'Hold

...

shelf'

...

option
defaultDeliveryAddressTypeId

...

-

...

UUID

...

of

...

user's

...

address type
fulfillment - Preferred fulfillment type. Possible values are 'Delivery', 'Hold shelf'

Example of request preference:

...