Serial Claim Report

Serial claim report program, written by ITD, has the capability of producing report and generating claim letters & updating Aleph. As requested by the Acquisitions/Serial Community, currently only the former is utilized and the latter is a manual process. To produce a report, the program identifies items with certain item process statuses and expected arrival date or issue date, retrieves data and then parses out the appropriate information to each campus' Task Manager. A date limit is used in order to produce manageable reports for all campuses. The process frequency of the report determines the number of days that are covered in each run. It is 32 days with a monthly run and 17 days for bimonthly. The process date is set to the 1st of each month plus the 15th for bimonthly.

With each run, the program checks the processing date and counts back 17 days. For example, November 1st report covers October 15 – 31 and the mid–month run covers October 29 – November 14; December 1st report will have November 14 – 30 and for months that have 31 days will be 15 – 31.

Two pieces of data determine the inclusion of items on a report: item process statuses, i.e., CL, EX, or NA, and the expected arrival date or the issue date (for items created in version 15). One easy way to identify items that created in version 15 is that the expected arrival date and the issue date are the same. Here is how the calculations are done:

1st claim: either expected date (for items created in v 16) or issue date + 1st claim interval (for items created in v 15)
2nd claim: 1st claim date + 2nd claim interval
3rd claim: 2nd claim date + 3rd claim interval
4th claim: 3rd claim date + 4th claim interval

The report sorting is by title/ADM doc#/issue date/description.

11/15/2005 yq

Information Technology Division College Park, MD 20742-7011
Please send comments and suggestions to ITD's Webmaster.
Content questions should be directed to Yalan Qi.