Dear Vlad,
have you considered thinking about the journal run as a collection? I'm
a novice here so I may not see the problems inherent in this suggestion,
but it makes more sense to me than treating it as an item.
For example, you could use accrualPeriodicity (conforming element) to
describe the frequency of issue.
I think the collection description working group might be working on a
recommendation for the open date range issue.
(http://dublincore.org/groups/collections/index.shtml).
As the 'right' way to do this is not yet resolved, could you create the
date range using separate fields as you suggest and on export map them
to whatever labels/ approach becomes the DCMI recommendation? You would
probably want some data mapping and transformations to occur on the
dataset you're exposing for interoperability anyway (e.g. adding a
rights statement or other data applicable to all your records).
I've a colleague who's taken this approach to collection start and end
dates for the Scottish Collections Network (data dictionary available at
http://scone.strath.ac.uk/service/sconeservice/ddtbsel.cfm )
I hope I'm not missing your point.
regards,
John Robertson
Vladimir Makarov wrote:
> 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/qualifiers.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]
> ----------------------------------------------------------------
>
--
R. John Robertson
Centre for Digital Library Research
Department of Computer and Information Sciences
University of Strathclyde, Livingstone Tower
26 Richmond Street, Glasgow, G1 1XH, UK
Tel: +44 (0) 141 548 5854
Website: http://cdlr.strath.ac.uk/
|