Good Afternoon Andy et al,
We actually need it for digital collection. Therefore we need to store time period for for serials, date of edition for books (Date.dateCopyrighted) and creation date for images and other digitalized materials (Date.created). The users will see, for example:
Harrison's Internal Medicine, Copyright 2005 (for book)
The American journal of surgery (Closed end journal)
Coverage: Available from 1926 until 1994
Annals of surgery (Open end journal)
Coverage: Available from 1996
We want to keep the system reasonably simple. I think that Andy is right, Date.available perhaps is not the best choice. How about using Coverage.temporal?
Also, what exactly is Period? According to http://dublincore.org/documents/dcmi-period/
it can be used to refine Date or Coverage elements. But it is not a Qualifier. It is not a separate element either.
Please forgive me if my question is too naive, but I am a new DC user,
Thanks a lot in advance,
Vlad
-----Original Message-----
From: DC-Libraries Working Group on behalf of Andy Powell
Sent: Thu 4/27/2006 11:34 AM
To: [log in to unmask]
Cc:
Subject: Re: How to use Data.availabe to store start and end dates
The collection-oriented approach suggested by John Robertson on
dc-general makes sense to me.
I also have some concerns that dcterms:available doesn't carry the right
semantics for what you want. For example, your holdings for a
particular journal might run from 1998 until 2000, but the issues
themselves might still be available (online or in the library) today.
In that case, dcterms:available is an open-ended date range running from
1998 to the current date.
So I wonder if holding information is better modelled using a range of
dates for dcterms:issued or for cld:dateContentsCreated (as per the
collection description application profile)?
Andy
--
Head of Development, Eduserv Foundation
http://www.eduserv.org.uk/foundation/
[log in to unmask]
ჸ (0)1225 474319
> -----Original Message-----
> From: DC-Libraries Working Group
> [mailto:[log in to unmask]] On Behalf Of Vladimir Makarov
> Sent: 27 April 2006 04:41
> To: [log in to unmask]
> Subject: How to use Data.availabe to store start and end dates
>
> Dear Members,
>
> We are creating relational database (MySQL) to map DC
> Metadata schema. We need to indicate the holding for some
> journals. Holdings may be a range (ex. 1995 - 2005) when we
> started and stopped subscription or, most often, the date
> from resource became available till the present time.
> According to the specifications at
> http://dublincore.org/documents/2005/11/07/usageguide/qualifie
> rs.shtml,
>
> the DC Element "Date" has following possible refinements (qualifiers)
>
> Created
> Valid
> Available
> Issued
> Modified
> Date Accepted
> Date Copyrighted
> Date Submitted
>
> Available seems to be a good choice, as per
> http://dublincore.org/documents/usageguide/qualifiers.shtml#available,
> "Available" is a date (often a range) that the resource will
> become or did become available.
>
> My question, however, is:
> While entering the Date.available to MySQL table, we could
> use the text column and enter it simply as "Available 1995 -
> 2005" or "Available from
> 1995 -- ", etc.
> But I think everyone agrees that is not the best approach.
> Date element should be represented by "Date" MySQL (or other
> Database) column data type. We are tempted to add our own
> qualifiers, such as "availableStart"
> and "availableEnd", but wish to use standard qualifiers only
> for interoperability reason.
>
> I am sure that the problem we are facing is not unique. If
> someone is willing to share, we will greatly appreciate it,
>
> Many thanks in advance,
>
> Vlad
>
> ----------------------------------------------------------------
> Vladimir Makarov
> Memorial Sloan-Kettering Cancer Center Library
> 1275 York Ave
> New York, NY 10021
> Tel: 212-639-7422
> Fax: 212-717-3048
> eMail: [log in to unmask]
> ----------------------------------------------------------------
>
=====================================================================
Please note that this e-mail and any files transmitted with it may be
privileged, confidential, and protected from disclosure under
applicable law. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
reading, dissemination, distribution, copying, or other use of this
communication or any of its attachments is strictly prohibited. If
you have received this communication in error, please notify the
sender immediately by replying to this message and deleting this
message, any attachments, and all copies and backups from your
computer.
|