Follow

10/31/15: How DISCO handles 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. 

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 of 12/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 10/31/2015.

To search on date, use the following syntax:

  1. date()
  2. date(...to...)
  3. date(before...)
  4. date(after...)
  5. createdate()
  6. loaddate()
  7. senddate()
  8. receiveddate()
  9. familydate()
  10. lastmodifieddate()
  11. alldates()
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments