Difference between revisions of "Date field"
(→Description) |
|||
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
| + | |||
| + | This field is used to store a single date. Internally EPrints always uses ISO standard notation for dates, it avoids confusion. This is YYYY-MM-DD. | ||
| + | |||
| + | In bibliographies sometimes exact dates of publication (or other events) are not known. EPrints allows you to store month and year values in date fields. YYYY or YYYY-MM. | ||
| + | |||
| + | In the database EPrints actually uses 3 integer fields to store the date, rather than a built in date field. This is because of the need to allow "NULL" in month and day if the date is just "1998". | ||
== Properties == | == Properties == | ||
Revision as of 17:58, 9 January 2007
Description
This field is used to store a single date. Internally EPrints always uses ISO standard notation for dates, it avoids confusion. This is YYYY-MM-DD.
In bibliographies sometimes exact dates of publication (or other events) are not known. EPrints allows you to store month and year values in date fields. YYYY or YYYY-MM.
In the database EPrints actually uses 3 integer fields to store the date, rather than a built in date field. This is because of the need to allow "NULL" in month and day if the date is just "1998".
Properties
| name | default | description |
| min_resolution | day | ... |
| render_res | day | ... |
| render_style | long | ... |
