> Date: Tue, 17 Jun 97 17:09:05 EST
> From: "Ray Denenberg (Library of Congress)" <[log in to unmask]>
>
> As a matter of fact there is an effort in progress to create a
> mapping between DC and bib-1. The proposed mapping is not yet
> complete but since this has come up I've included below how far
> we've gotten.
Thanks for this very useful summary.
> People talk in various contexts about retrieving Dublin Core
> records, or, in the case of CIMI, a structured Z39.50 metadata
> element containing DC elements as its subelements. But it isn't
> quite as clear why we want a mapping of Dublin Core to Z39.50 search
> access points. Can someone please articulate this?
We're basically representing the needs of the people we're working
with. We have partners who, with our help, want to publish existing
databases through Z39.50 servers. Some of those databases allow
searches on access-points which seem to correspond closely to Dublin
Core elements. We have been asked on various occasions for help in
identifying the appropriate USE attribute for these searches.
> And if so, do all DC elements apply or only some?
Probably not all, but it's hard for us to predict which ones may or
may not be included. For example ...
> For example, take the DC element "rights". Is it intended to search
> within the "rights" field, or is "rights" perhaps a DC element that
> doesn't map to a search access point.
No, that's one that we've been specifically asked about. (We've been
using 2004 -- Copyright Restriction -- from the CIMI-1 attribute set
for this: does that seem reasonable?)
> Resource Identifier may map to the combination: Use -- DocId,
> structure -- urx. This raises the question: what is the purpose of
> searching on a Resource Identifier? Is it for known item
> searching, or actually searching for records containing a given,
> say, URL?
We don't currently have a need to search for URLs, neither do we
envisage one -- however, we might not have envisaged a need to search
for "rights" either.
(Why would the structure=urx attribute be needed here?)
> 3. Some don't map:
> format
> contributor
> source
> Discussion: These three may be potential extensions to bib-1.
We have an existing requirement for searching "source", so this
extension would be very welcome.
The full list of our current needs is:
author BIB-1 1003
publisher BIB-1 1018
date We're currently using BIB-1 1011
(Date/time added to database), which
seems right for this database; but as
you say, Dublin Core date may be
underspecified.
source -- no mapping --
rights management CIMI-1 2004
Thanks to everyone who's helped with this thread.
Mike Taylor
System Simulation Ltd.
[log in to unmask]
Tel. +44 171 836 7406
|