Expire Holds Report
| • | Pipe-delimited Output |
The Expire Holds (Expireholds) report helps staff to manage expired holds. The report selects ACTIVE holds for which the date the hold expires has passed, and sets the hold status to INACTIVE with a hold inactive reason of EXPIRED. The report also generates notices to be sent to users for expired, cancelled holds.
The SirsiDynix Symphony Workstation server needs to be running to schedule and run this report, or the report will fail. Do not halt the SirsiDynix Symphony Workstation server until the report displays on the finished list.
If you use the Purge Inactive Holds report, keep in mind that selected holds are deleted completely from the database, and can only be restored from a current backup. Once the selected holds are removed permanently from the database, statistics reports cannot select and include these holds in the statistics report output. SirsiDynix strongly recommends that you run your statistics reports first. After you have finished compiling all of the statistics you want, run the Purge Inactive Holds report.
This report contains the following tabs.
| • | Basic Tab: Reports |
| • | General Notice Tab |
| • | Hold Selection Tab |
| • | Sorting Tab |
| • | Print Separate Reports for Each Library Tab |
A hold expiration date can be set when a hold is created, or set by default using the Days for Holds to Expire attribute in the Library policy. When the Expire Holds report runs, holds are selected that have expired any day before the report run date as long as the user has never been notified previously of a hold cancellation for that material. Selected holds are set to INACTIVE with a hold inactive reason of EXPIRED. You must run the Clean Holds Shelf (Cleanholdshelf) report to make the next holds on items available, to put the items in transit back to the owning library, or to direct the items to be reshelved.
When the Expire Holds report is run with the Count as a Notice Sent check box selected on the General Notice tab, the Date Cancellation Notified field is updated to the date and time the report runs. This field does not display at the workstation; it is managed solely through reports. By using this feature, a user will receive a single cancellation notice for each expired hold.
If you run the Expire Holds report with the Count as a Notice Sent check box cleared on the General Notice tab, you may later run the Notice for Cancelled Holds (Holdcancelntc) report to produce notices for expired holds. Then you must run the Clean Holds Shelf report to select the holds made INACTIVE by the Expire Holds report, make the next hold available, out the item in transit, or to direct the item to be reshelved.
To remove the inactive, expired holds completely from the system, run the Purge Inactive Holds Report.
If Generate Pipe Delimited Output is selected on the Charge Notice tab, the report creates a pipe-delimited file and places it in the /Rptprint directory with the naming convention of yyyymmdd_internalrptname.pipe. The report log lists the pipe-delimited report file name. This pipe-delimited file can be opened using a third-party application, such as a spreadsheet application.
Sorting selections made within the report are not applied to pipe-delimited files. For example, if you sort the report by zip code, the zip code sort is not applied to the contents of the pipe-delimited file.
The entries listed in the Brief Entries attribute of the User Address Format wizards are used to supply information for the address fields in the pipe-delimited file. The City/State field (if it is used) is evaluated as one field, not as two separate fields for the city and the state. The report will check user records for the fields listed in the Brief Entries attribute and print only the populated fields in the pipe-delimited output.
Pipe-delimited Key File
The pipe-delimited key file defines each field of the pipe-delimited file for a particular notice.
The following pipe-delimited key file defines the fields for an expired hold notice.
|date|Library name|street|line|city, state|zip|user name|street|line|city, state|zip|salutation|notice text|title|author|call number|hold reason|
The following example shows a pipe-delimited key file for an expired hold notice, and the notice output that is produced from the file.
|Friday, May 12, 2006|Rockerfeller Public Library|123 Main St.||
St. Louis, MO|35801|Mary Patron|1234 Fair Oaks Lane||
St Louis, MO|55555|Dear Mary Patron,|
This is to inform you that hold(s) you placed have been removed.
See the details below for an explanation. |A pictorial history of music
[by] Paul Henry Lang and Otto Bettmann.|Lang, Paul Henry, 1901-|ML89 .L15|
Hold has expired|
Friday, May 12, 2006
Rockerfeller Public Library
123 Main St.
St. Louis, MO
55555
Mary Patron
1225 Fair Oaks Lane
St Louis, MO
55555
Dear Mary Patron,
This is to inform you that hold(s) you placed have been removed.
See the details below for an explanation.
1 A pictorial history of music [by] Paul Henry Lang and Otto Bettmann.
Lang, Paul Henry, 1901-
call number:ML89 .L15
Hold Reason:Hold has expired
Related topics
My Circulation Group Reports (in SirsiDynix Symphony K12)
FAQs: Managing the Holds Shelf