Understanding the Collections Information Report Output
An XML file that is generated by the Collections Information (Collectiondata) report and is forwarded to Unique Management for initial collections reporting. This XML file is structured as follows.
|
Field |
Description |
Example |
|
<mode> |
Defines the mode in which the report was run. Values are SUBMISSION, UPDATE, SYNCHRONIZE, TEST-SUBMISSION, TEST-UPDATE, and TEST-SYNCHRONIZE. The Collections Information report can be run in two modes: SUBMISSION and TEST-SUBMISSION. SUBMISSION mode is when the report is run to submit users to collections. The TEST- prefix indicates that the report was NOT run to update database records. |
SUBMISSION |
|
<created> |
Describes the date the report was run. |
6/2/2008, 10:45 |
|
<key> |
File record number |
37 |
|
<name_key> |
User’s name, capitalized and formatted as LASTNAME FIRSTNAME for sorting. |
DOE JOHN |
|
<full_name> |
User’s full name, shown in mixed case letters and formatted as Last name, First name, middle initial (if any). |
Doe, John Q. |
|
<last_name> |
User’s last name, shown in mixed case letters. |
Doe |
|
<first_name> |
User’s first name and middle initial (if any), shown in mixed case letters. If the user’s full name appears in field 2, this field is left blank. |
John |
|
<id> |
User’s user ID number. |
XXXX123456789 |
|
<alt_id> |
Value in the Alt ID field in the user record. This alternate ID may be a Social Security Number or driver’s license number. |
DL12345 |
|
<previous_id> |
User’s previous ID |
222 |
|
<language> |
User’s language in the user record. |
ENGLISH |
|
<profile> |
User’s profile name listed in the Profile Name field in the user record. |
PUBLIC |
|
<birthdate> |
User’s birthdate in the user record. |
03/30/1957 |
|
<category1> |
Value in the User Category 1 field in the user record, if any. |
MALE |
|
<category2> |
Value in the User Category 2 field in the user record, if any. |
HIGHSCHOOL |
|
<category3> |
Value in the User Category 3 field in the user record, if any. |
|
|
<category4> |
Value in the User Category 4 field in the user record, if any. |
|
|
<category5> |
Value in the User Category 5 field in the user record, if any. |
|
|
<category6> |
Value in the User Category 6 field in the user record, if any. |
|
|
<category7> |
Value in the User Category 7 field in the user record, if any. |
|
|
<category8> |
Value in the User Category 8 field in the user record, if any. |
|
|
<category9> |
Value in the User Category 9 field in the user record, if any. |
|
|
<category10> |
Value in the User Category 10 field in the user record, if any. |
|
|
<category11> |
Value in the User Category 11 field in the user record, if any. |
|
|
<category12> |
Value in the User Category 12 field in the user record, if any. |
|
|
<care_of> |
User’s name who is responsible for this user. |
Mrs. John Doe Sr. |
|
<day_phone> |
Value in the DAYPHONE entry in the Addresses tab of the user record. This entry typically shows the daytime or work phone number for the user. |
256-555-1414 |
|
<home_phone> |
Value in the HOMEPHONE entry in the Addresses tab of the user record. |
256-555-1234 |
|
<phone> |
Value in the PHONE entry in the Addresses tab of the user record. |
256-555-5678 |
|
<work_phone> |
Value in the WORKPHONE entry in the Addresses tab of the user record. |
256-555-9101 |
|
<zipcode> |
User’s zip code. The ZIP entry in the Addresses tab of the user record is necessary to allow sorting by zip code. |
35801 |
|
<address_line1> |
Address line 1 of the mailing address block. The mailing address is whichever address is specified as the Primary address on the Addresses tab of the user record. |
100 Main St. |
|
<address_line2> |
Address line 2 of the mailing address block. The mailing address is whichever address is specified as the Primary address on the Addresses tab of the user record. |
Huntsville, AL |
|
<address_line3> |
Address line 3 of the mailing address block. The mailing address is whichever address is specified as the Primary address on the Addresses tab of the user record. |
|
|
<address_line4> |
Address line 4 of the mailing address block. The mailing address is whichever address is specified as the Primary address on the Addresses tab of the user record. |
|
|
<address_line5> |
Address line 5 of the mailing address block. The mailing address is whichever address is specified as the Primary address on the Addresses tab of the user record. |
|
|
<address name="1"> |
Cumulative Address 1 information, if any. Each defined entry is contained by <entry> tags. |
|
|
<address name="2"> |
Cumulative Address 2 information, if any. Each defined entry is contained by <entry> tags. |
|
|
<address name="3"> |
Cumulative Address 3 information, if any. Each defined entry is contained by <entry> tags. |
|
|
<bill_fines_due> |
User’s total unpaid bill balance. |
25.00 |
|
<first_delinquency_date> |
Date of oldest unpaid bill. This date is shown in the date format configured for the SirsiDynix Symphony system, such as YYYYMMDD. |
20080702 |
|
<submission_referral_fee> |
Amount of the collection fee, if any is to be assessed to collect payment from the user. This amount is specified in the Basic Collection Fee field on the Fee/Update Options tab of the Collections Information report. |
5.00 |
|
<total_amount_due> |
Total amount due. This amount includes unpaid bill balances and the collection fee. |
86.00 |
|
<amount_paid> |
Amount this user has paid toward this bill. |
40.00 |
|
<amount_forgiven> |
This field is populated when paid bill(s) has a reason of PROCESSFEE and the payment type for the bill is CANCEL. |
5.00 |
|
<value_returned> |
This field is populated when paid bill(s) has a reason of LOST and the payment type for the bill is CANCEL. |
25.00 |
|
<library> |
There are two elements that describe the <library> element: <name> and <amount_due>. <name> is the Library policy name of the library that has an outstanding bill for this user. <amount_due> is the amount due to this library |
MAIN
66.00 |
Related topics