I sympathize with your plight. This issue has come up time and time again.
There was a proposal from a project suggesting that new qualifiers be
approved for "Date.Digitized" and "Date.Original" for this very situation.
(It didn't get too far.) And there is a long history behind the
controversy about whether a Dublin Core record should describe only the
digitized and another is needed for the original (the "one-to-one"
controversy-- PLEASE let's not discuss that).
I would agree with you that the date of interest to you in these
situations for resource discovery is the date of the original. And Dublin
Core is intended for resource discovery. Date is defined as:
Name: Date
Identifier: Date
Definition: A date associated with an event in the life cycle of the
resource.
Comment: Typically, Date will be associated with the creation or
availability of the resource. Recommended best practice
for encoding the date value is defined in a profile of
ISO 8601 [W3CDTF] and follows the YYYY-MM-DD format.
That certainly allows you to use Creation date in the Date field; I would
argue that it is general enough to allow you to interpret the creation
date as either original or digitized creation, but you aren't able to
distinguish between those two. The following qualifiers for date are
approved:
Created
Valid
Available
Issued
Modified
Maybe your digitized date would fit into another category (Date Issued?).
Of course, it is not clear from your message whether you're using Dublin
Core unqualified or qualified. If unqualified (which is what I think
you're asking about), then you certainly could use DC.Date, since the
discovery date for creation that you're interested in is the date the
intellectual content was created (original date).
The Date element is a real problem in the DC element set and there have
been numerous criticisms about its lack of specificity. Without knowing
what type of date it is can make it almost useless. So I would at least
use the date that is of most interest to your application.
Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior Networking and Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ 1st and Independence Ave. SE ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4402 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ [log in to unmask] ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Date: Wed, 2 May 2001 10:18:56 +0200
> From: =?iso-8859-1?Q?Hilde_H=F8g=E5s?= <[log in to unmask]>
> Subject: Date for digitized objects
>
> Dear all,
>
> At the present I am working wiht DC for digitized objects, for instance a
> digitized radio broadcasting, a photo or a sound recording. I have a problem
> with the date for digitized objects. As I read the DC definitions and "Using
> Dublin Core", DC.Date should be used for the "instantiation", or the version
> "in-hand". Would this imply that DC.Date for digitized object should contain
> the digitizing date?
>
> If this a correct interpretation, then my problem is that this date is of no
> (or little) interest to the user. The interesting date is the date of the
> original, the broadcasting date or the date the photo was taken. Where do I
> put this kind of date? It could belong to DC.Source and one of my present
> ideas is to add a local qualifier to Source, something like Source.Date for
> the date of the original.
>
> Doos anyone "out there" have a good answer to my problem? (I do apologize if
> the matter has been discussed on the list before.)
>
> I appreciate your help!
>
> Hilde
> ___________________________________
> Hilde Hoegaas
> IT-dept. National Library of Norway, Rana Division
> E-mail: [log in to unmask]
>
>
