Paging (stack request) functionnalities

[zannkukai]

This commit implements tasks relative to UCL paging request in closed stack.
It allows to limit request for items belonging to specific location.
It also allows to restrict the pickup destination to some pickup locations
instead of all pickups locations of the organisation.
If an item of a "paging" location is requested, it also allows to send
a notification to notify a manager.

how to test

Nee to test with RERO-ILS-UI : rero/rero-ils-ui#171

• logged as a librarian, create a new location into your library. First step is to set the flag "allow_request" to false.
• create a new item an link it to this new location
• On an other browser, logged as a patron and try to request this item. The "request" button shouldn't be displayed

---

• on your first browser (logged as librarian) edit the new location : set "allow request" to true, and restrict pickup location to one or more (not all) possible pickups locations.
• on the second browser (logged as patron) refresh your page and try to request the item. The request select bow should only contains pickups locations that you select as possible pickups locations.

---

• on librarian browser : edit the location and set "send_notification" to true and set an email address into the "contact_email" field.
• on the patron browser : place a request on the newly created item. In your RERO-ILS console your should see than an email is send to location email address.

---

• Into the professional interface, all "request" button/select should follow the same behavior.

Code review check list

• Commit message template compliance.
• Commit message without typos.
• File names.
• Functions names.
• Functions docstrings.
• Unnecessary commited files?

[AoNoOokami]

Commit message:

• Updates schema location for UCL paging feature.
• Adapts existing features with new locations attributes.
• Updates fixture tests.
  ?

[pronguen]

• Notification should be sent only if the item is on shelf without previous pending loan. Now, a notification is sent to the location even if the item is already in circulation.
• Bug in the following case
  1. I have a location with pick up restriction (more than 1 pickup locations allowed)
  2. I edit this location
  3. I disable the button "Restrict pickup to"
  4. I cannot save
• In the notification e-mail, the Date placed displays the GMT time, we want the local time
  • Detail: Is Date placed correct? I would write Request date instead.
• Detail: in the notification e-mail, only the 1st statement of responsibility appears under Document title
• Detail: the use of icon "truck" for a pickup location in library detailed view could be confusing since this icon is already used for requests in the main menu. The best would be to change the main menu icon, for example with the shopping-basket already in use.

[zannkukai]

• Notification should be sent only if the item is on shelf without previous pending loan. Now, a notification is sent to the location even if the item is already in circulation.

Done

• Bug in the following case

  1. I have a location with pick up restriction (more than 1 pickup locations allowed)
  2. I edit this location
  3. I disable the button "Restrict pickup to"
  4. I cannot save

Introduced as an issue : #988

• In the notification e-mail, the Date placed displays the GMT time, we want the local time

Done : Should be test on ilsdev

• Detail: Is Date placed correct? I would write Request date instead.

Done

• Detail: in the notification e-mail, only the 1st statement of responsibility appears under Document title

I used the same method than all other emails (recall, due_soon, ...) send to user.

• Detail: the use of icon "truck" for a pickup location in library detailed view could be confusing since this icon is already used for requests in the main menu. The best would be to change the main menu icon, for example with the shopping-basket already in use.

Done