FAQs: Working with Request Formats

Creating a New Request Format

The following are necessary for creating a new request format.

Simple Entry IDs to include within the new request format
Synonym lists of the new Entry IDs for the Full, Brief, and Template appear
A new request format that includes the use of these synonym lists
A new format that includes Entries using the simple Entry IDs mentioned in the first bullet
A Request Type policy that uses the new format
A Request Status policy that may be necessary to indicate a proper response
Request List policies that include the new Request Type policy

To create a new request format

Note: For this example, you will create a Summer Volunteer Sign Up Request.

Name

SUMMER_VOL

Description

Summer Volunteer Sign Up

Record Type

OTHER

Purpose

REQUEST (This is automatically filled in by SirsiDynix Symphony and cannot be changed)

You are now ready to modify the policy you just created. To do this, you will need to create Entry IDs and add them to their corresponding entries, which will be added to the format.

To create entry IDs

Note: To add more entries to this format, repeat the steps you just performed for each entry. For this example, you will add PHONE, STREET, CITY/STATE, REQ_DATE, and COMMENT.

You will now need to create an entry for the dates the volunteer is available.

To create an entry

You will now need to create Full Entries, Brief Entries, and Template Entries Synonym Lists that use these new Entry IDs.

Name

SUMMERFULL

Type

Synonym List

Mode

Include Specified Entries in List

Entries

USER_NAME, PHONE, STREET, CITY/STATE, DATE_AVAIL, COMMENT, REQ_DATE

You must now create a new Request Type policy that uses the new request format. Fill in the attributes using the following information:

Name

SUMMER_VOL

Description

Summer Volunteers Sign Up

Special Use

None

Request Format

SUMMER_VOL

Response Format

REPLY (Using an existing Format policy)

User Key Required

Optional

Catalog Key Required

None

Request Text Required

Optional

Status

NEW

In this example, you can modify the appropriate Request List policies to include the new Request Type, SUMMER_VOL.

Note: The request lists are used by User Access policies that are linked to user logins.

Displaying a New Request Format in the e-Library

Now that the new request format is created, complete the following steps to make this format appear in the e-Library.

To make this format appear in the e-Library

The Library needs teen volunteers for the Summer 2001 Reading Program. If you are interested in volunteering, please fill in the following form. The Children’s Librarian will be contacting you about your volunteer schedule.

How do I restrict user access to certain types of requests?

The e-Library is delivered with I Need Material and My Account enhanced request features. It is recommended that these features be available to all user types for maximum benefit of e-Library’s personalized services.

The following are necessary to restrict user access to particular request types.

A Request List policy that includes accepted request types for the user
A User Access policy that includes this Request List policy
An Environment policy that references this User Access policy
A Gateway policy referenced by this Environment policy
A User Profile policy that references this Environment policy

To restrict user access to specific request types, perform the following steps.

Note: For this example, JUVENILE users will be limited to the HOLD, SRCHSVC, and QUESTION request types.

Note: This gateway has been previously modified to include a Request gateway element that displays only the HOLD, SRCHSVC, and QUESTION request types.

Which request format entry lists appear when performing different tasks in SirsiDynix Symphony?

The following describes which request format entry lists appear when performing different tasks in SirsiDynix Symphony:

Template entries for request formats appear when a request record is created or modified.
Full entries for request formats appear in the single record view at the workstation or printed in report lists.
Brief entries for request formats appear in lists of requests.

You should not have any entries in the BRIEF or FULL formats that are not also in the TEMPLATE format, or you will not be able to create requests which contain the entry missing from the TEMPLATE.

Also, if you do not have all of the TEMPLATE entries in the FULL and BRIEF formats, they will not appear or print in reports