- Article Type: General
- Product: Aleph
We see cases of incorrect dates in the "Last Return" date column of the GUI Circulation Items list. We see some dates which are in the future (such as, "10/00/2040") and others too far in the past (such as, "09/04/1909").
Though small discrepancies can be due to the time on the pc being set incorrectly, large errors -- in the return date, specifically -- are almost always due to incorrect backdating on the Return "Override Date" screen.
As of 2007, the system has prevented the entry of override dates in the future ("Return date cannot be later than now"), but, as described in SKB 8192-1639, it did not always do so. If you returned items prior to 2007, you could have these future dates.
There is nothing in the system to prevent the entry of dates in the far past as the override date.
The following SQL can be used to locate cases of future returned dates. The substr (z36h_time,1,8) shows you what the returned date *should* be.
SQL> select z36h_rec_key, z36h_id, substr (z36h_time,1,8), z36h_returned_date from z36h where z36h_returned_date > '20091119' order by z36h_id;
SQL> select z30_rec_key, z30_date_last_return from z30 where z30_date_last_return > '20091119';
<where "20091119" is today's date>
and the following to locate cases of returned dates in the far past:
SQL> select z36h_rec_key, z36h_id, substr (z36h_time,1,8), z36h_returned_date, Z36H_RETURN_CATALOGER_IP from z36h where z36h_returned_date < '19900101' and z36h_returned_date ^= 0 order by z36h_id;
SQL> select z30_rec_key, z30_date_last_return from z30 where z30_date_last_return < '19900101' and z30_date_last_return ^= 0;
<where '19900101' is the earliest legitimate returned date that an item could have>
There is no Aleph function to correct such dates. Such correction (if necessary) would need to be done using SQL. As always, you should back up the table before performing any such update.
- Article last edited: 10/8/2013