> 
>
> 
> 
The Request Type document defines the type of request available on the Request e-document and allows the system to apply logic unique to each type. For example, a request, which could include recalls, holds or pages, could be hold or delivery. Hold means that the patron will come to a pick-up location to retrieve the item when it becomes available. Deliver means that the item will be delivered to the patron when it becomes available. Request types could also include Copy or In Transit Requests.
Requests are managed via check-in or check-out transactions and those operations have business logic to follow when an item has a pending request(s) of any kind. Because of that, creating a new request type without adding business logic to the code will be pointless. The Request Type is used by an operator when creating a request for a patron. The Request Type determines the business logic to be followed.
 |
The Request Type document includes the Add/Edit Request Type tab. The system automatically enters data into both the Old and New sections in this tab. Selected data fields are available for editing.
Add/Edit Request Type Tab Definitions
|
Title |
Description |
|
Request Type Code |
Required. The request type code associated with this request type |
|
Request Type Name |
Required. The familiar title of the request type. |
|
Request Type Description |
The familiar description of the request type. |
|
Active Indicator |
Indicates whether this Request Type is active or inactive. Remove the check mark to deactivate |
