Prue,
we have this problem for some of our applications. We store the date as a
text field, not an ORACLE DATE field.
Debbie
Metadata Coordinator
Coordination Support Branch
National Library of Australia
ph. 02 6262 1673
fx. 02 6273 2545
e-mail [log in to unmask]
http://www.nla.gov.au/meta
> ----------
> From: [log in to unmask][SMTP:[log in to unmask]]
> Sent: Thursday, 6 May 1999 2:23 PM
> To: [log in to unmask]; [log in to unmask]; [log in to unmask]
> Subject: Date format in Oracle
>
> We are using Oracle for our metadata repository and ISO8601 as our
> metadata
> date scheme, with the expectation of having dates of the form YYYY,
> YYYY-MM
> or YYYY-MM-DD. However, it appears that Oracle cannot cater for the YYYY
> or
> YYYY-MM form and requires us to convert to YYYY-01-01, YYYY-MM-01 or a
> similar default. We feel that this is not acceptable bibliographic
> practice
> - it may not matter for searching, but could be very misleading if dates
> are displayed in a search result.
> Has anyone else had this problem, and were you able to resolve it?
> Regards, Prue
>
> Prue Deacon
> Web Business Solutions
> Commonwealth Department of Health and Aged Care, Australia
> [log in to unmask]
>
>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|