Item Creation Date

Because of quirks due to the way the item-level Date Created field was handled during various upgrades and migrations, the data may not always accurately represent the date that copy record was actually created.

A Date Created value of 5/19/1999 is almost always erroneous for those libraries that were part of CCS at that time; the actual date created is probably much older. May 19, 1999 was the date that CCS upgraded to the version of Libs+ that added a Date Created field to the copy record, and the upgrade automatically inserted that date into every copy record.

For Crystal Lake, a Date Created value of 4/23/1991 is almost always erroneous; the actual date created is probably much older. Dates after that are probably accurate.

For Glenview, a Date Created value of 1/1/1970 is almost always erroneous; the actual date created is probably much older. Dates after that are probably accurate.

For Evanston, a Date Created value of either 1/1/1970 or 12/1/1990 is almost always erroneous; the actual date created is probably much older. Other dates are probably accurate.

For Highland Park, a Date Created value of 4/26/2005 is almost always erroneous; the actual date created is probably much older. Dates after that are probably accurate.

For Huntley, a Date Created value of 11/2/2001 is almost always erroneous; the actual date created is probably much older. However, dates both before and after it are probably accurate. Huntley started cataloging new records in the CCS database in June of 2001, but the rest of their existing holdings were migrated into the database on November 2, and were all given that date as a Date Created.

For Niles, in addition to the May 19, 1999 issue, a Date Created value of January 1 of any year is merely an approximation based on the barcode range and the section of the collection, and may be off by anything from a few weeks to a few decades. Any other date is probably accurate.