In order to support customising hold shelf request expiry by service point, we need to be able to store a hold shelf expiry period
property ((e.g. holdShelfExpiryPeriod)) for a service point.
- Includes conditional validation for when hold shelf expiry should be present
- There is a period schema already defined in circulation, this should use a similar structure
Should the conditional validation, that this property should only be allowed when a service point is used for pickup, be implemented in the storage API? Should the period schema used in mod-circulation-storage be extracted to shared RAML for reuse? (with a stricter definition, which Vega team have discussed)?