Data - How do I deal with invalid dates?

DISCO attributes dates to each document based on information provided in the load file or within the metadata of the document file. However, the dates given are sometimes incorrect and result in documents being displayed or sorted in nonsensical order in DISCO. 

What is an "Invalid Date"?

  • Any date before 1/1/1980 is considered to be invalid for our purposes (the year 1980 date is often seen as the result of a Y2K bug that stamped documents to that year).
  • Any date that is the date of processing of the load file
  • Any date that is in the future (beyond present day)

How DISCO handles an "Invalid Date"

To address this problem, if a document's date is determined to be invalid, DISCO will fall back to a different date referenced in the load file or metadata. In the event that we have exhausted all dates in the pecking order, DISCO will assign the document a date of12/31/9999, which will be a reflection that it is invalid in our system (and cause it to be sorted to the bottom when sorting on date).


Note: DISCO handles invalid dates using the above process on new ingests on or after 11/03/2015.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request