Requesting (Retrieval) a Remote Storage Item

Purpose/Overview:

Requirements/Scope:

1. When a page request is created in circulation if the item’s effective location is remote - circulation request is saved in the "retrieval requests queue"

Approach:
Checking, that the item location is remote should be done based on cache implemeted in MODRS-2
Existing circulation events, which are implemented using PubSub should be used.

1. In order to provide additional information for Dematic the following fields should be saved in the field:
   1. holdId - (should be populated from "requestId") - the name is holdId, as it has this name in the XML response of Dematic
   2. patronBarcode
   3. callNumber - item callNumber
   4. itemBarCode
   5. patronName
   6. requestDate
   7. pickupLocation
   8. requestStatus
   9. requestNote
   10. instanceTitle
   11. instanceAuthor
   12. remoteStorageId