Using Notice Tables

To create your own customized notices, you must access notice information stored in your Horizon database. When you run circulation reports, Horizon stores notice data (including borrower number, item, title, and block type) in three tables. You can use your own program or a third-party report writer to extract the desired information from these three tables and place it anywhere on your notices.

Because each library can use any number of third-party report generators, this section lists only the tables and their columns from which report generators (or library-created programs) can extract notice information. You can print your customized notices and send them through your local postal service or you can send notices by email.

The notice table stores information about the borrower (such as the borrower number) and summary information from all the blocks on the notice. It also stores information about the borrower location (such as the library name and address).

Column

Contains This Information

add_corr_req

Whether the message “Address Correction Requested” is included in the notice (1=Yes).

Note: If you are in the United States, SirsiDynix can customize the text in this message depending on the contract your library has with the United States Postal Service.

balance

Balance due (if any).

balance_str

Balance due (formatted).

Use this column instead of the balance column for third-party report programs, since it is already formatted with dollar signs, decimal points, and so forth.

batch#

System-assigned number of the batch that contains the notice.

borrower#

System-assigned number of the borrower record for the borrower who receives the notice.

content#

Notice that the line represents (first, second, and so forth).

invoice#

Number of the invoice.

location

Code for the location to which the borrower belongs.

output_date

Date that the notice was created in Horizon.

total_amount

Total amount owed (if any).

total_amount_str

The total amount owed (formatted).

Use this column instead of the total_amount column for third-party report programs, since it is already formatted with dollar signs, decimal points, and so forth.

The notice_batch table contains information about each batch of notices that you create in Circulation Reports.

Column

Contains This Information

batch#

System-assigned number that identifies the batch that contains the notice.

comment

Message or note about the notice batch.

emailed

Number of e‑mailed notices contained in the batch.

last_output_date

Date the batch was last used to create notices.

last_output_time

Time the batch was last used to create notices.

printed

Number of printed notices contained in the batch.

send_email

Whether the notice was sent by email.

times

Number of times the batch has been used to create notices.

type

Type of notice.

The notice_content table stores more detailed information about individual unresolved blocks on a borrower’s record.

Column

Contains This Information

amount

Amount owed for the item (if any).

amount_str

Amount owed (formatted).

Use this column instead of the amount column for third-party report programs, since it is already formatted with dollar signs, decimal points, and so forth.

author

Name of the item’s author.

batch#

System-assigned number of the batch in which the notice is contained.

block

Block code for which the notice is created.

block_descr

Description of the block for which the notice is created.

burb_ref#

Number of the block in the borrower’s record.

call_number

Call number of the title for which the notice is created.

comment

Notes or a message about the notice or block.

content#

Notice that the line represents (first, second, and so forth).

This number is used with batch# to link each line in this table to a particular notice in the notice table.

copy

Copy of the title for which the notice is created.

date

Applicable date.

(For example, an overdue notice would have an overdue date.) This field is null where dates do not apply (such as with fines).

expire_date

Date a hold expires.

group_id

Groups items by block type.

(For example, overdues would be listed together, fees would be listed together, and so forth.)

ibarcode

Barcode of the item for which the notice is created.

item_location

Location code of the item to which the notice applies.

Note: You can use only one location in each report (either item_location or pickup_location).

notice_block_language

Message included on the notice (for example, “The following items are overdue:”).

This message comes from the Default Language field on the block table. (For more information, see Setting Up Blocks.)

pickup_location

Identifies the hold’s pickup location, if the notice is for a hold.

Note: You can use only one location in each report (either pickup_location or item_location).

price

Price of the item for which the notice is created.

title

The title of the item for which the notice is created.

 


© 1998-2017 Sirsi Corporation