Open topic with navigation

# DateFormatCSVs

A list of supported date formats. One or more date formats that you want IDOL server to be able to read from the files that it contains. Separate multiple date formats with commas. There must be no space before or after a comma. You can type one of the following:

- `AUTNDATE`

- a string that contains one or more of the following:

  `YY` | Year (two digits). For example, 99, 00, 01, and so on.
  `YYYY` | Year (four digits). For example, 1999, 2000, 2001, and so on.
  `#YY+` | Year (two or four digits). If you provide two digits, it uses the `YY` format. If you provide four digits, it uses the `YYYY` format. For example, it interprets `07` as `2007 AD` and `1007` as `1007 AD`.
  `#Y` | Year (one to a maximum of 16 digits), optionally followed by `AD` or `BC`. An apostrophe (`'`) immediately before the year denotes a truncated year. For example, `2008`, `'97` (interpreted as `1997`), `97` (interpreted as `97 AD`), `'08` (interpreted as `2008`), `2008 AD`, and `200 BC`. A truncated year with a BC identifier is not valid (`'08 BC`).
  `#FULLYEAR` | Year (one to a maximum of 16 digits). For example, `8`, `98`, `108`, `2008`, each of which is taken literally. The year is taken relative to the common EPOCH (0 AD).
  `#ADBC` | Time period. For example, `AD`, `CE`, `BC`, `BCE`, or any predefined list of EPOCH indicators. Typically, the year specified in the above formats is interpreted as untruncated and relative to the EPOCH. For example, 84 AD is interpreted as 1984 AD, and 84 BC is interpreted as 84 BC. The only exception to this is when you use both `#YY+` and `#ADBC`. In this case, the format is interpreted as untruncated, even if the year was set to truncated by `#YY+`. For example, 99 AD is interpreted as the year 99 AD. HPE recommends that you use only `YY`, `YYYY`, or `#FULLYEAR` with `#ADBC`.
  `LONGMONTH` | A long month, for example, `January`, `February`, and so on.
  `SHORTMONTH` | A short month, for example, `Jan`, `Feb`, and so on.
  `MM` | Month (two digits). For example,`01`, `10`, `12`, and so on.
  `M+` | Month (one or two digits). For example, `1`,`2`,`3`,`10`, and so on.
  `DD` | Day (two digits). For example, `01`, `02`, `03`, `12`, `23`, and so on.
  `D+` | Day (one or two digits). For example, `1`, `2`, `12`, `13`, `31`, and so on.
  `LONGDAY` | Two digits with a postfix. For example, `1st`, `2nd`, and so on.
  `HH` | Hour (two digits). For example, `01`, `12`, `13`, and so on.
  `H+` | Hour (one or two digits).
  `NN` | Minute (two digits).
  `N+` | Minute (one or two digits).
  `SS` | Second (two digits).
  `S+` | Second (one or two digits).
  `ZZZ` | Time zone, for example, `GMT`, `EST`, `PST`, and so on.
  `ZZZZZ` | Time difference (one to nine digits). For example, `+04` denotes four hours ahead of UTC. Other examples include `+4`, `+04`, `+0400`, `+0400 MSD` (the string `MSD` is ignored). A further example is `+030`. In this case the time difference is interpreted as 30 minutes. This option accepts a single `Z` character in a date string as UTC. It accepts time zones between `-1300` and `+1500`.
  `#PM` | An `AM` or `PM` indicator (two characters). For example, `2001/09/09 02:46:40 PM`.
  `#S` | A space.

- Type formats in order of length (starting with the longest). HPE Distributed Index Handler matches format strings in the order they are listed. If a shorter format is listed first, HPE Distributed Index Handler might match against an incorrect format, for example, matching `19/10/2002` as `DD/MM/YY` and indexing the document with the date `19/10/20`.

- Separate multiple formats with commas. There must be no space before or after a comma. To specify a format that contains a space, put the format in quotation marks.

Type: | String
Default: | YYYY/MM/DD
Required: | No
Configuration Section: | Server
Example: | `DateFormatCSVs=D+/SHORTMONTH/YYYY,DDMMYY` In this example, only document dates with the format `D+/SHORTMONTH/YYYY` (for example, 2/Jan/2001) or `DDMMYY` (for example, 020101) can be indexed with a date. `DateFormatCSVs="D+SHORTMONTH YYYY","Date: D+ LONGMONTH, YYYY"` In this example, only document dates with the format `D+ SHORTMONTH YYYY` (for example, 2 Jan 2001) or `Date: D+ LONGMONTH, YYYY` (for example, Date: 2 January, 2001) can be indexed with a date. `DateFormatCSVs=LONGMONTH/D+/#Y H+:N+:S+` In this example, only document dates with the format `LONGMONTH/D+/#Y H+:N+:S+` (for example, September/9/2001 AD 2:46:40 or September/9/2001 2:46:40 or September/9/'01 2:46:40 or September/9/'01 AD 2:46:40) can be indexed with a date. `DateFormatCSVs=LONGMONTH/D+/#FULLYEAR #ADBC H+:N+:S+` In this example, only document dates with the format `LONGMONTH/D+/#FULLYEAR #ADBC H+:N+:S+` (for example, September/9/8 AD 2:46:40 or September/9/2008 AD 2:46:40 or September/9/'01 2:46:40 or September/9/'01 AD 2:46:40) can be indexed with a date. `DateFormatCSVs=D+ LONGMONTH YYYY HH:NN:SS ZZZZZ`
See Also: |

© 2017 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm