The information that appears on the Basic Information tab for requests varies depending on the request type or the request wizard selected.
Basic Information Tab for Requests
Any of the following fields can display in the Basic Information tab for Requests. The fields will vary depending on the Request Type.
| • | User Name |
| • | Profile Name |
| • | Original Request ID |
| • | User ID For Requests |
| • | Request ID |
| • | New Request ID (for duplicated requests) |
| • | Request Type |
If the request is linked to an item in the catalog, title, author, call number, and item, information will display on a button. Selecting this button will display detailed volume/copy information.
User ID and Name glossaries display additional information about the user.
Basic Info Tab for Request Wizards
The Basic Info tab for the Request wizards may contain the following information. This will vary based on the Request type that is selected on the wizard’s Properties screen.
The following fields are defined for the Basic Information tab for requests and request wizards.
| • | Alt ID |
| • | Date Modified In Requests |
| • | Date Placed In Requests |
| • | Date Replied or Reply Date |
| • | Date Viewed |
| • | New Request ID (for duplicated requests) |
| • | Origin Library |
| • | Original Request ID |
| • | Profile Name |
| • | Request ID |
| • | Request Type |
| • | Service Library |
| • | Status for Requests |
| • | User Access |
| • | User ID For Requests |
| • | User Name |
The Alt ID (alternative ID) field is an optional alphanumeric-character field that can be used for a unique number or name different from the User ID. If the library must use random barcodes as user IDs, then the alternate ID can be an individually significant number or name such as a Social Security number, student ID number, or driver’s license number. The Alt ID field is limited to a maximum of 20 alphanumeric characters.
For Requests, if the Request Type policy defines user identification as necessary to process the request, and the library has specified that a user should enter an alternative user ID, then this field displays. If it displays, it can either be an optional or required field. This field can contain up to 20 characters of the ID of the user for whom the request is being placed, or the operator’s user ID.
This field is updated when a library user or library staff member modifies the request record. It is also updated when the library sends a request reply.
This field displays the date a request was created. This field is maintained within the system and cannot be directly modified.
This is the date entered by the user who answers the request.
Note: When a request record is created or duplicated, this date is automatically set to Never. As long as the request does not yet have a reply, or the reply is not ready to be seen by the library user, this date should remain Never.
As long as the reply date is set to Never, the user cannot view the reply. Use the Calendar gadget to select either No Date or to enter a Specific date that indicates when the request has been answered.
This is the date that the library user viewed the request and reply. As long as the date viewed is Never, the user can view his or her request, but will receive the following system message in association with any reply that may be in the record.
A reply to your request has not yet been sent.
Note: It is important to set a reply date once the request has been answered so the user who submitted the request can view the reply.
New Request ID (for duplicated requests)
This field contains the unique number by which requests are identified. You may assign a new request ID when duplicating an existing request using the Duplicate Request wizard.
Note: Selecting AUTO from the drop-down list automatically generates a unique request ID patterned after an established scheme.
The system administrator may create a pattern that has a prefix, an incrementing numeral, and a suffix, such as REQ-1000-93. In a multilibrary system, each library may have a different pattern, such as REQ/MAIN-1000, REQ/WEST-1000, or REQ/MURREY-1000.
Library field values are defined in the Library policies set up by your SirsiDynix Symphony System Administrator. At the basic level, this field determines the library where an item is held and where the user is registered in a multilibrary setting.
Note: The Library field does not display in a single library system.
In the request module, the Origin Library field displays the library associated with the station where the request originated, or, if using a floating station that does not have a library defined, the library associated with this user. Origin Library is maintained by SirsiDynix Symphony and cannot be directly modified.
The Original Request ID field displays on the Duplicate Request screen when you are duplicating an existing request using the Duplicate Request wizard. The number refers to the Request number of the particular request you are duplicating. The system-generated request number displays in the following format: REQ-322
This field contains a User Profile policy name. This is a required field when creating a user. Example Profile names could be STUDENT, ADULT, Faculty, Guest or LOST CARD. The User Profile policy name determines the user’s privileges, loan period and fine rate.
This field contains the unique number, up to 20 characters, by which requests are identified.
Note: Selecting AUTO from the drop-down list automatically generates a unique request ID patterned after an established scheme.
The system administrator may create a pattern that has a prefix, an incrementing numeral, and a suffix, such as REQ-1000-93. In a multilibrary system, each library may have a different pattern, such as REQ/MAIN-1000, REQ/WEST-1000, or REQ/MURREY-1000.
The request type identifies what the request is to be used for and the format of the display. Request Type and Request Format are separate policies, but they may use the same policy name.
| • | Request Type is a policy which establishes the behavior of the request, such as whether user or item information is required. |
| • | Request Format is a policy that determines what text entry fields are available when a request or reply is displayed. |
In the request module, the Service Library displays the library whose staff should respond to a request. Service Library defaults to the same library as the originating library, but this field may be changed to any library listed in the policies. Service Library allows staff at one library to direct or redirect a request for response by another library.
You may use the Service Library alone or combine it with Status to produce a list of requests. By specifying a library only, a list of all requests created in, awaiting a response from, or answered by that library, will appear. By specifying a library and a status, a list of all requests in that library with the specified status displays.
Note: The Library field does not display in a single library system.
This field contains the status for a request record and is based on a defined policy. All request records may be displayed for a particular service library that has the same status.
Note: Each request type must have a default Status policy defined that will be assigned to a new request during the Create Request process. For example, all ILL requests would default to a status of NEWILL.
While a default status exists for each policy type, the Status drop-down list allows you to change to another Status policy for the request being created.
This field references the User Access Policy of the user performing the function.
When creating the user ID, you can either assign a user ID, or allow SirsiDynix Symphony to automatically generate one.
Typically, libraries use random numbers associated with barcodes for unique user identification. However, you may user other alphanumeric characters, such as a driver’s license number, according to the unique numbering or naming scheme established by your library. The user ID can be up to 20 characters in length.
Note: You can enter a user ID using the User Search Helper or the User Search Gadget
If the Request Type policy defines user identification as necessary to the processing of the request, and the library has specified that a user should enter his or her user ID, then this field displays when a request is placed. If it displays, it may be optional or required. This field may contain up to 20 characters of the user ID for whom the request is being placed, or the user ID of the user placing the request.
This field contains the user’s name. By default, this value is in the form last name, first name (or preferred name) and initial, such as Smith, Joe H. The label for this field may be changed by the library.
© 2006, 2014 SirsiDynix